Oh god, this "off on" debate is so confusing that I even don't wanna update ASN to the latest beta patch to try it. 

If it ain't broke, don't fix it.

 

If maximum visibility is a problem for you, give it a try otherwise you can wait for the official release and just ignore the option.

 

I see some people treating this as a "tweak" that will improve the experience. It is not and does not EXCEPT on those systems experiencing an issue.

 

If you don't have the issue or if you don't know if you have the issue - ignore the option.

 

Vic

If it ain't broke, don't fix it.

 

If maximum visibility is a problem for you, give it a try otherwise you can wait for the official release and just ignore the option.

 

I see some people treating this as a "tweak" that will improve the experience. It is not and does not EXCEPT on those systems experiencing an issue.

 

If you don't have the issue or if you don't know if you have the issue - ignore the option.

 

Vic

 

Yeah, something like that. b5921 is working pretty good here, no visibility issues so far, at least I think there isn't. The thing is, I don't know anymore the visual difference between broken and proper visibility with ASN. I experimented to much that I've lost a clue what is right/wrong visually.

Got the latest update. FPS dropping to 15-16 just before going into clouds and still being low through the clouds. Turned off ASN and got back up to 50-60 fps. Any solution to this?

Got the latest update. FPS dropping t5o 15-16 just before going into clouds and still being low through the clouds. Turned off ASN and got back up to 50-60 fps. Any solution to this?

Unchecked box in Multiple Visibility Layers or something like that in ASN.

Same here, latest update trashed my fps. Looked for your suggestion and could not find any phrase or setting like that.

Same here, latest update trashed my fps. Looked for your suggestion and could not find any phrase or setting like that.

Sorry I'm away from my computer at the moment but if you have the latest ASN beta patch 5926 there is an extra tab in the settings under Visibility.  Its called Multiple Visibility Layers.  By default the box should not be checked;  if it is checked you may run into performance issues with Overcast conditions.

 

I have mine unchecked.  Here is a link to the description:

 

http://www.hifisimtech.com/forums/showthread.php?5872-ASN-for-P3D-Open-beta-update-March-24-2016

 

This can probably explain better than myself.

Here is a link to the description:

 

http://www.hifisimte...e-March-24-2016

 

This can probably explain better than myself.

 

Specfically, check out this line from that link:

 

 

NOTE: Some users report reduced performance in P3D 3.2 related to 3rd-party graphics add-ons which change shader code to increase cloud sprite size/volume. Please contact your graphics add-on provider support resources for information regarding how to disable this shader code adjustment to restore performance. Uninstalling/reinstalling the "Content" installer should also restore your shader code. After applying such fixes, it is important to clear your shader cache. This issue is not related to ASN.

 

 

and these threads:

http://www.avsim.com/topic/485428-new-rex-feature-feedback/

http://www.avsim.com/topic/485159-so-whats-going-on-at-rex/page-6#entry3390974

 

Seems like the cloud.fx cloud sprite size is being altered to 0.67 from the P3D default of 0.50.  REX has identified this and will be changing its UI to allow users to "size" their sprites.

 

A setting of 1.00 is twice the size of 0.50, so you can interpolate what a 0.67 size will do to your FPS.  I've manually changed mine back to 0.50 in my cloud.fx file and the performance difference is quite noticable.

Specfically, check out this line from that link:

 

 

and these threads:

http://www.avsim.com/topic/485428-new-rex-feature-feedback/

http://www.avsim.com/topic/485159-so-whats-going-on-at-rex/page-6#entry3390974

 

Seems like the cloud.fx cloud sprite size is being altered to 0.67 from the P3D default of 0.50.  REX has identified this and will be changing its UI to allow users to "size" their sprites.

 

A setting of 1.00 is twice the size of 0.50, so you can interpolate what a 0.67 size will do to your FPS.  I've manually changed mine back to 0.50 in my cloud.fx file and the performance difference is quite noticable.

 

Thank you. I located the cloud.fx file but im unsure on what i should change. Is it this one?

 

    float4x3 quad = (float4x3)0;

    float height = packedCorner.y;

    float width = packedCorner.x;

    GetScreenQuadPositions(quad, width*0.67, height*0.67);

 

Is that the one i should change to 0.50?

 

 

GetScreenQuadPositions(quad, width*0.67, height*0.67);

 

Yep...that would be the one.

 

Don't forget to delete your shader folder in Users\[YOURNAME]\AppData\Local\Lockheed Martin\Prepar3D v(x) and allow it to rebuild.

Yep...that would be the one.

 

Don't forget to delete your shader folder in Users\[YOURNAME]\AppData\Local\Lockheed Martin\Prepar3D v(x) and allow it to rebuild.

 

Alright, thanks! Hopefully the fps will get back up again

Alright, thanks! Hopefully the fps will get back up again

 

No guarantees.  Each rig is different, but it helped on mine.  I also don't use SGSS in NI, which can also affect FPS.

Okay i am also in the club today, but is this the trick with B5921 to sum things up ?

 

 

From earlier in this thread"

 

"I located the cloud.fx file but im unsure on what i should change. Is it this one?

 

    float4x3 quad = (float4x3)0;
    float height = packedCorner.y;
    float width = packedCorner.x;
    GetScreenQuadPositions(quad, width*0.67, height*0.67);

Is that the one i should change to 0.50?

 

 

 

 

BTW SLI is really rocking with 4XSGSS and NI@29FPS for now

 

Michael Moe

No update from REX yet?

 

 

 

 

BTW SLI is really rocking with 4XSGSS and NI@29FPS for now

 

Michael Moe

Only I can not block the FPS with the SLI, otherwise I have stutters? 

No update from REX yet?

 

 

Yes! a while ago.

 

Update REX TD and you can define your own cloud scale, or leave at default.

 

 

It was very naughty of REX to change the scale with out telling users though