I noticed there were a number of threads on this issue last year and earlier this year, both on Avsim and LM's forums. But to my mind there were never conclusive nor even authoritative answers to what were the causes. Some said it was setting AM, too high settings, it's an Orbx problem, etc. I noticed on the LM forum that no one claiming to be an official LM representative answered what was the problem. (On the A2A forum if you post a problem, someone from A2A responds typically within hours.) I was not really having the problem until I installed v4.4, and now I have it big time. I have tried most of the unofficial solutions,and nothing seems to fix the problem. I am thinking about uninstalling and reinstalling v4.3 for the time being. If someone here is aware that there is a real answer out there, hidden somewhere withing the many threads and responses, I would greatly appreciate hearing it.

 

Unfortunately, too many people ignore this issue and don't complain enough. This issue became visible since version 4.1 came out, I personally complained (and have a post here and on their web recently) about it.

Apparently, LM don't care about it and to my recollection, they said over a year ago that they will look into a solution. Unfortunately, 3 or 4 versions later still the same issue for a large number of people.  

Just a few examples    

https://www.dropbox.com/s/j9uzigilvqnlkzv/slow to load.PNG?dl=0

https://www.dropbox.com/s/lel60ergirqxgov/textures.PNG?dl=0

I asked different people and everyone came with a different suggestion, unfortunately, LM is to fix it.

I agree with you that 4.3 is better from this point of view...…………………..

Check this one, it was too much of inconvenience. I really don't understand why would they block it instead of committing of fixing the issue or just admit it that they unable or unwilling.

I would not have a problem with the last part, but locking the post for a valid and known a problem I have an issue with it. 

https://www.prepar3d.com/forum/viewtopic.php?t=130120&start=45

Edited December 4, 20187 yr by killthespam

I agree the autogen loads too slow. The further you fly from the starting scenario point the longer it takes to load autogen in the distance. On my system I can see a line roughly 15-20NM out in urban areas sometimes less, sometimes further that is very annoying where the autogen - nonautogen dividing line is. I have since lowered my autogen to normal density and turned up load distance to max and terrain radius to max to help. It does help as well as some of the new scenery 4.4 tweaks. But still not where it needs to be. LM needs to improve this a lot.

I have 64GB of DDR4 at 2800mhz running at 12CL. SLI 2080TIs and a TR 2990WX CPU that boosts up to 4.2ghz w/ HT off. P3D is on it's own m.2 2TB 960 Pro SSD and same type of m.2 SSD for OS only (W10). My rig is impeccably maintained. This has been an issue for the last few releases for me.

I agree since around 4.1 was the last time it was decent, seems to have gotten worse.

And unrelated it is unacceptable how that engine sound pitch glitch got through to the release version of 4.4. That is LITERALLY the same sound glitch from FS2000 where when you went into the cockpit after being outside and the engines pitch is higher than slows back down to where it should be. It was fixed in FS2002 and has been fixed since P3D4.3. Whatever they did they brought that old bug out of hiding. While the code has slightly been changed since then, higher sample rates and sound cones, the base sound engine is unchanged since FS2000. So it's entirely probable that glitch could still surface again. Even if it's not the same bug the characteristics are the same as the FS2000 one. Very annoying.

I can’t believe that LM didn’t fix the autogen issue for this release ... I kind of suspected it wouldn’t be fixed because my post questioning this issue was deleted on their forum ...

 

 

The best way to fix autogen loading issues is to set the internal frame rate limiter to other than unlimited. The price will be some FPS but the autogen loads correctly.

4 hours ago, BlueSky31 said:

The best way to fix autogen loading issues is to set the internal frame rate limiter to other than unlimited. The price will be some FPS but the autogen loads correctly.

I tried this. Set to 30 fps. Absolutely no effect on the autogen problem that I can detect.

How are your settings then? With unlimited and autogen draw distance on "medium", the autogen loading late and in patches should be eliminated. With a frame limit inside P3D, you should be able to go higher than "medium", but only if your hardware is capable of. Currently, I use a limit of 30FPS and "very high" (the setting just one notch below max) and I only see autogen loading in extremly heavy scenarios and only at the very end of the view distance. So basically limiting the FPS to 30 almost eliminated the issue (it is still there of course, but not that prominent anymore).

POP_FREE_AUTOGEN=1 does not seem to be functioning anymore - I set my FPS to 20 and on a high visibility day I see the autogen pop in chunks; that was supposed to be fixed.

I remember this working at some point (autogen fading in to view), but not in 4.3 or 4.4, and I wonder if this has something to do with this issue.

Stuff gets fixed and other stuff that was fixed gets broken.

3 minutes ago, pracines said:

Stuff gets fixed and other stuff that was fixed gets broken.

Exactly my thoughts too Paul.

BluSky31 and AnkH, thank you so much for the good intentions. Unfortunately it doesn't fix the problem. 

We just try to hide the issues with different tweaks and try to believe that is ok when actually it's a big problem for many of us starting over a year ago with V 4.1.

This is something very visible and unpleasant, besides this now we have an additional issue with the engine sound.

I would think that after over a year where many of us tried so many tweaks to no end and no success we would not ask too much from LM to fix it!

Unfortunately people got used with this "tweaking" from FSX and find this normal.

LM has a very good potential of doing good things and we should ask from them first  to fix what is broken and then to add the other goodies.

We should remember that this is not a FREE software (we paid individually for each version V1, V2, V3 and V4) and the small updates (fixes) for each version are part of the normal process.

What I found unacceptable is that LM blocked a  series of posts with valid problems regarding the software instead to commit to a fix, that's the biggest problem IMHO.

Let's be real here, when you buy a product for some people will work perfect and for other not, that's why we take that product back to be fixed or else.

 

Unfortunately, that's the consequence of allowing 3rd party add-ons. LM only tracks down problems associated with the base sim. Even then their first suggestion is to use use lower IQ values as they also can't control what hardware is being used.

Jay,

If you don't mind, maybe I'm getting this wrong but we are not talking about 3rd party add-ons or some odd hardware. I'm just looking at vanilla installation within LM minimum system requirements before adding anything else.

Again I'm sorry if I misunderstood your post.  

I was only pointing out that LM either ignores or locks posts when they are redundant versions of previous posts in which the user was told to remove all add-ons and lower their settings. I wasn't responding to your specific issues.

Jay,

That's fine thank you!

Edited December 5, 20187 yr by killthespam

17 minutes ago, jabloomf1230 said:

I was only pointing out that LM either ignores or locks posts when they are redundant versions of previous posts in which the user was told to remove all add-ons and lower their settings. I wasn't responding to your specific issues.

And now they are deleting them ...