zkiwi66
Members
-
Joined
-
Last visited
-
I just went to increase my rolling cache from 64 to 128 ( and turned dynamic settings ) and noticed my rolling cache was 0.0. No wonder i have been having issues the last couple of days.
-
OK some extra info. I tried again and have noted that if i leave the sim running with Atmos without doing anything eventually the sim will CTD. I thought that must mean a ram issue, especially with the faulting module not being a Atmos module and specifically flightsim related modules. I sent those event files to REX but then while doing so i noted that about 15 minutes after flightsim crashes and with Atmos running still i get an error in one of the REX Atmos .dll files. This is strange because Atmos should be doing nothing other than monitoring for flightsim to be running.
-
Yes, the windows event log shows that the faulting module has nothing to do with Atmos BUT it only happens when Atmos is running (100% of the time it fails Atmos is running and i have never had a CTD when i am not running Atmos). The way Atmos runs it adjust environment/atmospheric settings and i am assuming it does this constantly as the flight continues (hence the need to have it running continuously rather than set it and shut it down) so I am wondering if the change from windowed to fill screen interrupts or updates something Atmos is monitoring to display the updated settings dynamically and that causes the CTD ( in my case at least). Annoyingly it is not happening every time so hard to fault find. Of course one option is to never swap between windowed and full screen mode. Then i would get no CTD and could continue to run Atmos.
-
I had the same issue with CTDs with Atmos installed. I removed it until Tech update 1 and the manual are available and had not had any CTD since. Yesterday i updated to Win 11 24H2 and thought why not try Atmos again. Wouldn't you know it but 45 min into a one-hour flight with Atmos making it look fantastic when i went from windowed mode to full screen mode the sim CTD. Atmos is removed again until Tech update 1 comes out and i will try again.
