15 minutes ago, Speedbird 217 said:

Lol you’re funny. I should be able to turn on and off my screen without CTD, don’t you think? Without Atmos no crash. With Atmos, crash. That’s textbook poor programming but I can see that it’s pointless to argue with you.

Indeed its pointless. The cause was and is your system. 

 

2 minutes ago, GSalden said:

Indeed its pointless. The cause was and is your system. 

 

Funny how you think you can diagnose other systems from a distance.

1 minute ago, StoneDoor said:

Funny how you think you can diagnose other systems from a distance.

Did you read what he wrote ?

You too had issues. Ethernet issues of I am correct.

Hopefully hou have of wording now.

Edited November 2, 20241 yr by GSalden

Just now, GSalden said:

Did you read what he wrote ?

Yes. And I understood what he wrote.

Just now, StoneDoor said:

Yes. And I understood what he wrote.

So why that reply ?

From the outside this thread highlights an issue with the software running on some people's systems, everyone's seems are different and programs will cause crashes for different reasons.

I've avoided Atmos due to the clunkiness of other Rex products and the fact MSFS24 is round the corner, these crashes for other people don't worry me but they should be a concern for Rex.

2 hours ago, MarcG said:

but they should be a concern for Rex.

Great comment, they dont seem to be that interested,just read the replies given to tickets opened on the subject,or the lack of replies to other tickets raised,it shows a total disregard to customers suffering from a CTD with Atmos installed.

On 11/2/2024 at 3:07 PM, pete_auau said:

seems  strange  as  you went  from window  mode  to full screen   suggest  this  has  caused  it  to ctd, if  you can  reproduce  this  all  the  time than you will have  your  answer

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.

 

Not experiencing crashes here, but hope Rex can get it sorted for everyone. Just love what it can do for the sim. This one from a recent flight. Nothing dramatic, just looks so good to me...

 

On 11/3/2024 at 6:13 PM, zkiwi66 said:

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.

 

Thought Id give it another go, so loaded into a flight at the gate and started Atoms, left it sitting at the gate, to see what happens, then 15mins in..... CTD!, hadn't done anything, gone anywhere or changed any settings, just came back to my pc to see it was on the desktop. started again without atmos, loaded in to flight at the gate as I did with atmos and low and behold 2hrs later Im still at the gate with sim working fine, must be my pc!

 

14 hours ago, muddy funkster said:

Thought Id give it another go, so loaded into a flight at the gate and started Atoms, left it sitting at the gate, to see what happens, then 15mins in..... CTD!, hadn't done anything, gone anywhere or changed any settings, just came back to my pc to see it was on the desktop. started again without atmos, loaded in to flight at the gate as I did with atmos and low and behold 2hrs later Im still at the gate with sim working fine, must be my pc!

 

According to all the PC specialist on here that are not suffering with a CTD when using Atmos,yeah it must be your PC,but all the users getting a CTD with Atmos installed know better.

On 11/4/2024 at 7:13 AM, zkiwi66 said:

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.

 

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.

 

I was having the same issue with couatl, so I ran REX without couatl and had no CTD. I then realized that I hadn't updated GSX in months. After the update on GSX the sim is running smoothly with no CTDs as of yet.

1 hour ago, MarbleSack said:

I was having the same issue with couatl, so I ran REX without couatl and had no CTD. I then realized that I hadn't updated GSX in months. After the update on GSX the sim is running smoothly with no CTDs as of yet.

Interesting. Going to try again without gsx. 

I have consistent ctd on every flight when running atmos. Here is my eventlog error. I hope this can help developer fix the issue.

 

Application: weathercreator.exe
CoreCLR Version: 7.0.2024.26716
.NET Version: 7.0.20
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
   at weatherforcemsfs.weatherforcemsfs.SetFunction7(Int32)
   at weatherforcemsfs.weatherforcemsfs.SetFunction7(Int32)
   at weatherforcemsfs.weatherforcemsfs.valCloudShading_ValueChanged(System.Object, System.EventArgs)
   at System.Windows.Forms.NumericUpDown.set_Value(System.Decimal)
   at weatherforcemsfs.weatherforcemsfs.SetCloudShader(Int32)
   at weathercreator.MainWindow.CldIntensity(Int32)
   at weathercreator.Functions.Reset.ResetWeather()
   at weathercreator.MainWindow.wWeatherCreator_Closed(System.Object, System.EventArgs)
   at System.Windows.Window.WmDestroy()
   at System.Windows.Window.WindowFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at weathercreator.App.Main()
 

 

As you can see in the exception info, there is a memory access violation exception. I hope they can fix the issue.