Shader mod remnants--serious performance hit in v5.2

[Bob Scott 7,720]

For those doing module upgrades to P3D v5.2, be advised that if there are any remnant shader modifications left behind from earlier versions, they can cause severe performance degradation in v5.2

It's highly recommended to delete your ShadersHLSL folder (located in your P3Dv5 root folder) just prior to installing the new client module so that no previously modified shader files are left behind to booger up the new sim.

If you've already installed v5.2 and find yourself having performance issues, uninstalling the client, deleting the ShadersHLSL folder, and reinstalling the client has worked for many others to eliminate the problem.

[coastaldriver 919]

Correct. Note - also I found that using the FSL Spotlights addon to change VC lighting etc, will now cause CTD with 5.2 if the ini file is activated via the FSL GUI. 

Edited June 11, 2021 by coastaldriver

[Nemo 1,305]

On 6/11/2021 at 6:52 PM, w6kd said:

If you've already installed v5.2 and find yourself having performance issues, uninstalling the client, deleting the ShadersHLSL folder, and reinstalling the client has worked for many others to eliminate the problem.

Deleting the folder and using the repair function of the installer was good enough in my case.

[davenicoll 104]

On 6/12/2021 at 9:29 PM, Nemo said:

Deleting the folder and using the repair function of the installer was good enough in my case.

+1

[Darcy 63]

On 6/11/2021 at 10:52 AM, w6kd said:

For those doing module upgrades to P3D v5.2, be advised that if there are any remnant shader modifications left behind from earlier versions, they can cause severe performance degradation in v5.2

It's highly recommended to delete your ShadersHLSL folder (located in your P3Dv5 root folder) just prior to installing the new client module so that no previously modified shader files are left behind to booger up the new sim.

If you've already installed v5.2 and find yourself having performance issues, uninstalling the client, deleting the ShadersHLSL folder, and reinstalling the client has worked for many others to eliminate the problem.

Yep had to do this and all good now.

 

Thanks