4 minutes ago, Swe_Richard said:

Well of course it works for many, I didn't say anything else now did I? I said the sim is unusable FOR ME which is absolutely true as it crashes constantly since SU5 and the HF (very stable before the update). Besides, I seriously doubt they've isolated any "X-factor" yet and from the correspondence I've had with the support they simply do not know what's causing the crashes. 

Are you looking to get it working again, or just wait for next patch?

3 hours ago, Nyxx said:

19 min and  2 things.

1) Set setting and then set to "ready only"

It doesn't appear to do any good to set this file to read only , if you are into file editing. The reason for this is that 
if you look at that advanced settings under file permissions, you will see that win10 allows system changes to override
permissions. It seems that MS2020 has the ability to make changes to this file at a system level.

2) Studios drivers! 

Right!

It could force overwrite the settings but it doesn't. So read-only needs to be tagged else it will overwrite to either it's default just by using it's normal permission.

4 minutes ago, Alpine Scenery said:

Are you looking to get it working again, or just wait for next patch?

I think I am holding out for the patch now as I've tried just about everything. 

27 minutes ago, omarsmak30 said:

Or just complete clean reinstall driver could also have helped depite being studio or game driver. Nevertheless I am happy now and I won't touch it for sometimes 😅

I like to use DDU for a nice clearn un-install. Some say the new "Clean install" its not needed but hey, I play it safe 🙂

24 minutes ago, neil0311 said:

So why is it working fine with no CTDs for some of us? I’ve not had a single CTD despite hours of use with “ultra” settings. I get the frustration, but the melodrama is silly.

There’s obviously something that affects a number of people with a specific game configuration and/or hardware configuration, and not others. And they’ve isolated the “x factor” through crash dumps or other troubleshooting.

 

Ive not had any CTD for months, since Su5 Ive had 2 and they dont say anything worth noteing in the reports. Asobo have tried to sort some CTD out with the first HF  and say there working on other CTD. If your not having any, thats great, good for you. 

If it was as simple as  people with a specific game configuration and/or hardware configuration,it would have been seen and sorted out fast.

Hense why Asobo say

• CTDs – We are currently investigating and are planning on several fixes for World Update 6.

15 minutes ago, Nyxx said:

I like to use DDU for a nice clearn un-install. Some say the new "Clean install" its not needed but hey, I play it safe 🙂

Ive not had any CTD for months, since Su5 Ive had 2 and they dont say anything worth noteing in the reports. Asobo have tried to sort some CTD out with the first HF  and say there working on other CTD. If your not having any, thats great, good for you. 

If it was as simple as  people with a specific game configuration and/or hardware configuration,it would have been seen and sorted out fast.

Hense why Asobo say

• CTDs – We are currently investigating and are planning on several fixes for World Update 6.

Well, on Asobos list of things they have to do, which has been published for many months, CTDs I believe are number 3 or 4 on that list, and it says something like " in progress" or " working on" or something like that. It has never said "solved". 

1 hour ago, omarsmak30 said:

Or just complete clean reinstall driver could also have helped depite being studio or game driver. Nevertheless I am happy now and I won't touch it for sometimes 😅

