September 28, 20223 yr I posted about this problem before. You get a dialog at each start of the flight saying that an error on your graphics card occurred and you should switch off overclocking and get recent drivers. My workaround now is to disable the scenery cache completely. No CTD after that change. Paul Schmidt We're fools to make war on our brothers in arms.
September 28, 20223 yr Thank you for the tip. Intel Core Ultra i7-265KF (3.6 GHz/4.9 GHz), MSI Inspire 3X RTX 5070 TI (16Gb), DDR7 32Go, screen ASUS XG32VQR 32'', Honeycomb Alpha Flight Controls, Bravo Throttle Quadrant, Pro Pedal CH Products, TCA Sidestick Airbus, TCA Boeing Yoke Edition, Winwing EFIS Combo, Tobii Eye Tracker
September 28, 20223 yr Author 1 hour ago, Axis3600 said: How to delete the cache ? Go to the general options and data. Paul Schmidt We're fools to make war on our brothers in arms.
September 28, 20223 yr 4 hours ago, flyingpauls said: I posted about this problem before. You get a dialog at each start of the flight saying that an error on your graphics card occurred and you should switch off overclocking and get recent drivers. My workaround now is to disable the scenery cache completely. No CTD after that change. There could be something in this. I deleted my scenery cache and stopped it from running again - no CTD of this type since. Rob (but call me Bob or Rob, I don't mind). I like to trick airline passengers into thinking I have my own swimming pool in my back yard by painting a large blue rectangle on my patio. Intel 14900K in a Z790 motherboard with water cooling, RTX 4080, 32 GB 6000 CL30 DDR5 RAM, W11 and MSFS on Samsung 980 Pro NVME SSD's. Core Isolation Off, Game Mode Off.
September 28, 20223 yr Author Still checking if it was a Placebo. 🙂 Paul Schmidt We're fools to make war on our brothers in arms.
September 28, 20223 yr 7 hours ago, flyingpauls said: I posted about this problem before. You get a dialog at each start of the flight saying that an error on your graphics card occurred and you should switch off overclocking and get recent drivers. My workaround now is to disable the scenery cache completely. No CTD after that change. Maybe that's why I never had that error. I always had the scenery cache disabled. Alvega CPU: AMD 7800X3D | COOLER: Cooler Master MasterLiquid 240L Core ARGB | GPU: RTX 4070 TI Super 16GB OC | Mobo: ASUS TUF GAMING X670E-PLUS WIFI |RAM: 32 GB Corsair Vengeance RGB DDR5 6000MHz PC5-48000 2x16GB CL36 | SSDs: WD Black SN770 2TB NVMe SSD (WIN11), WD Black SN850X SSD 2 TB M.2 2280 PCIe Gen4 NVMe (MSFS), Crucial MX500 2TB (Other stuff) | CASE: Forgeon Arcanite ARGB Mesh Tower ATX White | Power Supply: Forgeon Bolt PSU 850W 80+ Gold Full Modular White
September 28, 20223 yr 3 hours ago, flyingpauls said: Still checking if it was a Placebo. I hate to spoil your party, but I had that error too - before updating to the new Nvidia driver released yesterday -, however I never used scenery cache. Edited September 28, 20223 yr by Bernard Ducret Bernard CPU = 12900K / GPU = Nvidia 3090 VRAM 24 GB / RAM = 64 GB / SSD = 2 TB 980 PRO PCle 4.0 NVMe™ M.2,
September 28, 20223 yr Author 1 hour ago, Bernard Ducret said: I hate to spoil your party, but I had that error too - before updating to the new Nvidia driver released yesterday -, but I never used scenery cache. word not allowed ... Paul Schmidt We're fools to make war on our brothers in arms.
September 29, 20223 yr I have had this error about 5 times in 4 days. Anyone else still got the problem? erich
September 29, 20223 yr I had this problem during flight a couple times yesterday. Just recently upgraded to Windows 11, went back to windows 10 and took another flight without issues. Maybe a coincidence. Mike
September 29, 20223 yr Hi After half an hour I remembered this error. Tried it with and without a full community folder. Up until SU9 this bug didn't exist, this bug came with the SU10 update. https://drive.google.com/file/d/1tQY_UpWjCpeXohLEzwEDqUl5b0FbuT90/view?usp=sharing Unfortunately, I can no longer fly the simulation. Asobo needs to fix this bug. In the meantime, until the bug is fixed, I'm flying P3D You have alternatives. Edited September 29, 20223 yr by _Airbus_Fan_ Prost Torsten Künne
September 29, 20223 yr I get this error every time I pop out a window. And it’s not Vram related as I have a 3090
September 30, 20223 yr 12 hours ago, _Airbus_Fan_ said: Hi After half an hour I remembered this error. Tried it with and without a full community folder. Up until SU9 this bug didn't exist, this bug came with the SU10 update. https://drive.google.com/file/d/1tQY_UpWjCpeXohLEzwEDqUl5b0FbuT90/view?usp=sharing Unfortunately, I can no longer fly the simulation. Asobo needs to fix this bug. In the meantime, until the bug is fixed, I'm flying P3D You have alternatives. P3D is not an alternative.
September 30, 20223 yr 9 hours ago, ErichB said: P3D ist keine Alternative. @ErichB It's still better than not flying at all. Before the MSFS came, the P3D was a sim that was flown a lot. In any case, with this bug, the sim is no fun. Prost Torsten Künne
Archived
This topic is now archived and is closed to further replies.