July 23, 20232 yr Highly doubt its the plane itself. I've been plagued with CTD's for weeks now. Regardless of plane etc 7800+4090+64ram Just Flight RJ, 146 and F28, Piper Arrows ---A2A Aerostar and Comanche---Black Square Starship, Duke(s), TBM, Bonanza/BaronV2, KingAir---FSReborn FSR500---COWS Da42---FX P180, HJet & VJet---FlySimWare Chancellor and LearJet---FlightSimStudio EMB175 &P2006T---Fenix 320---PMDG DC6, 737(700+900), 777---C22J---Milviz Cessna 310 & Porter---SimWorksStudios Kodiak, PC12, Zenith & RV14---BigRadials Goose---IndiaFoxEcho MB3339+F35.
July 23, 20232 yr 1 hour ago, bcuomo said: With the A2A Comanche I've had 4 CTDs out of 6 flights. I'm on the latest driver. Haven't been able to test other aircraft, but I've never had that many CTDs so close together. Don't know if it's driver, Sim or plane related. If it was plane related there would be lots of people here reporting CTD's. Did you try with all other mods disabled? If disabling other mods doesn't fix it you could also try another driver. Latest driver is also known to cause CTD's to some folks, I would suggest you to try with 531.29. 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
July 24, 20232 yr I experinced a few CTD with DX12 after installing the latest drivers, and so I switched back to DX11 and sofar no more CTD.
July 24, 20232 yr 13 hours ago, Alvega said: If it was plane related there would be lots of people here reporting CTD's. Did you try with all other mods disabled? If disabling other mods doesn't fix it you could also try another driver. Latest driver is also known to cause CTD's to some folks, I would suggest you to try with 531.29. I also doubt it's the plane, it's just never happened so frequently. I'm currently using DX 11 and the only add-ons I have in the community folder are aircraft. I did have one airport mod but removed it... Made no difference. I am using GeForce Experience to update drivers. Is there a way I can roll back to 531.29 using that? I haven't manually installed or un-installed drivers in years and so I'm not as knowledgeable as I once was, lol.
July 24, 20232 yr I refuse to update drivers if things are working w no CTD. still on 517.40 w 3080 7900x3d , 64gb 6200mhz 30CL Ram, RTX 3080
July 24, 20232 yr I had a CTD with the Comanche yesterday on my third flight with it. Had been in the air for 40 minutes or so. I had already rolled back my Nvidia driver to 531.29, so it's not just an issue with the newer drivers. I wouldn't be surprised if accusim 2.0 isn't playing nice with certain things, it being new and all.
July 24, 20232 yr 35 minutes ago, jhelix70 said: I had a CTD with the Comanche yesterday on my third flight with it. Had been in the air for 40 minutes or so. I had already rolled back my Nvidia driver to 531.29, so it's not just an issue with the newer drivers. I wouldn't be surprised if accusim 2.0 isn't playing nice with certain things, it being new and all. That is possible.
July 24, 20232 yr When I ran into the large performance drop with the 536.40 driver, one of the things I pulled for testing were the Navigraph chart add-ons (split screen & avionics-g3000-g5000). I had already discovered that the split-screen mod absolutely tanked my performance with my older system, so I removed it earlier. When I tested the chart embed in the g3000 I lost an additional 3-5 fps with the new driver so I yanked it also. Today, having successfully rolled back to the 531.29 driver and getting good results, I put the charts mod back in for the g3000. This time I only lost about 1 fps so I'll probably keep it in. Randall Rocke
July 24, 20232 yr This is by now an old story, but for some of us, SU12 introduced the infamous "graphics error" CTD, and nothing has cured it, including changing drivers. For me, and others, it happens even with the 531.29 driver, despite the fact that it seems to fix the issue for some people. I long ago came to the conclusion that it is an Asobo problem that will only be fixed by them, hopefully with SU12.
Archived
This topic is now archived and is closed to further replies.