This is a good point. I just switched over to the Studio driver and it is working very well. However I usually perform an express install and using the manual installation process (per Overkill's video) and checking the clean install may have really been the difference.

I would hedge my bets that if those who are seeing a positive result from using the Studio Drivers, instead unistalled their current Game Ready drivers and reinstalled them, they'd see the same benefit.  GPU drivers come with tons of configuration data buried in app data; if that gets messed up, you're in for a rough ride.   A clean driver install will set the configs to Nvidia (safe) defaults.  I'm not talking about settings made via the Control Panel BTW.

Studio Drivers have fewer features than Game Ready and really aren't a great solution for using with a demanding graphical application like MSFS.  

Edited August 5, 20214 yr by JYW

24 minutes ago, Flypops said:

This is a good point. I just switched over to the Studio driver and it is working very well. However I usually perform an express install and using the manual installation process (per Overkill's video) and checking the clean install may have really been the difference.

DDU is sort of the gold standard from IT people I have dealt with, when changing drivers. They always tell me, a few minutes doing DDU stops many problems down the line. 

40 minutes ago, Bobsk8 said:

It has never said "solved". 

Crashes are never something you can mark as "solved" in any sufficiently complex large piece of software, especially a simulation with literally an unbounded state set. If you think you've solved them all, it only means there's one you haven't yet discovered.

This biggest problem here is that there is a mismatch in expectations. CTDs can only be solved, truly, if you happen to be debugging at the time one happens, and that means that you need to be able to reproduce the exact conditions that led to the crash. The cause might be the terrain system loaded a null pointer into the cache 45 minutes ago and just decided to use that same index randomly now, a ton later. In fact, most of the time the causes are this elusive and nearly impossible to consistently hit.

In a project this large with millions and millions of lines of code spanning decades of work, this is truly a huge task. The team does nightly soak testing where they have overnight flights to try and catch some of these things, but unless you have the exact hardware, you might never see the same CTD. So you do the best you can, and as soon as you spot a cause you can debug, you solve it. CTDs are always priority 1 bugs on the project. Any time the cause for one is found, it is immediately triaged and fixed. We understand that crashes are frustrating, and even more so ones that feel so consistent a developer should surely have seen it, but the reality is that if a developer saw it and was able to reproduce it, it would already be fixed.

Even though there are no specific CTD fixes listed for the hotfix, rest assured the team always has them at top of mind.

-Matt

2 hours ago, Swe_Richard said:

Well of course it works for many, I didn't say anything else now did I? I said the sim is unusable FOR ME which is absolutely true as it crashes constantly since SU5 and the HF (very stable before the update). Besides, I seriously doubt they've isolated any "X-factor" yet and from the correspondence I've had with the support they simply do not know what's causing the crashes. 

Your comment was things are so broken that they may “never be fixed” which is hyperbole. And that’s my point.

They know (or have a good idea) what’s causing issues. And they’ve already said they’re working on fixes.

I’m convinced there is a common thread for folks having issues. I’m just not smart enough to know what it is, but I believe the dev team does. 

Sorry, this video is totally word not allowed.

He basically instructs people to hack the sim, and then even to prevent the system to correct unallowed changes.

nobody of us has any clue what these settings do, and there is a reason why the system tries to revert it back.

OK, you may have been used the kind of playing around with everything that is not encrypted because FSX was dead anyway but this is not the case with FS2020. 

Do this with any other product, you loose warranty as soon as this is detected.

Even if you try to fix constant CTDs or unsatisfactory graphics, this behavior is one of the root causes for all the mess.

51 minutes ago, neil0311 said:

Your comment was things are so broken that they may “never be fixed” which is hyperbole. And that’s my point.

They know (or have a good idea) what’s causing issues. And they’ve already said they’re working on fixes.

I’m convinced there is a common thread for folks having issues. I’m just not smart enough to know what it is, but I believe the dev team does. 

No, that is not any such thing. I’ve been triaging with support and it is clear beyond any reasonable doubt that they have no explanation or solution to my problem what so ever. In fact, they kind of low-key imply my computer is at fault. Of which it is not. Everything else works like a charm and that includes MSFS SU4.  So no, definitely not my computer. 
 

I would also be very interested to know how you know they ”have a good idea” of what’s causing this issue. They have alluded to no such thing as of yet…?

6 minutes ago, Swe_Richard said:

No, that is not any such thing. I’ve been triaging with support and it is clear beyond any reasonable doubt that they have no explanation or solution to my problem what so ever. In fact, they kind of low-key imply my computer is at fault. Of which it is not. Everything else works like a charm and that includes MSFS SU4.  So no, definitely not my computer. 
 

I would also be very interested to know how you know they ”have a good idea” of what’s causing this issue. They have alluded to no such thing as of yet…?

Sorry but you’re ignoring facts. This is explicitly what the dev team said in their post on the official forums, in addition to other items scheduled to be fixed.

”CTDs – We are currently investigating and are planning on several fixes for World Update 6.”

If you’re convinced that issues will never be fixed and this whole MSFS thing is hopeless, then it seems logical that going back to FSX and P3D would be not only logical but inevitable. 👍

9 minutes ago, Swe_Richard said:

So no, definitely not my computer. 

Of course it is. That’s doesn’t make it “your fault” but when two users are using the same application, and one has issues and one doesn’t, it means there is something specific to the configuration of the user having issues. And the fix is to figure out the variable(s) and adjust the application or fix the bug(s).

That’s IT troubleshooting 101. 

1 minute ago, neil0311 said:

 

”CTDs – We are currently investigating and are planning on several fixes for World Update 6.”

If you’re convinced that issues will never be fixed and this whole MSFS thing is hopeless, then it seems logical that going back to FSX and P3D would be not only logical but inevitable. 👍

Well.. Maybe it is because English is my second language. I don't know. The native english speakers can surely educate me on this but "we are currently investigating and planning on several fixes for update 6" is vague at best. The comment about SU6 (which is weeks and weeks away) feels like a slightly desperate attempt att buying time. One would think that users having CTDs would be above top priority but when they give a weak answer about maybe doing "several fixes" in about a months time my spidey sense starts tingling a wee bit. Add to this the non-answers they have given me from support then I am not particularly impressed.

This is not about going back to another platform. For me, the superiority that MSFS could bring to the table, have made the other platforms irrelevant. And if a fix remains out of my reach the result for me would be quitting this hobby altogether.