So I begin to see the real problem why end user (your customers) will never see the light of a 64bit platform ... you realize you're just shooting yourself in the foot for a few extra pennies? If you looked at a bigger long term future, those pennies would be dollars (or euros - take your pick). It really boggles my mind ... you have the opportunity to move forward and your stuck in the past ... 13 years in the past.
It's really mind-blowing how you managed to be entirely and utterly wrong under every account with just one simple sentence. You managed to get the reality of the situation ENTIRELY backwards, the only possible explanation is, you wanted to post this on Aerosoft forum, and got confused and posted it here.
Let's see the facts:
- We were the absolute FIRST developers to release fully native native FSX code for a scenery, back in 2007, when nobody else had any idea how to do it
- We were one of the first developers to support Prepar3D, without absurd dual licensing, paid updates and anything like that. All our products license for P3D has always been offered under the same license than the FSX one.
- We were one of the first developers to support Prepar3D V2, with all our installers available a couple of days after it was released.
- We are still one of the first developers that, since 2010, doesn't have ANY single bit of FS8 or FS9 code in their sceneries. KDFW, KLAX, CYVR and KJFK2 don't have ANY legacy code, and there are basically no other developers that can say the same.
If you should hold to your absurd reasoning that you would stop purchasing products from developers "stuck in the past" (which is laughable when directed to FSDT), you should stop to purchase *anything*, because each and every 3rd party scenery out there has some FS8 code inside.
We have this problem only in some of the older sceneries and, as I've said, quite clearly, we are just waiting for the first fix from LM and, if they don't fix it, WE WILL! Wasn't that clear enough ?
last thing I want is to see a 3rd party content provider telling LM to support 13 year old design constructs just so they don't have to do any work. At what point did you think/believe LM are the only ones that should be updating their work??
Because, OBVIOUSLY, if a fix from LM will make HUNDREDS of 3rd party sceneries to be working ( hundred ONLY from Aerosoft, according to them, we don't know how many more are around, and that's not even counting freeware ), it makes sense for them to fix it, instead of having hundreds of sceneries to be updated and users having to scourge around for hundreds of patches for all their stuff.
But other than that, this is not just an "ordinary" backward compatibility issue. Do you even KNOW how the problem manifests ? The whole P3D MENU DISAPPEARS, and the fps halves.
Do you find this to be normal ? Don't you realize that, something like this might be a symptom for a potentially dangerous memory leakage in the sim ? That's why THIS has to be fixed by LM or, at least, being checked why it's happening.
