Ok so I thought I could solve these by myself but apparently not.

 

Ever since upgrading from 3.1 to 3.2 I have a few problems.

 

Deleted and installed client and content only. Backed up autogen folder and copied over once done.

 

No changes in settings/tweaks except for removing 2x SGSS AA in NVI.

 

 

1) Blurries and scenery popping.

 

Using the same exact AM of 116 as in 3.1 but the sim is a lot more stuttery. Also I notice the scenery threads at 90-100% most of the time whereas in 3.1 they peaked at 80-90%. As I've mentioned there are no other changes in settings.

 

http://postimg.org/image/dagq5i4x1/

 

Any ideas Steve?

 

 

2) MSAA

 

2x MSAA and the GPU gets pegged at 99% most of the time even in clear skies. This causes stutter or converted into input lag/delay if I set pre rendered frames to 1 in NVI. Previously only the combination of 2xMSAA and 2xSGSS in dense clouds would cause this behaviour.

 

 

3) Pockets of water shimmering excessively

 

Some areas of water shimmer and distort as if its a mirrored reflection of the water itself. This happens at low altitudes when flying.

 

I thought that 3.2 was supposed to better but oh well.

 

I'm already considering a complete reinstall. My guess is something went wrong with the content installation. Also I can't tell if the scenery is default or ORBx although I have updated the objectflow and checked that the ORBx scenery is enabled in scenery.cfg.

 

There are also some flickering textures which I can live with but i'm not sure if they are related to these problems.

 

Any help would be greatly appreciated, although I'm beginning to think the best option is a full reinstall.

 

Regards,

Shanan

Ok so I thought I could solve these by myself but apparently not.

 

1. Did you clear your shaders?

2. I would try a clean install using DDU (http://www.guru3d.com/files-details/display-driver-uninstaller-download.html) to remove the graphics drivers and installing the most current driver (http://www.guru3d.com/files-details/geforce-364-51-beta-driver-download.html)

 

Also, I would advise to run all 3 installers. I know it's not the easiest, most convenient route. But it eliminates any potential issues. I did all three and am very happy. The only extra work was reinstalling FTX Global, which in the end, isn't that big of a deal. 

1. Did you clear your shaders?

2. I would try a clean install using DDU (http://www.guru3d.com/files-details/display-driver-uninstaller-download.html) to remove the graphics drivers and installing the most current driver (http://www.guru3d.com/files-details/geforce-364-51-beta-driver-download.html)

 

Also, I would advise to run all 3 installers. I know it's not the easiest, most convenient route. But it eliminates any potential issues. I did all three and am very happy. The only extra work was reinstalling FTX Global, which in the end, isn't that big of a deal.

 

I use the shader cache version tweak and I changed the number so I guess that should have done it.

 

So I should try installing scenery alone instead of a full reinstall? I just have a feeling something got corrupted.

 

 

I use the shader cache version tweak

 

Clear them anyway. 

 

 

 

So I should try installing scenery alone instead of a full reinstall?

 

I would...

Thanks, will try doing those tonight and see how it goes.

Deleted the shaders folder, cleaned GPU drivers with DDU and reinstalled them.

 

I have one question though

 

After installing scenery.msi I've reinstalled Global. Must openLC and vector be reinstalled as well?

 

As for Rex textures should they be reapplied?

1. Did you clear your shaders?

2. I would try a clean install using DDU (http://www.guru3d.com/files-details/display-driver-uninstaller-download.html) to remove the graphics drivers and installing the most current driver (http://www.guru3d.com/files-details/geforce-364-51-beta-driver-download.html)

 

Also, I would advise to run all 3 installers. I know it's not the easiest, most convenient route. But it eliminates any potential issues. I did all three and am very happy. The only extra work was reinstalling FTX Global, which in the end, isn't that big of a deal. 

 

Ok so cleaning the drivers and clearing the shaders solved the MSAA problem. But the blurries are still there and whats worse is now I have mountains floating in the sky. CPU threads doing the scenery are still pegged at 100% or close to that.

 

Heres a snapshot of the texture glitches (mountains in the sky) and blurries (notice the grass) in the default carenado at low altitude :

 

http://postimg.org/image/rgdv82vs5/

I think those mountains in the sky are just the tops of mountains appearing above a haze layer. I see that too with ASN. Don't know if it happens with other weather engines.

 

For the blurry textures you could try limiting the frame rate to see if that helps.

Don't apply REX yet until they update.

I'm in the same boat as you unfortunately Shanan.

 

The v3.2 upgrade has given me noticeable stuttering, slow loading autogen and blurries.  I'm considering a clean install this coming weekend.

I did a clean install and gave me a perfect sim so far.

Thanks for all the replies guys.

 

I tried limiting frames and nothing changed. Though I did not try it with the FFTF tweak.

 

You're probably right about the mountains. I think it looks that way because the Rex clouds aren't loading. I never saw this before in 3.1 with ASN.

 

My initial thoughts were that it might be Rex. But I don't see how it could affect autogen and scenery loading. As far as I know it only affects the clouds?

 

Seems like the only course of action left is a full reinstall. Will probably get to it and pray for the best. Worst case scenario I might have to revert to 3.1.

 

Regards,

Shanan

Thanks for all the replies guys.

 

I tried limiting frames and nothing changed. Though I did not try it with the FFTF tweak.

 

You're probably right about the mountains. I think it looks that way because the Rex clouds aren't loading. I never saw this before in 3.1 with ASN.

 

My initial thoughts were that it might be Rex. But I don't see how it could affect autogen and scenery loading. As far as I know it only affects the clouds?

 

Seems like the only course of action left is a full reinstall. Will probably get to it and pray for the best. Worst case scenario I might have to revert to 3.1.

 

Regards,

Shanan

 

I have read more than a few comments on Facebook about people rolling back to 3.1 because of issues they couldn't resolve. 

He's a work around for soft clouds. Don't use the program to install them. Just go to the corresponding texture folder and drop it into the P3D texture folder. That way you avoid it installing the broken cloud.fx file.

That's not "official" but that's what I did and it's working well.

I have read more than a few comments on Facebook about people rolling back to 3.1 because of issues they couldn't resolve.

 

That's odd cos almost everyone at avsim seems to be having a good time with 3.2.

 

He's a work around for soft clouds. Don't use the program to install them. Just go to the corresponding texture folder and drop it into the P3D texture folder. That way you avoid it installing the broken cloud.fx file. That's not "official" but that's what I did and it's working well.

Thanks. Will try that and see if it makes any difference. But probably not since it's just a fix for clouds.