Now show me a video from 15 miles out on a stabilized approach.
"Stabilized" doesn't change anything, unless you were trying to say that my crappy hand-flying was giving the scenery an unfair advantage regarding smoothness.
At 15 NM out, it's entirely normal you would see ONE big pause, when the scenery loads, which is a common thing for all our sceneries, since we do custom memory management which means nothing of the scenery is loaded when you are outside of its range, so no memory is taken when not required, and all memory is reclaimed when you go somewhere else.
With other sceneries that don't have this custom memory management, it's very well known default simulator memory handling is not very efficient and not all scenery is fully unloaded, even if you are hundreds of miles away. Which is why, many users got accustomed to change their Scenery Library for each flight, and turn off all the scenery except the starting and the destination one, to save memory. There are utilities created to ease this process.
This is not required for our sceneries, thanks to the custom memory management, at the small price of a single pause at about 15-16 NM out, which is when the scenery loads.
This scenery is made to be still compatible with FSX so, even if in P3D4 the loading range is larger, the scenery must load at some time so, it wouldn't be very different if we loaded everything at, let's say, 30 NM, you still would have a pause but, such larger range would likely affect other airports nearby so, 15-16 NM is the correct range.
In FSX, part of the scenery loads at 15 NM out, and part loads progressively, since the whole scenery won't fit in memory (especially together with memory hungry airplanes) so, while in FSX the initial pause at 15 NM would be shorter, you'll have many smaller pauses during the approach.
I hope you agree with me that a single pause at 15 NM out and then nothing else is better than many smaller pauses all along the approach. But if you want to simulate this in P3D4, lower the "Anti pop-up" setting in the Addon Manager to its minimum value of 1, and the scenery will behave as in FSX. But it's surely much better the way it is now.
Of course, we don't support FSX anymore, so all our future sceneries will get away with this memory saving methods, since they will only have to work with P3D4, and will be designed taking into account this.
