September 1, 20205 yr Hey guys so I am getting this error still after I thought I had fixed it by disabling full screen optimization. p3d v5 hf2 its only happening when I fire up the qw 787 default aircrafts it’s fine. driver 416.14 should I run a sfc/scannow?? thanks mike Edited September 1, 20205 yr by mikeymike
September 1, 20205 yr 10 minutes ago, mikeymike said: should I run a sfc/scannow?? Doesn't hurt, and might find some system file errors. 10 minutes ago, mikeymike said: driver 416.14 Your driver is old. Update to 452.06 (You will gain back ~1 GB of VRAM) What video card and how much ram do You have? But I would try lowering the graphics settings first. (You are consuming all your VRAM) Edited September 1, 20205 yr by RamonB Ramón. Time, is the one thing no one can buy.
September 1, 20205 yr Author Just now, RamonB said: Doesn't hurt, and might find some system file errors. But I would try lowering the graphics setting. Thanks will do. my settings are medium to high. i9 9900k 1080ti 32gb ram 3600mhz gigabyte aorus master. thanks mike
September 1, 20205 yr Also update Your nvidia driver to 452.06 You will gain back ~1. GB of VRAM Ramón. Time, is the one thing no one can buy.
September 1, 20205 yr I would try a reinstall. Could be a real light or true glass thing. I mean reinstall the plane. Not the sim 5800X3D, 4090FE, 64GB DDR4 3600C16, Gigabyte X570S MB, EVO 970 M.2's, Alienware 3821DW and 2 22" monitors, Corsair RM1000x PSU, 360MM MSI MEG, MFG Crosswind, T16000M Stick, Boeing TCA Yoke/Throttle, Skalarki MCDU and FCU, Logitech Radio Panel/Switch Panel, Spad.Next
September 2, 20205 yr Author 1 hour ago, micstatic said: I would try a reinstall. Could be a real light or true glass thing. I mean reinstall the plane. Not the sim Will try also. thank you mike
September 2, 20205 yr His vram usage is probably just fine, for some reason many lump DXGI errors in with VRAM issues which they are quite different. i7-13700KF, 32gb DDR4 3200, RTX 4080, Win 11, MSFS 2024
September 2, 20205 yr Definitely update the video card driver, and also delete your shaders after that. That will allow P3D to rebuild the shader cache. Rhett 7800X3D ♣ 96 GB G.Skill Flare ♣ Gigabyte 4090 ♣ Crucial P5 Plus 2TB
September 2, 20205 yr Author 1 hour ago, RamonB said: Also update Your nvidia driver to 452.06 You will gain back ~1. GB of VRAM I’m sitting at 10.1gb our of 11 with this driver sorry meant 446.14 driver it has been the most stable and fluid out all the Latest drivers above that. mike
September 2, 20205 yr 11 hours ago, mikeymike said: it has been the most stable and fluid out all the Latest drivers above that. If you get "DXGI_ERROR_DEVICE_HUNG" error messages, saying you were using "most stable driver" sounds a little bit contradictory 😉 But no offense, it's true.. Prepar3D v5 is not completely "innocent", there are still issues, so everybody is looking forward to 5.1 to improve stability even more. (Personally, for me HF2 is very stable and I rarely have issues nowadays) Anyway, you said this happens with the QW787, a plane which uses TrueGlass and RealLight (by TFDi).. TrueGlass and RealLight are still in beta and rather unstable - while TFDi delivered an update a few days ago which lowers VRAM usage of both these components, it's still unstable (for me) and their 717 is the only plane where I get sometimes DXGI_ERROR_DEVICE_HUNG messages. So I just don't use it until it gets out of beta. If this only happens with the QW787 (I don't have it installed in v5), there is a chance it's the same issue.. You can try to disable RealLight and TrueGlass by renaming the TrueGlass.dll and RealLight.dll into something like TrueGlass.dll.bak and RealLight.dll.bak (change the file ending so it doesn't load anymore) or move them to a different folder (they reside in your "Prepar3D v5\gauges" directory). If you do this, of course both components won't work anymore but the plane should be flyable and your VRAM usage will go down. Maybe you can try this and if you don't get these "DXGI" errors anymore after disabling, you found the issue. Unfortunately, if this is the case, there isn't much you can do besides waiting for TFDi to deliver updates improving stability of both RealLight and TrueGlass. Edited September 2, 20205 yr by roesti
September 2, 20205 yr This was driving me mad last week. I had one graphics profile that always resulted in this error. It turns out not having 'black-out desktop' enabled was the issue. I don't know why and it might just be me but I thought I'd share!
September 2, 20205 yr Author 1 hour ago, roesti said: If you get "DXGI_ERROR_DEVICE_HUNG" error messages, saying you were using "most stable driver" sounds a little bit contradictory 😉 But no offense, it's true.. Prepar3D v5 is not completely "innocent", there are still issues, so everybody is looking forward to 5.1 to improve stability even more. (Personally, for me HF2 is very stable and I rarely have issues nowadays) Anyway, you said this happens with the QW787, a plane which uses TrueGlass and RealLight (by TFDi).. TrueGlass and RealLight are still in beta and rather unstable - while TFDi delivered an update a few days ago which lowers VRAM usage of both these components, it's still unstable (for me) and their 717 is the only plane where I get sometimes DXGI_ERROR_DEVICE_HUNG messages. So I just don't use it until it gets out of beta. If this only happens with the QW787 (I don't have it installed in v5), there is a chance it's the same issue.. You can try to disable RealLight and TrueGlass by renaming the TrueGlass.dll and RealLight.dll into something like TrueGlass.dll.bak and RealLight.dll.bak (change the file ending so it doesn't load anymore) or move them to a different folder (they reside in your "Prepar3D v5\gauges" directory). If you do this, of course both components won't work anymore but the plane should be flyable and your VRAM usage will go down. Maybe you can try this and if you don't get these "DXGI" errors anymore after disabling, you found the issue. Unfortunately, if this is the case, there isn't much you can do besides waiting for TFDi to deliver updates improving stability of both RealLight and TrueGlass. Thanks for the reply. let me clarify,I did have to reinstall P3d v5 and quality wings 787 ,as I got a new m2 ssd and after doing so i get this error. and for the driver. For some reason any driver above 446.14 the sim is jerky /stuttery Thanks mike Edited September 2, 20205 yr by mikeymike
September 2, 20205 yr Author 53 minutes ago, slod said: This was driving me mad last week. I had one graphics profile that always resulted in this error. It turns out not having 'black-out desktop' enabled was the issue. I don't know why and it might just be me but I thought I'd share! Interesting!! As mine is not enabled. will try. thanks mike
September 2, 20205 yr An iffy GPU overclock can also cause these errors. This includes factory overclocks. I have a pair of water-cooled 980Ti boards that came from the manufacturer overclocked, and one of them would occasionally go off into device hung La-La land at its default (factory overclock) speed. Slowing it down just slightly fixed it. 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
September 2, 20205 yr 14 hours ago, mikeymike said: Its only happening when I fire up the qw 787 Reallight seems to be your problem with this equipment on your system. Go to the Aircraft.cfg and add (noRL) in the panel section of the repaint. This should solve the problem. [fltsim.XX] title=QualityWings 787-8 American N815AA sim=Boeing 787-8 GE model=ge panel=noRL <------------------ This section sound=ge texture=N815AA kb_checklists= ui_manufacturer=Boeing-QWSim
Archived
This topic is now archived and is closed to further replies.