Hi, in v4.1 I still have autogen loading issues when arriving at large autogen areas: if autogen drawing distance is set to higher than medium, the autogen loads at the last moment, just when I overfly the area. And it is loaded in patches, not gradually. This was highlighted way before v4.1 was released and LM said it was being investigated...

You may need to tune various settings to achieve the desired level of performance on your hardware. Medium autogen settings in v4 are higher than v3. We are continually making performance improvements with each update and various improvements to the autogen system are being planned.

Sorry but it's quite a shame that in v4.1 many minor features have been addressed, while important issues like this one are still the same as in v4.0. The nice feature of autogen extending much further than in v3 is at the moment useless if you have no autogen loading at arrival...
Best regards,
James

I confirm it 3770K @4.5GHz, GTX 1060-6, SSD
I'm generally surprised by the principle of caching. Why on the external camera I can look at the object, then turn away, and when I look again - the textures start to load again. What for??

I confirm it 3770K @4.5GHz, GTX 1060-6, SSD
I'm generally surprised by the principle of caching. Why on the external camera I can look at the object, then turn away, and when I look again - the textures start to load again. What for??

This above for me too, even with twin 1080ti in SLI mode.

I wish they'd spent more time fixing these old problems instead of doing stuff like VR, which FlyInside does waaay better.

I have done research on this and found that unlimited fps settings cause it. Lock your fps in game and your autogen will not disappear or load late. It must be a bug that would be good to have patched in a hotfix.

Well, now you know where the loss in 7-10 FPS goes into. That's because if you limit your FPS internally, you activate the fiber frame time fraction "tweak", which has a default value of 0.3. If you use unlimited FPS, P3D uses a setting of 0.01. The higher the FFTF value, the more resourced does the CPU dedicate to scenery loading, but the lower the frame rate. This explains the loss in frame rate and the earlier loading of autogen.

That is unfortunate. I am using v3, so I am not familiar with v4, but I know that limiting frames in v3 and making sure that the system can handle the maximum FPS results in a quicker scenery load at high speeds. I hope other users have some more tips.

Just as an info: I never had this issue. Then I installed PILOT's FS Global 2018 mesh and since then, my autogen is gone at arrival... Will see if rebuild of the prepar3d.cfg helps to eliminate this issue again for me... then I will test without the mesh and see if it helps...

A recent observation on autogen:
I continued a VFR flight, following the IS70 westward, having started just west of St.Louis; aircraft is the Carenado Cessna C227 (not too much system depth), airspeed about 170kn, flightlevel about 500-700ft above ground; weather by HIFI's AS4 (cloudless sky). All scenery drawers maxed out, the drawers for autogen traffic at 45%.
For about 90 minutes it was a more or less smooth flight (about 13-15 FPS, as I'm used to) - no problems with autogen, which seemed to 'grow' somewhere far beyond the horizon, so no patches were discernible.
But...
When I reached Kansas City - still following the IS70 - FPS dropped to 7-10, autogen got lost in favour of the individual 3D scenery, and did not recover to normal afterwards. From here on the autogen loaded either just behind or just ahead of my position, of course in visible patches. Sometimes I even had to pause the sim, so the autogen could catch up with loading.
The strange thing is, that, even when Kansas City was no longer visible behind me, the situation did not improve for the rest of the flight, which brought me westward as far as Junction City.
Michael.

I can confirm this problem too.
I am on a high end 8700K with a GTX 1080 TI and this autogen loading problem is a real issue.
I have reduced autogen radius and autogen buildings to medium and low and it is still a problem.

This is a mojor problem with V4.1.
Will LM cofirm a fix available soon.