This discussion is getting quite hilarious. There’s about half a dozen people in this thread alone who get CTDs only with Atmos. There’s more people with various issues/CTDs and odd PC behaviour linked to Atmos on various Discord groups that are sim related.

And yet we have the few experts here who keep telling us there’s nothing to see, it’s all our fault and our systems are unstable. There’s one common denominator here and that’s Atmos. I’m really not sure what to say anymore.

I sure hope none of you have to make any deductive decisions in your careers - you’d probably blame someone dying from gunshot for having something “wrong with their bodies” before they died too because not everyone dies from gunshots. Brilliant logic!

I just want to say from the top, I am not questioning that some people are having trouble with Atmos crashing them to desktop.

What I do want to ask is, why is it there are lots of people like me that are not crashing to desktop after hours of use and have not had any trouble with it?  What is the difference? 

Is it an AMD v Intel thing?  Or a faulty preset people are using? 

For reference I use an Intel 14900k, an Nvidia 4080, and the Lupo presets exclusively.

Played around with it again last night trying to produce a crash along with some FSLTL and LatinVFR KFLL stress testing.

Again fully updated Windows 10 and latest Nvidia driver. Pretty much max eye candy graphical sliders pushed to the extreme in VR using 1.4 Supersampling.

Played with REX Atmos for about 15 minutes going through several public preset profiles switching and flipping between a ton of configuration combos effortlessly without a delay nor stutter from the addon.

Couldn't produce a CTD, " so reducing graphics quality by 10%" isn't gonna solve your issue here.

Sucks some are getting the CTD because Atmos is a total visual gamechanger. The cloudy night coming into KEYW was something visually stunning unlike default MSFS colors and clouds.

 

Edited October 19, 20241 yr by blueshark747

11 minutes ago, bobcat999 said:

I just want to say from the top, I am not questioning that some people are having trouble with Atmos crashing them to desktop.

What I do want to ask is, why is it there are lots of people like me that are not crashing to desktop after hours of use and have not had any trouble with it?  What is the difference? 

Is it an AMD v Intel thing?  Or a faulty preset people are using? 

For reference I use an Intel 14900k, an Nvidia 4080, and the Lupo presets exclusively.

Thank you, that’s exactly the point that should be investigated - what is causing the issue? Not helpful for some to just keep repeating there’s something wrong with our systems.

That’s nonsense as when numerous people have a problem caused/surfaced by the same piece of software then clearly that software is doing something that is causing issues on that system. That doesn’t mean the system is inherently unstable or “pushed over the edge” - it means there’s something wrong with the software that manifests itself under certain circumstances.

I have a 13900KF, 4090 and also only use Lupo presets. Despite people here claiming that Rex have “investigated” this, I have not seen any evidence of that. First of all it shouldn’t be down to us users to troubleshoot CTDs caused by a a payware addon, and at risk of repeating myself, the response to my support ticket was ridiculous and makes me believe they haven’t got a clue what is going on or how to even establish the issue.

23 minutes ago, bobcat999 said:

I just want to say from the top, I am not questioning that some people are having trouble with Atmos crashing them to desktop.

What I do want to ask is, why is it there are lots of people like me that are not crashing to desktop after hours of use and have not had any trouble with it?  What is the difference? 

Is it an AMD v Intel thing?  Or a faulty preset people are using? 

For reference I use an Intel 14900k, an Nvidia 4080, and the Lupo presets exclusively.

At last a sensible response from a fellow simmer,thank you,not the usual answer,its all your systems are unstable.

did a dirty test with my second sim PC AMD 5950X and nvidia 3090 2x16 Gskill  stable system with atmos , swap the mems to a pair of crappy Venegance 2x16 mems , stable at 1,4v with atmos at rated 1.35 signs of artifacts 1.30v artifacts and ctd after 10min , it run the sim without atmos at 1.3v . is it atmos or crappy mems bad system tuning ? it was easy to get the system unstable 

it crash the sim with 1.27v without atmos

 

 

Edited October 19, 20241 yr by westman

28 minutes ago, westman said:

