December 6, 20205 yr Anyone else running into DXGI errors with P3Dv5.1HF1? I am having quite a few in circumstances where I am fine in v5.0/4.5. Mainly happens in the FSL Bus but have had one in PMDG NGXu too. Not using trueglass and not anywhere near the VRAM limit... Cheers
December 6, 20205 yr See this forum : multiple threads about it on the first page with suggestions 5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 - MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb - Corsair 5400 case - Corsair 360 liquid cooling set - 3x 75’ TCL tv. 13600 6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb - 1x SSD M2 2800/1800 2TB - 2x Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - FOV : 200 degrees My flightsim vids : https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0
December 6, 20205 yr 14 minutes ago, ah2511 said: Anyone else running into DXGI errors with P3Dv5.1HF1? I am having quite a few in circumstances where I am fine in v5.0/4.5. Mainly happens in the FSL Bus but have had one in PMDG NGXu too. Not using trueglass and not anywhere near the VRAM limit... Cheers Let me guess 1080ti 2080ti 3080ti? Reinstall drivers using studio drivers.
December 6, 20205 yr Author 1 hour ago, GSalden said: See this forum : multiple threads about it on the first page with suggestions Hey mate, which forum? Tried just about every fix I can find and no luck 1 hour ago, fluffyflops said: Let me guess 1080ti 2080ti 3080ti? Reinstall drivers using studio drivers. RTX 3090. Have tried every driver available (not many for the new series) including studio and the same behaviour occurs
December 6, 20205 yr remove trueglass if installed does this relate to turning off vr seen issuses there. Colin hodds I7 9700K,nvidia 3090 ,ssd ,32gig 3200mhz ram ,win10,prep3d
December 6, 20205 yr Author 33 minutes ago, cannow said: remove trueglass if installed does this relate to turning off vr seen issuses there. No addons with trueglass. Have had it once turning off VR but the vast majority are within 5mins of loading a scenario, before even setting up VR
December 6, 20205 yr I found that the Riva Tuner was the cause of my DXGI errors. Removed it completely and so far not had any more of the errors. Asus Maximus Hero XI , i7-8086, 16 Gb RAM, nVidia GTX 1080 ti
December 6, 20205 yr 22 minutes ago, wardp said: I found that the Riva Tuner was the cause of my DXGI errors. Removed it completely and so far not had any more of the errors. Same with Asus gpu tweak software Same with trueglass Both will cause dxgi errors.
December 6, 20205 yr 1 hour ago, ah2511 said: No addons with trueglass. Have had it once turning off VR but the vast majority are within 5mins of loading a scenario, before even setting up VR I have this most times turning of vr this is the only time I have this issue thank you,Jim MSI A520M-A PRO,AMD Ryzen 7 5700X3D 8 Core, 16 Threads 4.1Ghz,Arctic Freezer 36 ARGB Black Edition CPU Cooler,MSI VENTUS 2X Nvidia RTX 4070 12GB Graphics Card,Corsair 32GB Vengeance LPX (2x16GB) 3200Mhz DDR4 Memory,Gigabyte UD750GM 750W Gold Rated Modular PSU,Kingston NV3 2TB NVME M.2 GEN 4 SSD.
December 6, 20205 yr 5 hours ago, GSalden said: See this forum : multiple threads about it on the first page with suggestions Sorry to ask, but what do you mean with "first page" (of what)? - 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).
December 6, 20205 yr A lot of the third-party GPU utilities that do on-screen displays (Rivatuner, Afterburner, Precision X1 etc) do not play nicely with DX12. I use EVGA's Precision X1 and have to turn the OSD off when running P3Dv5...P3Dv4, which uses DX11, has no issues with the OSD when running the same add-ons. Also, I relax the timeout params in the Windows DDM--see https://docs.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys I set TdrDdiDelay to 20 (default is 5) and TdrDelay to 10 (default is 2). 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
December 6, 20205 yr The solution for me was to switch off "Enable Bathymetry". See here: https://www.prepar3d.com/forum/viewtopic.php?f=6315&t=140629&start=90 Karl i9-9900K@5,0 | 32GB 3200 | 2080TI | 4K 55" | MSFS | P3D V5
December 6, 20205 yr Author Have uninstalled MSI etc. I am pretty sure I have Bathymetry on though. Will give this a go
December 7, 20205 yr Author 14 hours ago, kaha said: The solution for me was to switch off "Enable Bathymetry". See here: https://www.prepar3d.com/forum/viewtopic.php?f=6315&t=140629&start=90 Karl Turning off bathymetry seemed to work. I tested at a few locations where I generally get the error and the problem stops if I turn bathymetry off. Thanks Karl!
December 7, 20205 yr 9 hours ago, ah2511 said: Turning off bathymetry seemed to work. I tested at a few locations where I generally get the error and the problem stops if I turn bathymetry off. Thanks Karl! its going to be fixed in v6.3. 🙂
Archived
This topic is now archived and is closed to further replies.