It was formerly one of the best addon developers, but it seems the time is over. Sad, but I have the impression.

 

I got a new computer system and wanted to install the Maddog of course.

During the flight loading screen (when I want to start a flight with the Maddog), MSFS (Store) CTDs after about 2-3 minutes.
(That is the initial loading, I know about the first long loading times, but never got that far. Wasn't able to start one single flight since now)

 

I have tried really everything and I'm out of ideas:
started everything as Admin, deleted Maddog folders in documents, LocalState/packages, searched on my complete system for every Maddog file.

Event Manager tells me, faulty file is LocalState\packages\lsh-maddogx-aircraft\m29c388fdb1902c8a_0.dll

Installed in different locations

Asked a guy to share his content.xml with me (as SU10 does no have a content.xml and I deleted my old one unfortunately), but there are no entries for the Maddog.

 

What makes me really upset, is that there is such a lousy support from Leonardo. Created a support ticket 14 days agao, first answer come after 3 days, since then always several days radio silence.

For the most expensive addon in MSFS I await something better.

😡

 

If anyone have any further ideas I can try, please tell me.

many thanks

Well, I can not help you for your problem but only agree with what you say about Leonardo.

I am so much dissapointed by them! I bought the plane for 90 euros having in mind all the great memories I had with it in FS2004. Here it came with nearly no communication at all, and now it is the same no com about any future development we should expect when buying such an expensive addon. Hope my 90 euros are well spent by them though 🙄 

Pierre

Edited September 14, 20223 yr by Pochi

I have to agree, we have had no update for months. For the most expensive addon at present in MSFS the back up service seems lacking.

I've been VERY surprised at the radio silence from maddog.  To the point I've been worried about them.  I'm hoping everything is ok there at their team as they have not been acting like they have the last 5 years.  

"very few customer had this issue and it was quickly solved with the suggestion I previousy posted.

One or two had to reinstall MSFS (so the blame was on some corrupted file of the sim, not of the Maddog)

Kind regards,
Davide Marras." 

 

 

Seems, these are the final words of support. 

No apologize, just "not our problem any more". 

🥺

 

Good bye Leonardo 

Hello guenseli,

I understand your frustration, and the Maddog wasm compilation is sometime very tricky,
ending up with CDT or unfinished results (I can jump into the VC but all is CAD with the 2 animated pilots and the inability to interact with anything)

After several tests I was able to achieve the WASM compilation following the steps below :

1 First of all, delete the "lsh-maddogx-aircraft" folder in your LocalState\packages\

2 Once in MSFS, the trick is to select the default Leonardo liverie and a runway QFU at the airport of your choice as departure. (don't put the Maddog at the gate !)

3 "Fly"

4 be patient (it took around 12 minutes on my sytem to get the Maddog flyable, the double of PMDG !)

Hope this help

Georges

Hello Georges, 

Thx for trying to help. 

But done already all that. 

 

Last option is indeed to reinstall MSFS. But as I have absolutely no problems with the ton of addons I have, I do not want to do this. (and I have also started with a clean community folder) 

 

I assume it could also be some kind of registration error maybe, but if Support doesn't want to help me, what should I do. 

 

And it is the attitude of the Leonardo support which really makes me angry.

Edited September 14, 20223 yr by guenseli

In case you run the SU10 beta, that could be the problem, because the SU10 beta is probably not supported officially.

8 hours ago, guenseli said:

It was formerly one of the best addon developers, but it seems the time is over. Sad, but I have the impression.

 

I got a new computer system and wanted to install the Maddog of course.

During the flight loading screen (when I want to start a flight with the Maddog), MSFS (Store) CTDs after about 2-3 minutes.
(That is the initial loading, I know about the first long loading times, but never got that far. Wasn't able to start one single flight since now)

 

I have tried really everything and I'm out of ideas:
started everything as Admin, deleted Maddog folders in documents, LocalState/packages, searched on my complete system for every Maddog file.

Event Manager tells me, faulty file is LocalState\packages\lsh-maddogx-aircraft\m29c388fdb1902c8a_0.dll

Installed in different locations

Asked a guy to share his content.xml with me (as SU10 does no have a content.xml and I deleted my old one unfortunately), but there are no entries for the Maddog.

 

What makes me really upset, is that there is such a lousy support from Leonardo. Created a support ticket 14 days agao, first answer come after 3 days, since then always several days radio silence.

For the most expensive addon in MSFS I await something better.

😡

 

If anyone have any further ideas I can try, please tell me.

many thanks

imo, their reply by email as always been on point. I never had a CTD with the maddog. Every time I fly it , It's a really good experience.  I would follow the suggestion from others and completely remove everything and reinstall. Also make sure you don't have Razer Software running or Capture One. If you don't know what it is than don't worry. 

Just now, fogboundturtle said:

I would follow the suggestion from others and completely remove everything and reinstall.

As i said, I've done that. Followed every suggestion, except reinstalling the sim until now.

Does not help to tell me that the Maddog works for you. That was the case also on my old system. Maddog was without any problems. With my new PC, I was never able to start a flight with her.

Support is really lousy in my case. So, seems that things changed probably.

 

1 minute ago, guenseli said:

As i said, I've done that. Followed every suggestion, except reinstalling the sim until now.

Does not help to tell me that the Maddog works for you. That was the case also on my old system. Maddog was without any problems. With my new PC, I was never able to start a flight with her.

Support is really lousy in my case. So, seems that things changed probably.

 

if it doesn't work on your new pc, It really pointing to the fact that your new PC is the issue. There is a new build (SU10) being release in a week or so. So this might solve your issue.

6 minutes ago, guenseli said:

As i said, I've done that. Followed every suggestion, except reinstalling the sim until now.

Does not help to tell me that the Maddog works for you. That was the case also on my old system. Maddog was without any problems. With my new PC, I was never able to start a flight with her.

Support is really lousy in my case. So, seems that things changed probably.

 

The problem appears to occur when the base WASM files are compiled. That is done by MSFS itself the first time an aircraft is loaded, and neither Leonardo nor any other developer using WASM has any control over that process, nor any way to troubleshoot or debug the compiler if it crashes. 

8 minutes ago, JRBarrett said:

The problem appears to occur when the base WASM files are compiled.

 

Seems so, yes.
Other developers have much less trouble with it is seems

18 minutes ago, fogboundturtle said:

So this might solve your issue.

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

Just now, 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

did you try to reinstall Visual C++ Redistribution ? do you have any type of antivirus running on that pc. if you do, get rid of it. Just use Windows Defender.