Sign in to follow this  
TheBoom

Blurries with high autogen

Recommended Posts

Anyone else noticing blurries and scenery popping with maxed out LOD and autogen in 3.2?

 

I never had this problem in 3.1 and I know they changed the building draw distance in 3.2but never expected it to cause this much of a performance loss when it comes to scenery rendering.

 

All settings are similar to 3.1. A reinstall changed nothing either.

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

I too struggle with this with 3.2. Very blurry textures and autogen "circles" around my airplane. I haven't been able to find a solution yet. But my 3.1 stall was crisp and beautiful. Sorry, no real answer for you, but your not the only on in the boat.

Share this post


Link to post

It's fine. I'm just baffled at the performance difference. Using locked fps some of the problems go away but at the cost of fps in higher density areas.

 

3.1 was near perfect. Something in 3.2 is crippling the experience and I can't seem to find out what.

Share this post


Link to post

I think its ASN.. I have the same. Turning on Voluemetric Fog while at 30000ft helps

Share this post


Link to post

I already have volumetric fog on at all times. I doubt it's ASN since its do to with scenery rendering. It's something to do with P3D itself.

 

I have tried it with ASN off and clear skies as well.

 

There is however a slight possibly it may be Orbx related.

Share this post


Link to post

I don't think it's ASN as I use OPUS and have the same issues. Even with clear weather, I get really bad blurries. 

Share this post


Link to post

Had a little time today so I went ahead to do some testing. Saved a flight in the Airbus somewhere between LOWW and EGCC.

 

My initial conclusion was wrong. Even with autogen turned down there is popping and blurries. In fact I deleted my cfg and shaders and let P3D rebuild them and still no difference. Even without a manual affinity mask or any other tweaks. Made no difference unlimited or fixed fps and FFTF either.

 

Which mean the problem almost definitely is within 3.2 itself?

 

Guess the only thing left to do is roll back to 3.1 and see how it pans out.

 

I also tested NV driver 361.43 which improved smoothness a little and lessened the load on the GPU for some reason.

Share this post


Link to post

I believe there is something that was changed in 3.2 that has caused blurries to appear in certain situations. If I cycle views at the Tower View and then cycle forward, the next view is a blurry mess - it clears up quickly but it is annoying. I have read similar comments from users on varying systems. No actual proof but I'm getting the perception that it has something to do with the way P3D is handling clouds, etc. This is with or without and weather programs activated.

 

Prior to 3.2, I rarely had even the smallest of blurries. This is with no changes to my system and/or settings. I tried a few adjustments with little effect so I've gone back to my default settings. I'm hoping the changes in V 3.3 will correct some of these.

 

Vic

Share this post


Link to post

Interesting observation Vic. I have also re-acquired the temporary 'blurries' when cycling certain views and had just assumed that I must have inadvertantly changed something although, hand-on-heart, I know that I haven't. As you say - let's see what V3.3 brings.

Share this post


Link to post

Neg TP - on one system w7/UTX/GEX and second system w10/FTX Global - same issue.

 

What's relevant to me is that I made no other changes than installing 3.2.3 - I am using the same settings as 3.1.

 

And, it's only very noticeable if I'm cycling views - just straight flight with no view changes is just fine.

 

 

Vic

Share this post


Link to post

Yes I've noticed that cycling views makes it worse but even in a fixed view I get them. Not as many but still noticeable and they don't exactly clear up fast.

Another thing I noticed were that the cloud shadows were also popping up. I initially thought that the processor could not keep up with the amount of data it had to load with AM 116 but 252 yields the same result. What's interesting is that even with 252 all 4 cores are maxed out at 100% most of the time whereas with 3.1 and an AM of 116 the 2 cores were never higher than 80-90%.

 

 

 


Is this with default scenery?

 

With Orbx Global and Vector and Open LC Europe. Same settings in Vector as I had in 3.1. Something tells me default scenery is going to be the same though.

Share this post


Link to post

Are all those problems occur with FPS set to unlimited? 

Share this post


Link to post

I have v2.5 installed and I have this blurries also. Very very slow texture loading

Share this post


Link to post

Are all those problems occur with FPS set to unlimited?

 

Both fixed and unlimited.

 

