June 11, 20214 yr 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. Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
June 11, 20214 yr 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, 20214 yr by coastaldriver
June 12, 20214 yr 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. - Harry 9800x3D (Strix x870e-E) - 64GB RAM (DDR5 6000, CL 30) - RTX 5090, 34'' 1440p OLED HDR - Windows 11 Pro (1TB M.2) - MSFS 2024 (MS Store, 4TB M.2).
June 15, 20214 yr 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
June 15, 20214 yr 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
Archived
This topic is now archived and is closed to further replies.