Mine have been set a varying levels, to determine their effect.
What I think my LNM shows clearly is why FPS could be being decreased over time.
Its not about that slider, which sets the Intial level of Simobjects created.
It should be about the number of simobject, that can exist, within a given range of your plane, how that varies with Altitude, and the type of simobjects.
The Optimum control would be to
(1) Set the total # that can exist.
(2) Set the Boundary in which they can exist… Typically based on
(a) If you can see them
(b) If you are in radio range of their communications
Ideally, you want the maximum number, that are relevant to you, limited by what your CPU can handle and any particular time, or part of your flight,
Ie, Once you are in the air, at a reasonable altitude, and distance from an airport, any Ground Services Simobject should be destroyed.
The problem is, it looks as if simobject generally are not being destroyed, which is likely just an oversight… but very obvious when looked at.
Its a complex compromise—
The biggest issue I now have , is not Framrate, but with the CPU no longer thread limited, it is allowing my GPU to run wild, and really heat up, while my CPU is remaining cool.
For any given hardware systsem, its a complex compromise, to set sliders, to optimize both CPU & GPU resources.
LNM can show Aircarft, not yet figured out how to visualize the total number of Ground Simobject, to determine their “life cycle”