May 18, 20197 yr 12 minutes ago, w6kd said: Did you delete your shaders after installing the 4.5 update? Yes I did here: C:\Users\xyz\AppData\Local\Lockheed Martin\Prepar3D v4\Shaders I have same issue with PMDG 747 but not with TFDI B717 and Flightsimlabs a320x. Edited May 18, 20197 yr by pilecan i7-8700K 3.70 GHz, GeForce GTX 1080 Ti, Samsung SSD 840 840 EVO 1TB, RAM 16 GB, Triple Monitors : 2 LG and Planar touch screen PCT 2265 as main monitor, Windows 10 up to date 🙂
May 18, 20197 yr On 4/5/2019 at 12:03 PM, HeartAviation said: System Specs I7700k 4,2GHZ 16GB ram 1060 3GB 1080p 144 hertz monitor gfx card ?
May 18, 20197 yr 2 minutes ago, tooting said: gfx card ? NVIDIA GTX 1080TI i7-8700K 3.70 GHz, GeForce GTX 1080 Ti, Samsung SSD 840 840 EVO 1TB, RAM 16 GB, Triple Monitors : 2 LG and Planar touch screen PCT 2265 as main monitor, Windows 10 up to date 🙂
May 18, 20197 yr i7 8700k 16 GB Edited May 18, 20197 yr by pilecan i7-8700K 3.70 GHz, GeForce GTX 1080 Ti, Samsung SSD 840 840 EVO 1TB, RAM 16 GB, Triple Monitors : 2 LG and Planar touch screen PCT 2265 as main monitor, Windows 10 up to date 🙂
May 18, 20197 yr 5 hours ago, pilecan said: Yes I did here: C:\Users\xyz\AppData\Local\Lockheed Martin\Prepar3D v4\Shaders I have same issue with PMDG 747 but not with TFDI B717 and Flightsimlabs a320x. If you're using a post-processing add-on that alters the stock shaders (PTA, Tomatoshade, Envshade) you need to ensure it's a version that's compatible with 4.5 HF1 and that it was properly installed on top of the default shaders and not over the already-modified shaders put in place by a previous version of the shader mod software. 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
May 19, 20197 yr 12 hours ago, w6kd said: If you're using a post-processing add-on that alters the stock shaders (PTA, Tomatoshade, Envshade) you need to ensure it's a version that's compatible with 4.5 HF1 and that it was properly installed on top of the default shaders and not over the already-modified shaders put in place by a previous version of the shader mod software. After installed 4.5 I updated the shaders the last version of Envshade who is suppose to be compatible with last version of p3d. I dont understand what you mean when you say " previous version of the shader mod software." For now I delete the shaders and install them of Envshade after restore. Texture problem sill there... i7-8700K 3.70 GHz, GeForce GTX 1080 Ti, Samsung SSD 840 840 EVO 1TB, RAM 16 GB, Triple Monitors : 2 LG and Planar touch screen PCT 2265 as main monitor, Windows 10 up to date 🙂
May 19, 20197 yr 3 hours ago, pilecan said: For now I delete the shaders and install them of Envshade after restore. Texture problem sill there... Delete the shaders again, and this time DO NOT use Envshade. Simply use the default shaders without any tweaks that Envshade makes. See if that fixes it? Do make sure that you first restore the default shaders. Benjamin van Soldt Windows 10 64bit - i5-8600k @ 4.7GHz - ASRock Fatality K6 Z370 - EVGA GTX1070 SC 8GB VRAM - 16GB Corsair Vengeance LPX @ 3200MHz - Samsung 960 Evo SSD M.2 NVMe 500GB - 2x Samsung 860 Evo SSD 1TB (P3Dv4/5 drive) - Seagate Barracuda 2TB 7200RPM - Seasonic FocusPlus Gold 750W - Noctua DH-15S - Fractal Design Focus G (White) Case
May 19, 20197 yr I'm guessing that you did not restore the original shaders (including the shader effect files in ShadersHLSL) prior to updating P3D. I don't use Envshade, but I do use PTA, and I know I'm supposed to restore the original P3D shaders prior to a client update. I imagine it's the same with Envshade. See Poppet's post in this thread for a possible solution using a P3D repair installation: http://www.prepared3d.com/forum/viewtopic.php?t=127028 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
May 20, 20197 yr 20 hours ago, Benjamin J said: Delete the shaders again, and this time DO NOT use Envshade. Simply use the default shaders without any tweaks that Envshade makes. See if that fixes it? Do make sure that you first restore the default shaders. Hi Benjamin, I deleted my shaders and not use Envshade after and the problem still there. Very strange... i7-8700K 3.70 GHz, GeForce GTX 1080 Ti, Samsung SSD 840 840 EVO 1TB, RAM 16 GB, Triple Monitors : 2 LG and Planar touch screen PCT 2265 as main monitor, Windows 10 up to date 🙂
May 20, 20197 yr 19 hours ago, w6kd said: I'm guessing that you did not restore the original shaders (including the shader effect files in ShadersHLSL) prior to updating P3D. I don't use Envshade, but I do use PTA, and I know I'm supposed to restore the original P3D shaders prior to a client update. I imagine it's the same with Envshade. See Poppet's post in this thread for a possible solution using a P3D repair installation: http://www.prepared3d.com/forum/viewtopic.php?t=127028 Hello, I tried Poppet's solution and I updated my NVDIA drivers and the problem still there. I dont understand why I have this problem with PMDG 747 amd QW787. Yes its true I didn't restore the original shaders and shader effect files. The solutions for now its restore them and reinstall P3D 4.5? i7-8700K 3.70 GHz, GeForce GTX 1080 Ti, Samsung SSD 840 840 EVO 1TB, RAM 16 GB, Triple Monitors : 2 LG and Planar touch screen PCT 2265 as main monitor, Windows 10 up to date 🙂
May 20, 20197 yr 1 hour ago, pilecan said: Hi Benjamin, I deleted my shaders and not use Envshade after and the problem still there. Very strange... 1 hour ago, pilecan said: Yes its true I didn't restore the original shaders and shader effect files. The solutions for now its restore them and reinstall P3D 4.5? Hence why in my post I highlighted to restore the original shaders, then test again without re-applying nay sort of Envshade tweaks. The issue is that Envshade changes the source profiles of the Shaders, so merely getting rid of the xompiled shaders, will not get rid of the Envshade tweaks. You have to restore the default Shader profiles, so that P3D can recompile the shaders based on those default profiles. Otherwise you'll just end up recreating the Envshade-tweaked Shaders. Benjamin van Soldt Windows 10 64bit - i5-8600k @ 4.7GHz - ASRock Fatality K6 Z370 - EVGA GTX1070 SC 8GB VRAM - 16GB Corsair Vengeance LPX @ 3200MHz - Samsung 960 Evo SSD M.2 NVMe 500GB - 2x Samsung 860 Evo SSD 1TB (P3Dv4/5 drive) - Seagate Barracuda 2TB 7200RPM - Seasonic FocusPlus Gold 750W - Noctua DH-15S - Fractal Design Focus G (White) Case
May 20, 20197 yr 40 minutes ago, Benjamin J said: You have to restore the default Shader profiles, Im not sure to know how to restore the default Shader profiles. I know that Envshade have an option for this. I use it and nothing changed. Thanks again Pierre i7-8700K 3.70 GHz, GeForce GTX 1080 Ti, Samsung SSD 840 840 EVO 1TB, RAM 16 GB, Triple Monitors : 2 LG and Planar touch screen PCT 2265 as main monitor, Windows 10 up to date 🙂
Archived
This topic is now archived and is closed to further replies.