did a dirty test with my second sim PC AMD 5950X and nvidia 3090 2x16 Gskill  stable system with atmos , swap the mems to a pair of crappy Venegance 2x16 mems , stable at 1,4v with atmos at rated 1.35 signs of artifacts 1.30v artifacts and ctd after 10min , it run the sim without atmos at 1.3v . is it atmos or crappy mems bad system tuning ?

 

Congratulations, you've deliberately crashed your sim. All you've shown is that undervolting crappy RAM crashes a system with or without Atmos. I'm running quality Kingston RAM at rated specs without any overclocking in the system. I can run Memtest and other stress tests for hours without a single error. So if, by your reasoning, it's my RAM that somehow is at fault then why is Atmos still the only thing that crashes my system and stress tests designed to identify issues with RAM are not?

Edited October 19, 20241 yr by Speedbird 217

2 hours ago, Speedbird 217 said:

Congratulations, you've deliberately crashed your sim. All you've shown is that undervolting crappy RAM crashes a system with or without Atmos. I'm running quality Kingston RAM at rated specs without any overclocking in the system. I can run Memtest and other stress tests for hours without a single error. So if, by your reasoning, it's my RAM that somehow is at fault then why is Atmos still the only thing that crashes my system and stress tests designed to identify issues with RAM are not?

With your attitude you won’t make many friends here.

Westman was willing to help by doing tests but the way you respond to him is like a spoiled kid. Your system is top notch, you know it all, so I guess you will solve your issue within no time …

Good luck 👍

13 minutes ago, GSalden said:

Westman was willing to help by doing tests

If you think that deliberately misconfiguring a computer is a bona fide test, you don't know what a real test is.

With those settings the system would probably have crashed anyway, regardless of whether Atmos was running or not.

Just now, GSalden said:

With your attitude you won’t make many friends here.

Westman was willing to help by doing tests but the way you respond to him is like a spoiled kid. Your system is top notch, you know it all, so I guess you will solve your issue within no time …

Good luck 👍

Because I don’t agree with your opinion that somehow all of this is our fault for having unstable systems I won’t make friends? I think I’ll cope, thanks.

Scientific and well intended help is always welcome as we’re trying to find out what’s causing this. However, his test was completely pointless, he proved that severely undervolting some crappy Ram causes the sim to crash.

That’s utterly irrelevant as no one is debating that and it’s expected to happen. It still does nothing to prove that all of us with crashes have unstable systems. He had to undervolt significantly to get there and the difference between Atmos and no Atmos voltages to crash the sim was negligible to the point that it’s statistically almost irrelevant. 

The fact remains that none of us have issues without Atmos. I don’t under or overvolt my Ram, I don’t overclock my system and I can run memory diagnostics and system stress tests for hours without any problems.

51 minutes ago, GSalden said:

With your attitude you won’t make many friends here.

 

 

i didnt think it was a attitude problem,just explaining what he has done with testing his system memory,to many people on here wont except the issue is Atmos.

Edited October 19, 20241 yr by Benbo

Since some days back a I have strange CTD. Everything worked perfect before. What could be wrong? And yes I have gone through the standard things. 
Deleted and reinstall Nvida drivers. Deleted All Rex addons.

Still CTD up on start. What else did I update, yes LNM and here a point of problems get more clear.

Could it be that LNM with all ships present start to give problem? I do not now.

I also have turned of my discord on PC and rich present in Volanta.

I also stoped using Bandicam as an capture device 

With those of and Atmos and Accuseason on no CTD

CTD could depend on many things.

 

I have no interest in Atmos and just checked this thread out of curiosity, but for those of you have crashing issues: do you have any of the Windows core isolation features enabled? On a clean install these would be enabled by default (and honestly one should keep them enabled for security's sake), but it's worth disabling to see if that makes a difference.

could  it  be a corrupt windows update which is  causing  this  issue,   this  is  related  to another  user  who had  issues  with the  fenix  efb  which wouldn't work after  many  support  tickets  he  still didn't get  to work  so i posted  a link on  where  you could  reinstall windows  with out losing  your  data,  guess  what  it  was  the  windows  which  was  causing  the  issue.

I just purchased and installed REX Atmos, registered, etc but I can't do anything there

Tried to uninstall - reinstall, same story

When I close the program, here is the error I get

Any advices ?

https://postimg.cc/SnpfJzR5

 

Thank you

Edited October 30, 20241 yr by Sphynnx