Could you please tell me the reason for that .cfg change? I can assure that I haven't touched anything else in FSX and there has been no other installation in the meantime.
That setting is confirmed to be dangerous and will cause crashes (not just to FSDT sceneries), see here:
http://www.fsdreamteam.com/forum/index.php/topic,13623.msg104730.html#msg104730So we remove it while installing, since we cannot afford to have users being mislead the scenery crashes, when they have a setting that has been proven to be very dangerous, which of course it's the reason why FSX, by default, don't use it (it uses an internal value which is way higher than zero).
See this, directly from Microsoft:
https://blogs.msdn.microsoft.com/ptaylor/2007/06/01/fsxtweak-of-the-week-or-2/In RTM, the default setting was 1MB (1000000). The lower this number, the more pools the allocator will have to rummage through to find space for buffers and the more stutters you may have. In Sp1, we raised the default to 4MB (4000000) and optimized the underlying algorithm for finding free buffers.
So, setting it to 0 could be very dangerous, and it will hurt performances since the CPU will have to do more work, and it will cause graphic artifacts and possibly crashes, if the combination of scenery+airplane is taking a lot of VRAM.
Since we cannot just change it to a random value, the most sensible option is simply removing the section, so FSX will go back to default ( 4MB on FSX SP2/Xpack ).
Of course, if you are *sure* that tweak is good for your system, you can always put it back as it was.
