I surely believe that everything was tested but it can't be the case that we've bought an unusable airport if we want to use it in combination with commonly used addons like the NGX and ORBX.
As I've said already to another user, which after my explanation got my point, it's just wrong to automatically assume the "commonly used addons" automatically means the newest product arrived should RESTRAIN in detail, just because there's are already many other products that use lots of memory and someone might want to use them all together at the same time in the same place.
If you bought CYVR today without having the NGX, you wouldn't get ANY OOM, because you would immediately save 800MB, which is more than what CYVR takes. If you decided to buy the NGX the next month, you might start seeing OOMs, then which one is to blame ? You would get the impression the newly purchased airplane broken an airport which was otherwise working very well and it still works with "any other airplane".
I'm sorry, but it's nobody's fault if there are many addons to choose from, and FSX only supports up to 4GB. The only real problem here, is the unfortunate situation we are in, with no short term hope to have a 64-bit FSX, since LM said it will be very complex to port P3D to 64 bit, and they are probably the only ones that can do that.
Let's assume this reasoning that you don't accept either to stop using many addons together, and you don't accept to lower your settings either, which is of course agains the cold hard fact that a certain point your 4GB WILL end, you know what will happen in a few months/years, if you continue to use this kind of reasoning ?
You will not be able to purchase or add ANYTHING anymore, because the more pre-existing stuff you have on the market, which will then fall into the "commonly used addons", the less memory you have for a NEW product, because if this year your FSX config starts at 3.2GB, the next year, if you keep adding things which you pretend to use, all together, without any limitation, your FSX will start maybe at 3.8GB, so ANY scenery added in such situation, even the smallest one, will NOT fit in memory, and you'll blame that poor future scenery developer, that maybe took great care to make a scenery that takes half size of a current one...
As other users also stated, we never had these OOM issues at any other airport. It's not fair to tell people to lower their texture size (the manual emphasizes to set it to HD!) or not use ORBX anymore.
First, nobody said to stop using OrbX which, even if it obviously has an impact, it's not the largest one. We offered many choices, that don't involve stopping using anything, which are:
- Try to use DX10, this will immediately save you about 300MB
- Turn off HD textures
- Lower your settings, especially the scenery radius
You don't have to do everything: you can CHOOSE which solution to use. OR, you lower other settings, OR you simply don't fly with a certain airplane there.