FSDreamTeam forum
September 16, 2019, 10:40:05 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Login Register  
Pages: 1 [2] 3 4
  Print  
Author Topic: Update on the ORD V2?  (Read 7561 times)
Zimmerbz
Newbie
*
Posts: 31


« Reply #15 on: January 31, 2019, 04:24:32 PM »

Yikes.  Iím beginning to think this is never going to be released!
Logged
Captain Kevin
Beta tester
Sr. Member
*****
Posts: 258


Captain Kevin


« Reply #16 on: March 15, 2019, 03:52:18 AM »

Yikes.  Iím beginning to think this is never going to be released!
That's what everyone says about just about everything nowadays.
Logged

Captain Kevin
Zimmerbz
Newbie
*
Posts: 31


« Reply #17 on: March 15, 2019, 03:33:14 PM »

Has there been a status update other than in 2017 saying it will be released sometime in 2018 yet we are in 2019?  The YouTube stuff looks great and looks pretty complete to me but an update on the progress would be appreciated.
Logged
virtuali
Administrator
Hero Member
*****
Posts: 36006



WWW
« Reply #18 on: March 15, 2019, 05:00:13 PM »

Has there been a status update other than in 2017 saying it will be released sometime in 2018 yet we are in 2019?  The YouTube stuff looks great and looks pretty complete to me but an update on the progress would be appreciated.

The scenery is being worked on, and will be released when it's ready. You wouldn't want to be released *before* it's ready, don't you ?
Logged

Zimmerbz
Newbie
*
Posts: 31


« Reply #19 on: March 15, 2019, 10:40:33 PM »

I totally agree.  I wouldn't want an unfinished product.  I was just saying some progress updates would be nice to what is left, what is completed, etc. 
Logged
Captain Kevin
Beta tester
Sr. Member
*****
Posts: 258


Captain Kevin


« Reply #20 on: March 15, 2019, 10:59:25 PM »

I totally agree.  I wouldn't want an unfinished product.  I was just saying some progress updates would be nice to what is left, what is completed, etc. 
I don't know how much use that would be. When it comes to software, it's usually the final bits that can be the most difficult. In addition, sometimes you have an issue where you think you fixed something, only to then introduce new problems, and now you have to take the time to fix that. So it's very hard to say.
Logged

Captain Kevin
NMahinK
Full Member
***
Posts: 112



« Reply #21 on: March 16, 2019, 06:49:28 AM »

It's the last 50 feet of Everest that is the hardest to finish......In the meantime, enjoy the other airports that our passion has to offer.
Logged
767 Pilot
Newbie
*
Posts: 36


« Reply #22 on: March 17, 2019, 01:33:49 AM »

Here is a website to go to.....: O'Hare 21

Doug
Logged
skywreck
Newbie
*
Posts: 14


« Reply #23 on: March 21, 2019, 03:59:56 PM »

If it is ready why not release it without the PBR? PMDG as an example just did an update on the 747 to convert to PBR, could you not do the same when you finally finish the PBR textures?

regards

Joaquin
Logged

Thanks and regards


Joaquin Blanco

Intel Core i7 4790K Haswell overlocked to 4.4GHz, Corsair Hydro Series H75 Liquid Cooler, Asus Z97-K Motherboard, 16GB Corsair/Crucial/Samsung PC3-12800 1600MHz DDR3, GeForce GTX 970 4GB, 250GB Samsung 840 EVO SSD, Seagate 2000GB SSHD Hybrid.
virtuali
Administrator
Hero Member
*****
Posts: 36006



WWW
« Reply #24 on: March 21, 2019, 04:56:47 PM »

If it is ready why not release it without the PBR? PMDG as an example just did an update on the 747 to convert to PBR, could you not do the same when you finally finish the PBR textures?

Nobody ever said it's "ready", not even with non-PBR textures. There's nothing to convert, the scenery was made as a PBR project even before PBR support for P3D was announced, it's just the scenery is incredibly big, and it's constantly changing AS WE SPEAK.

We already remade some parts of the ground, because we got some pictures which shows even the current AIRAC chart included in the latest Navigraph update, it's already obsolete, and I expect it will change again, many times, before it will be released.
Logged

Richard McDonald Woods
Full Member
***
Posts: 127



WWW
« Reply #25 on: March 22, 2019, 10:42:35 AM »

Waiting for time to stand still Huh
« Last Edit: March 22, 2019, 10:45:02 AM by Richard McDonald Woods » Logged

Dave81
Newbie
*
Posts: 16


« Reply #26 on: March 22, 2019, 04:33:29 PM »

This isn't meant as me being impatient or understanding that things change but this was the quote from April 17th 2018:

"We decided to "froze" it at the March 2018 situation, otherwise we'll never be able to release it...".

I take this is no longer the case?

Thanks,
Dave
Logged
virtuali
Administrator
Hero Member
*****
Posts: 36006



WWW
« Reply #27 on: March 26, 2019, 01:51:31 PM »

We decided to "froze" it at the March 2018 situation, otherwise we'll never be able to release it...".  I take this is no longer the case?

Of course, just read my last post.

In April 2018, nobody outside LM could possibly knew, if and when P3D would eventually get PBR (we only assumed it would, eventually, and we were right, but there was no telling exactly *when*, back then).
Logged

Zimmerbz
Newbie
*
Posts: 31


« Reply #28 on: April 05, 2019, 03:15:19 PM »

Are you able to provide a more detailed progress update?  Or is the 2017 announcement that it will be released sometime in 2018 going to morph into a 2019 announcement that it is going to be released sometime in 2020?
Logged
virtuali
Administrator
Hero Member
*****
Posts: 36006



WWW
« Reply #29 on: April 05, 2019, 03:41:03 PM »

Are you able to provide a more detailed progress update?  Or is the 2017 announcement that it will be released sometime in 2018 going to morph into a 2019 announcement that it is going to be released sometime in 2020?

It will be released when it's done. You don't want it to be released *BEFORE* it's done, don't you ? The development is progressing just fine, it's just an incredibly huge airport, and we want to make it right.
Logged

Pages: 1 [2] 3 4
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!