Well, I did not include Rob's last post as this is the answer he gave for each and every thread existing in regard of this issue since v4.0 is out. And guess what, 4.1 had the issue, v4.2 had the issue and now also v4.3 has it. I bet that v4.4 will also have it, maybe v5.0 will be improved...

To me, that's not really supportive. He will give us more info if they have it. So why closing the thread? Theoretically it would still be possible that the one or other user finds a workaround or even the reason of the issue. Like this, it will be simply ignored again...

Ok, guys, this might be Placebo or not, but the following struck me yesterday: I did a flight from AS LEPA to AS LSZH with the AS A321, using ProATC/X, ActiveSky weather and REX live texture replacements. And I used my standard settings with autogen draw distance on high. And guess what? My autogen was fully loaded when approaching LSZH. As it should be. Now, the interesting Thing is, what was different? This:

1. I installed the fix from FSDT that corrected an error obviously already present from the beginning of the 64bit era. The bug was located in the Addon Manager.

2. I used .bat files that moved ProATC/X, ActiveSky and REX off the first core to cores 5 and 6 only.

So, it seems that those two lttle things did reduce the load on my sim that much (along with a fixed frame rate of 30, of course), that autogen loading was not hampered anymore and could keep up with the sim even on the setting "high".

I’m hopeful that the GSX will be a big help with this late autogen loading (since Umberto said the bug was there from the beginning of v4), but we’ll see.

James

I am pretty sure that with those three things (FSDT update, locked frame rate and .bat files for all addons running outside the sim), the load can be reduced enough that the autogen issue is prevented. However, I am aware that if I would now think to turn up the settings again, I would sooner or later run into the same problem again.