Back to preport from my formerly announced test:
I repeated the flight from about 25 minutes east of Kansas City, following the IS70 westward until about Abilene.
What remained the same (in comparison to my last flight of that route)? - aircraft, scenery with addons, route.
Weather (from AS4) had changed to overcast at 7000ft in the beginning, opening to clear sky in the second half of flight.
What I changed:
I updated the video driver to the most recent version 388.43 (the former version caused driver failure messages during P3D flights, the version before that caused P3D to pause for further 4-5 seconds each time I ended a break in a flight).
Then I changed the following video setting parameters:
FSAA: Off (was on)
AA: 8xMSAA (was 2x)
Texture Filtering: Anisotropic 16x (was Anisotropic 4x)
VSync: On, Triple Buffering marked (was off, not marked)
Level of detail radius: Ultra (was Max)
Tesselation factor: High (was Ultra)
Mesh resolution: 2m (was 1m)
Texture resolution: 60cm (was 7cm)
Use high-resultion terrain textures marked (was marked)
Scenery complexity: Very Dense (was Extremely Dense)
Autogen draw distance: Medium
(was Extremely High)
Autogen vegetation density: Very Dense (was Extremely Dense)
Autogen building density: Dense (was Extremely Dense)
Dynamic 3D Autogen Vegetation remained unmarked
Water Detail: High (was Ultra)
Bathymetry remained enabled
Reflections remained unchanged with marks on all except vegetation
Special effects detail and distance remained High.
Enable HDR Lightning remained marked
Brightness: 1.30 (was default)
Bloom 0.20 (was default)
Saturation: 1.15 (was default)
Dynamic Reflections: Off (was Ultra)
Dymamic Lightning, Langdinglights illuminate ground and Display lens flare remained marked.
Shadow quality: High (was Ultra)
Shadow draw distance remained Ultra.
Casting and receiving shadows remained unchanged (all boxes marked except Vegetation receive, Particles cast and No shadow flagged Content cast)
Cloud draw distance 60 mi (was 110mi)
Cloud coverage density remained at maximum.
Aviation traffic and Land and Sea traffic remained unchanged, all drawers about in the middle at 50-60%.
Changes in AS4:
Maximum cloud layers limited to 3 (was 5)
Maximum cloud draw distance remained at 100mi
Minimum cloud draw distance reduced to 65mi (was 90mi).
And what was the results?
1st: A silent sigh of P3D with which it faded to desktop (CTD) without any error message just at the beginning of the test (I had just set the scenario date back to mid november, as snow-covered autogen trees in a snow-covered country are harder to see than their green pendants).
2nd: Another 'silent CTD' after exactly 30 minutes of flight, just crossing above Kansas City - an issue of the video driver?
3rd: (a successful undisturbed flight of over 60 minutes):
And now for the most important: AUTOGEN DID _NOT_ POP UP IN PATCHES
throughout the whole flight !!!
I needed a zoomfactor of 6+ to see the 'end' of the autogen-world, where trees and buildings slowly faded in!
A framerate in the mid-30s (instead of about 15) when outside a city, 15fps (instead of 8-10) in e.g.Kansas City.
No lag in loading autogen 'behind' Kansas City.
And the best is: I didn't have the feeling that I've missed any autogen tree, concerning the autogen building density I only noticed more blank spaces in densely covered city areas than in my last flight.
Fazit: it seems that - for me and my machine - I've solved the riddle about popping up autogen (maybe we always tried to turn the wrong knobs). Please don't go for me, when YOUR machine and P3D installation does not give the desired results.
And (for safety reasons): BACK UP all the ...\Lockheed Martin\Prepar3d v4\... folders (simply copy them to e.g. ...\Lockheed Martin\Prepar3d v4.bak\... - so you can step back in case of desaster.
Credits should go to Mathew Webb from FTX Forum; here's his explanatory video: https://ruclip.com/video/nN0rUxMiIME/pr ... e-sky.html