Thanks for reply Pat, and excellent news.
Colonel, read Pat's post:
I do not put ground objects down that are well outside mission parameters, so if you go off flying things that you expect might not be there.
My grfx settings are high (not maxed anymore post-1.016
) but I experienced this issue pre 1.016 anyways. It is not related to object render distance because buildings are still not there even when I fly low over where they are supposed to be. Other villages/airfields along the path (such as Mars-le-tour and Puiseux on the map) are rendered at greater visual distances off the mission path than you see in the screenshot with Doncourt.
This must be the generator trying to save system resources with areas literally off the waypoint path, and those airfields and villages not rendered are 180 degrees from the path (see map) BUT unfortunately within visual distance. Though please, somebody confirm and I'll feel much better.
I can email the mission as a test.
While on the subject, since there is an object render distance set anyways by the game, what resources are being spared by the mission generator cutting out buildings off the path? File size/mission load time I can understand, it can be a pain waiting. But if one has plenty of RAM there shouldn't be an in-cockpit performance issue once the file is loaded, correct? i.e. more potentially
viewable buildings spread out further around the mission path cannot all be seen at once--you still have the object render distance controlling what you see by where you are. Including more buildings around the mission area only allows you to deviate more from the path and still enjoy the scenery.
And who hasn't had an A2A engagement that took them considerably off the mission path? Chasing, or being chased...