1 hour ago, RobJC said:

I went looking for ideas on how to fix the CTDs i am having in SU2, and on the official forums lots of posts confirming CTDs, but no real help other than make sure your community folder is empty. A few Youtubers i follow also reported CTDs, which got me thinking.

The number of people getting CTDs is widespread. How was the QA team at Asobo/MS not seeing these? What XB do they have not to see the unplayable state SU2 is in on the console? Because clearly they would not have released SU2 had they witnessed these things. The xbox issues are particularly curious to me. It is the same hardware and software. How are they not seeing these issues?

I went back to the first 572 Nvidia driver then no ctd.

19 hours ago, usernamerequired said:

First time in a long time I've opted out of a beta. I can't get into a flight without a CTD, and I'm not in the mood to deal with this for the next few weeks.

That said, during the time I spent testing, I did notice an uptick in performance and reduced VRAM usage, so at least the team is heading in the right direction.

 

It will work with the first couple of 572.xx drivers.

35 minutes ago, MrBitstFlyer said:

It will work with the first couple of 572.xx drivers.

so you mean my 572.70 may cause the CTDs

22 hours ago, RobJC said:

Time to try XP12. 

I guess you're in the Beta?  It's a giant effort to move to a totally new platform unless you're pretty sure you will stay there.  There is the entire UI that will be new to you perhaps, setting up all of your controllers, learning myriad esoteric issues which all sims have and take time to learn, and then there is the installing of other addons, all over again.  Another option you have is to park 2024 and just stick with 2020 for now which is mature and solid.  I dabble in 2024, don't want to play in SU betas and spend now around 70% of sim time in 2020.  

On 3/27/2025 at 8:41 AM, tiberiu11 said:

 

At TDS Sim Software we are looking into this bug. As the TDS GTNXi does not crash with other aircraft and based on our internal testing, we do not think that it is a TDS issue, but rather a WASM issue, either due to the higher number of WASM modules being loaded or due to all WASM modules needing to be compiled with the MSFS 2024 SDK. (The TDS GTNXi WASM module is compiled with the MSFS 2024 SDK) This could very well be a MSFS 2024 SU2 Beta bug.

We have contacted A2A about this and we will do our best to assist from our side, but we think that our assistance will be limited, we just got caught as the last WASM gauge.

Thanks to the great help of A2A, this issue has been reported to Asobo and will be fixed in a future build!

What a mess. I removed everything but kept my community folder. Fresh install. NO BETA this time. Since I've been flying Inibuilds A350 I went on their initiation to install beta 1. But it was beta 2 which wrecked everything. 

Ok. Fresh install. Pointed at my custom location for the community folder. Since A350 was updated was advised didn't need betas. Great let's see. Perfect. Back to normal. Great flight with A350.

I noticed in graphics settings that beta 2 introduced FSR 3 and frame generation. At this point I don't care. Yes it hugely boosted frames but small comfort caused by the mess of beta 2 generally.

Edited March 28, 20251 yr by lenny777

SU 2 beta working absolutely splendid on my end at least.

Altough very sparse community folder (some ORBX aerodromes + COWS DA4x planes).

 

Edited March 28, 20251 yr by SAS443

5 hours ago, RobJC said:

How are they not seeing these issues?

Same way they didn’t see them at release. 

11 minutes ago, Ianrivaldosmith said:

Same way they didn’t see them at release. 

Same way some of us aren't seeing these issues because they're not happening to everyone.

Edited March 28, 20251 yr by Tuskin38

4 hours ago, DAD said:

so you mean my 572.70 may cause the CTDs

I had the latest 572 driver, but I downloaded the first one and no ctd.

45 minutes ago, Ianrivaldosmith said:

Same way they didn’t see them at release. 

Only thing I can think of at this point was that they actually DO know about these issues but release the Beta anyway, maybe in the hopes they will figure out WHY it is happening.  

So, whereas most organizations would hold the build if it was crashing for the internal test team Asobo either seem to miraculously miss all of these issues internally or they are experiencing the same thing but release the code anyway...  What would still be an Alpha or Pre-Beta build for most dev teams Asobo moves straight to Beta release even if there are known "critical" issues.  Otherwise, they are either blissfully oblivious or just the luckiest group ever that widespread issues don't impact ANY of their test team... 

Edited March 28, 20251 yr by psolk

11 minutes ago, psolk said:

whereas most organizations would hold the build if it was crashing for the internal test team

Asobo has held off builds before because of that.

2 hours ago, Ianrivaldosmith said:

Same way they didn’t see them at release. 

LOL

2 hours ago, Tuskin38 said:

Same way some of us aren't seeing these issues because they're not happening to everyone.

I know some people aren't seeing these issues on PC, but even on xbox? Because there really aren't many variables with that platform. 

1 hour ago, psolk said:

Only thing I can think of at this point was that they actually DO know about these issues but release the Beta anyway, maybe in the hopes they will figure out WHY it is happening.  

So, whereas most organizations would hold the build if it was crashing for the internal test team Asobo either seem to miraculously miss all of these issues internally or they are experiencing the same thing but release the code anyway...  What would still be an Alpha or Pre-Beta build for most dev teams Asobo moves straight to Beta release even if there are known "critical" issues.  Otherwise, they are either blissfully oblivious or just the luckiest group ever that widespread issues don't impact ANY of their test team... 

After all the ups (and mostly downs) Asobo have experienced so far, I cannot believe they would knowingly release it in this state. I wonder if this is processor (or other hardware) related, and the testers (assuming they have them) are all running similar hardware? Now that would be a very generous interpretation of the situation. 

6 hours ago, Noel said:

I guess you're in the Beta?  It's a giant effort to move to a totally new platform unless you're pretty sure you will stay there.  There is the entire UI that will be new to you perhaps, setting up all of your controllers, learning myriad esoteric issues which all sims have and take time to learn, and then there is the installing of other addons, all over again.  Another option you have is to park 2024 and just stick with 2020 for now which is mature and solid.  I dabble in 2024, don't want to play in SU betas and spend now around 70% of sim time in 2020.  

Yeah, big move to go to XP12. I just spent most of yesterday and today reinstalling FS20, so FS24 is obviously way better in this department. They just need to fix this while the bulk of us are still living.