Question is who is going to release their version first? With a finally updated version of KORD, whoever releases their version first is probably going to take the market on this well needed release. And with Drzewiecki releasing at least 2 airports in that current region for 1 price. Going to be interesting who gets the major downloads.
We took an eye on KJFK sales over the years, checking the montly sales data and, we were never able to observe the *slightest* change in sales, comparing before and after the release of the supposedly newer and more affordable New York airport package. In fact, I must say we even noticed a small *increase* in average monthly sales, and the most read questions on forums was users asking if they could use the other DD airports together with FSDT KJFK.
And KJFK is in a much worse competitive situation compared to KORD V2, since we haven't updated it since 2013, it starts to look a bit dated, there has been several changes in the Terminals too, but none of this is stopping users from buying it, even today.
KORD V2 is an entirely different matter, since it will be fully updated, and it's a scenery that we are sure will be the final word on O'Hare for the last decade. And it's a scenery made from the ground up for PBR and P3D4 and, while someone will try to downplay this, but I think you all noticed how much better sceneries using the P3D4 SDK looks to much better AND perform better than things compatible with FSX as well.
Not many might be aware of this, but the recent issue of lower fps in 4.5 is being looked at by LM and should be hopefully fixed soon, and during testing, LM keeps asking how many sceneries/airplanes originally made for FSX were installed. And some affected users wondered why they didn't see any fps drop (comparing 4.4 to 4.5) with the latest FlyTampa KLAS, while they DID had a 30% fps drop in another scenery made by a developer I won't name here, which still supports FSX.
LM might be eventually able to fix this, but this won't keep happening forever. At a certain point, I think FSX backward compatibility will just go away because, if I was LM, I would start wondering how sensible is spending time to fix issues related to make old stuff work, and I would really love a future V5 would just stop supporting anything that is not at least P3D4-native.