June 11, 20214 yr 7 minutes ago, Druce said: Can someone please write this step by step what to do? This has been explained again and again, suggest you read the post from the beginning 😉 Bert
June 11, 20214 yr I am using EA enabled vol clouds off how do i eliminate the white film beyond clouds like thick haze with latest ASP3D beta p3d v5.2 thanks mike
June 11, 20214 yr 1 hour ago, SergioN said: My experience may help you. First I made a client and content update to 5.2, it was bad, got DXGI errors every session and few other issues like effects not getting installed, very strange. So decided to make a fresh install deleting every p3d folder as described in p3d's PDF. All fixed for me. So may be you could try this, hope it helps. (I'm with GTX 1080 Ti though) I only deleted the P3d.cfg and the shaders, but installed all three components (complete P3d install) - maybe will try again and delete all dedicated folders. Greetings Andrew Bowler
June 11, 20214 yr 14 hours ago, PATCO LCH said: Heck of a lot more than two days amigo. Try two weeks and a lot of hair pulling if I had any to pull. The client, content, scenery works a treat for me. I gurantee you there will still be plenty of posts in 2 weeeks time, mentioing black squares, shaders buggered, sims that dont start,ai proformance issues etc etc etc. I rather spend 2 weeks to have a nice fresh install for the next year until 5.3 or whatever is next than all of the above issues. just saying....
June 11, 20214 yr 3 hours ago, airlinetycoon said: I only deleted the P3d.cfg and the shaders, but installed all three components (complete P3d install) - maybe will try again and delete all dedicated folders. I wonder if issue is related to AMD card. I am having very similar issue, basic planes install , complex planes ctd every tiime. I am using amd rx580 card. I also have a windowed mode issue, The planes always spawn iin windowed mode. I installed client ,content and scenery, reinstalled client and deleted shaders folder again. I5 9600k@ 4.8ghz rx580 limping-along 2x 23" 1080P Monitors
June 11, 20214 yr 5.2 is broken. This is what I get with the PMDG 777. Also, frame rates are so low that I can't do anything (I can't even pan the camera). I uninstalled client, content and scenery and reinstalled. Images here... https://imgur.com/X13rxpPhttps://imgur.com/IJknX7qhttps://imgur.com/6bLA2iUhttps://imgur.com/7ZGXrUY AMD Ryzen™ 9 9900X3D, AM5, Zen 5, 12 Core, 24 Threads, 4.4GHz, 5.5GHz Turbo 64GB (2x32GB) DDR5 6000MHz Corsair Vengeance 32GB GeForce® RTX 5090 Graphics Card
June 11, 20214 yr Re-uninstall client. Delete C:\Program Files\Lockheed Martin\Prepar3D v5\ShadersHLSL, uninstall/disable envshade, re-install client Vincent Rouleau AMD Ryzen 7950X3d / 64.0GB G.SKILL Neo DDR5 6000 / Gigabyte GeForce® RTX 4080 16Gig / / Samsung C49RG9 49' /ASUS PB287QQ ‑ 27" UHD / AGAMMIX 2TB / Samsung 970 PRO 1TB / PNY SSD 1TB / Windows 11 / Gigabyte B650M Elite Motherboard
June 11, 20214 yr I believe I found my solution - I ticked in the P3d shadow settings "particles" on. When I disable this option, no Device Hung so far. Greetings Andrew Bowler
June 11, 20214 yr 8 minutes ago, airlinetycoon said: I believe I found my solution - I ticked in the P3d shadow settings "particles" on. When I disable this option, no Device Hung so far. I thought it was vegetation that was the issue? Edited June 11, 20214 yr by Ray Proudfoot Image removed in quoted post
June 11, 20214 yr 2 minutes ago, fluffyflops said: I thought it was vegetation that was the issue? No, vegetation ticked is ok. Only when "particles" are enabled I get the device hung immediately. Greetings Andrew Bowler
June 11, 20214 yr Seriously done a lot of tidying up, loading, reloading and reinstalling a variety of files fo 5.2 (wasted a day it seems). Narrowed down the problem to three areas so 1. Anybody had any issues with FSL Spotlights and 5.2. For older models it appears to crash the sim newer ones not at all. That is removing the spotlights ini stopped the CTD for that model only. Why one model and textures is ok but another results in a CTD with FSl spotlight ini is unknown at the moment. EA and the dynamic lighting causing a clash? 2. Not sure why but some older sound files pre V5 (some back to MS2004) that played ok in FSX and 5.1 now seem unstable in 5.2 reverting to an alternate sound package, fixed some issues here. I know there are changes to 5.2 and the way it is handling sound. 3. Still have a mysterious hide and seek issues with one addon - picked up by P3D and allowed - but will not appear in the vehicle menu even though the previous sim load, there it was and working? As you will have guessed these are all older models that have been reworked first into FSXA and then into P3DV5 - so can of worms for these really.
June 11, 20214 yr 1 hour ago, vincentrouleau said: Re-uninstall client. Delete C:\Program Files\Lockheed Martin\Prepar3D v5\ShadersHLSL, uninstall/disable envshade, re-install client I did a total uninstall and reinstalled using the P3D one-stop installer and it seems to have worked...thank you! AMD Ryzen™ 9 9900X3D, AM5, Zen 5, 12 Core, 24 Threads, 4.4GHz, 5.5GHz Turbo 64GB (2x32GB) DDR5 6000MHz Corsair Vengeance 32GB GeForce® RTX 5090 Graphics Card
June 11, 20214 yr 1 hour ago, BWBriscoe said: 5.2 is broken. This is what I get with the PMDG 777. Also, frame rates are so low that I can't do anything (I can't even pan the camera). I uninstalled client, content and scenery and reinstalled. Images here... https://imgur.com/X13rxpPhttps://imgur.com/IJknX7qhttps://imgur.com/6bLA2iUhttps://imgur.com/7ZGXrUY Same problem here. I will try to uninstall and re-install client. Mark CYYZ
June 11, 20214 yr 1 minute ago, MarkW said: Same problem here. I will try to uninstall and re-install client. The solution was posted above. You need to delete your ShaderHLSL folder and then reinstall the client. Basically, you have incompatible shaders and you need to clear them out so the 5.2 client can install the new defaults.
June 11, 20214 yr 15 minutes ago, Chapstick said: You need to delete your ShaderHLSL folder and then reinstall the client. Is this your recommendation because the ShadersHLSL folder could have been modified by some third party software, thus leaving spurious shader files in there after uninstalling the Client? Edited June 11, 20214 yr by Reader
Archived
This topic is now archived and is closed to further replies.