I have v2.5 installed and I have this blurries also. Very very slow texture loading

2.5 wasn't that bad. 3.0 I had none. 3.2 is worse than 2.5 for some reason.

Share this post


Link to post

Might be on to something.

 

Removed AM, changed Autogen_Batch_Lod=2 (by default) to 1 and fixed fps to 33. Blurries seem to be gone. Also added Autogen_Tree_Lod=1 and the trees popping seem to be gone. Not sure if the tree LOD entry still has any effect but worth a try.

 

Ultimately it may have been a case of 116 simply not providing enough processing power for the scenery.

Share this post


Link to post

Might be on to something.

 

Removed AM, changed Autogen_Batch_Lod=2 (by default) to 1

 

 

This however will increase the Autogen and therefore the load on your system, making the likelyhood of blurries greater. Setting it to zero gives maximum Autogen LOD, whereas higher numbers, up to a max of eight, will thin it out and ease the load.

 

More likely the AM was not optimal for terrain loading.

Share this post


Link to post

This however will increase the Autogen and therefore the load on your system, making the likelyhood of blurries greater. Setting it to zero gives maximum Autogen LOD, whereas higher numbers, up to a max of eight, will thin it out and ease the load.

 

More likely the AM was not optimal for terrain loading.

You're right. But I think changing the batch LOD reduced the popping since it loads more in the preload or something along those lines.

Share this post


Link to post

I guess that might help after an initial load, but it may affect loading later in the flight as the terrain and Autogen try to keep up. In general if you are getting slow loading Autogen (pop in) or terrain (blurries) then it indicates settings are too high for the system, so tweaking them higher can only lead to more problems. I can't say I noticed any change in terrain or Autogen performance in 3.2 over other versions and its certainly no worse.

Share this post


Link to post

I guess that might help after an initial load, but it may affect loading later in the flight as the terrain and Autogen try to keep up. In general if you are getting slow loading Autogen (pop in) or terrain (blurries) then it indicates settings are too high for the system, so tweaking them higher can only lead to more problems. I can't say I noticed any change in terrain or Autogen performance in 3.2 over other versions and its certainly no worse.

I guess it varies from system to system. I had the same exact settings in 3.1 and no issues. 6700k at 4.7 no problem with max autogen. 3.2 is another story. I am trying to figure out a solution instead of turning down settings. If I had to turn down settings to compromise I might as well roll back to 3.1.

 

That being said a new AM and that tweak has almost completely resolved the issue.

 

Regards

Share this post


Link to post

That being said a new AM and that tweak has almost completely resolved the issue.

 

Its certainly is the case that iterations from V2 onward have varied in their need, or sensitivity to AM settings.

 

You should not have to compromise much with your setup that's for sure.

Share this post


Link to post

Yes. It's just that an AM of 116 has recently been advocated so much (myself included) that I have probably been blindsided by it. The fact that it probably isn't going to work for all situations and settings is quite real and more apparent in 3.2

 

Undeniably 116 still produces less stutters and more smoothness prolly cause it's less processing overhead after all.

 

It's back to finding the balance between smoothness and immersiveness.

Share this post


Link to post

An AM setting of 85 in the Config seems to be the optimum de facto for any modern quad core system running P3D. Process Lasso also appears to enhance the capabilities of P3D further if it is nominated as a 'Game' in the options list. 

Share this post


Link to post

An AM setting of 85 in the Config seems to be the optimum de facto for any modern quad core system running P3D. Process Lasso also appears to enhance the capabilities of P3D further if it is nominated as a 'Game' in the options list. 

 

85 will give P3D 4 LPs to use, same as 116, but it will offer one thread per core. Better smoothness but overall same processing power as 116. Blurries are likely to remain.

 

Yes I have P3D classified as a game in Process Lasso.

Share this post


Link to post

In 3.1 I found AM 85 better than AM of 116 (i7 3770 nonK) but with 3.2 I find 116 outperforming 85.

 

One thing I have found with my GTX 960 4 gig, I can usually (when searching for a way of lessening a nagging stutter)  add a bit more load through a scenery adjustment and it will smooth it out. It makes me think that on my card there is a sweet spot located between too much load and too little a load.

 

Just my personal experience.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this