Just now, fogboundturtle said:

did you try to reinstall Visual C++ Redistribution

no, which one do I need and where do I get the right version?

 

Just now, fogboundturtle said:

Just use Windows Defender. 

I do already
(Edit: installed also with Defender off)

Edited September 14, 20223 yr by guenseli

https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

get the X64 version

Guenseli - please check You post in the Leonardo Maddog X forum.

13 minutes ago, fogboundturtle said:

get the X64 version

thx for the hint, installed it, but no success: CTD again

thx Finn, but unfortunately this is alo not working 😫

is your windows in english ? did you install the UTF-8 support in windows ?

No german OS, but the old system was also german.

WIN11 - don't know what UTF-8 support is, but I assume WIN11 should bring everything thing I need?

 

thx for your patience!

You helped me more in half an hour then Leonardo the last 14 days 😬

2 minutes ago, guenseli said:

No german OS, but the old system was also german.

WIN11 - don't know what UTF-8 support is, but I assume WIN11 should bring everything thing I need?

 

thx for your patience!

no You have to click an option in regional settings. I am sure if you google it, you will find out how to do it.

Yes, found it, enabled it ... but .... CTD 😩

30 minutes ago, guenseli said:

Yes, found it, enabled it ... but .... CTD 😩

I really don't know what is wrong with your PC. that leaves the 2 nuclear option : Reinstall Windows or MSFS. Both of them doesn't sound like fun to me. I just did a flight this weekend with it so I know SU10 Beta is not the issue. 

No, nohing is wrong with my PC or my MSFS installation.

 

As an other user i the Maddog forum suggested I have disabled DEV mode. however, MSFS was CTDing again.
I uninstalled the Maddog, rebooted and reinstalled again (something I've done more then a dozen times the last weeks) ... AND NOW IT IS WORKING!

Quit MFS and restarted even with dev mode on and it is working now.

 

In the end I have no clue, but many thanks to everybody who has helped me 🥰

 

And to Leonardo: now go and get your business sorted!!! 😡

7 minutes ago, guenseli said:

No, nohing is wrong with my PC or my MSFS installation.

 

As an other user i the Maddog forum suggested I have disabled DEV mode. however, MSFS was CTDing again.
I uninstalled the Maddog, rebooted and reinstalled again (something I've done more then a dozen times the last weeks) ... AND NOW IT IS WORKING!

Quit MFS and restarted even with dev mode on and it is working now.

 

In the end I have no clue, but many thanks to everybody who has helped me 🥰

 

And to Leonardo: now go and get your business sorted!!! 😡

Something was corrupted for sure. I am glad you can fly it now. Enjoy !

2 hours ago, guenseli said:

No as I'm on SU10 beta already.

Of course it is tied to my new PC system. But it's now up to Leonardo support to help me solving this issues, whatever it is.

 

But that kind of support I recieve currently is miserable

There is nothing Leonardo can do to help you. They have no control over the WASM compiler that is built into MSFS, and no way to determine why the compilation is failing on your system. Asobo is the only one who can determine that. I have the Maddog and it compiles perfectly fine on the SU10 beta installation on my computer, so it is something unique to your machine.

Leonardo cannot offer support for this particular problem - the root cause is out of their hands, and the suggestion that you reinstall MSFS is probably the best that can be done under the circumstances.

8 minutes ago, JRBarrett said:

Leonardo cannot offer support for this particular problem - the root cause is out of their hands, and the suggestion that you reinstall MSFS is probably the best that can be done under the circumstances.

 

All other addons - and I have a lot - do not have this problems with compilation. They simply work.

Leonardo support could be polite, fast, could apologize for incovenience. They are nothing of it.

 

And to disable the dev mode - even that it has then just work after a reboot - was finally the solution it seems.

So, nothing was corrupt. If there have been sth corrupt then it have been solved by my countless reboots and reinstallations before also.