Recently, I installed the Leonardo MD-80. Followed all the steps, and the only thing it did differently than any other addon installation was doing something to the AIRAC files. Anyways, I started up FSX and launched the MD 80. First thing I noticed was the lack of a VC. Then, I click ALT to bring up the little menu bar at the top and I noticed that my addons menu was missing! I uninstalled the MD-80 and did a system restore. Still no addons menu, and now whenever I exit a flight, no main menu comes up, only a message saying a fatal error occured. No addons menu means I can't alter various settings of addons like sound, fuel,etc. And now it crashes after every flight. All was fine until I installed the Leonardo MD-80. I'm not trying to accuse it, but the problem started right after I installed it. I am also afraid to rename the FSX.CFG since the last time someone did that (microsoft tech support did it while controlling my computer wirelessly) half my addons crashed when I tried to load them and half suddenly had invalid registrations (I don't know why because I buy all of my products from reputable sites and never pirated). Now, a lot of my addons like the PMDG MD-11 crash and the 747 crash whenever I select them all because of this MD 80. Ugh!!!! One more thing after doing more tests. Most addons don't laucnch now giving me some DLL error and the NGX HUD doesnt work. So basically, no addons work correctly now.

Hi Mark: Sorry to hear of your problem with the 80! Let's see what we can do..

 

1). I strongly suggest UAC is turned off:

2). Do not launch FSX, and then the Maddog. This is most important.

3). Go here, and download the quick-start guide - this will help you getting airborne.

4). Go here, for help with the Load Manager setup - needed for steps 5 & 6. This site also has a doc regarding VC problems.

5). In the Quick-Start Guide's Appendix, it shows how to setup a default flight at Seattle, using the Cessna 172.

 

6). After you've saved the default flight - (mine is "Cessna 172 at KSEA Gate B8) - switch the aircraft for the Maddog - don't do anything - just save this flight as the "Maddog at KSEA Gate B8". FSX will append ".FLT": this needs to agree with the name of the "Default Situation" in the LM's Setup - General page.

 

7). Once this is done - using "Run as Admin" - fire up the Maddog's "Load Manager" and setup the flight.

8). Half-way down the Setup General page - there is a window requesting the default flight. Enter the name of the flight which you just created in Step 5 above.

9). Once this is all done you can put a check mark at the top of the LM front page to start FSX. Select "Cold and Dark" in the small window that pops up next.

 

10). This doc will help you somewhat with more advanced setup, and other docs and help is also available once you get to this point - almost ready to start. Here I want to know if you still have a problem with VC or menu, etc.. so please come back here and ask. I will monitor the thread. :smile:

 

Cheers,

 

pj

Hi Mark: Sorry to hear of your problem with the 80! Let's see what we can do..

 

1). I strongly suggest UAC is turned off:

2). Do not launch FSX, and then the Maddog. This is most important.

3). Go here, and download the quick-start guide - this will help you getting airborne.

4). Go here, for help with the Load Manager setup - needed for steps 5 & 6. This site also has a doc regarding VC problems.

5). In the Quick-Start Guide's Appendix, it shows how to setup a default flight at Seattle, using the Cessna 172.

 

6). After you've saved the default flight - (mine is "Cessna 172 at KSEA Gate B8) - switch the aircraft for the Maddog - don't do anything - just save this flight as the "Maddog at KSEA Gate B8". FSX will append ".FLT": this needs to agree with the name of the "Default Situation" in the LM's Setup - General page.

 

7). Once this is done - using "Run as Admin" - fire up the Maddog's "Load Manager" and setup the flight.

8). Half-way down the Setup General page - there is a window requesting the default flight. Enter the name of the flight which you just created in Step 5 above.

9). Once this is all done you can put a check mark at the top of the LM front page to start FSX. Select "Cold and Dark" in the small window that pops up next.

 

10). This doc will help you somewhat with more advanced setup, and other docs and help is also available once you get to this point - almost ready to start. Here I want to know if you still have a problem with VC or menu, etc.. so please come back here and ask. I will monitor the thread. :smile:

 

Cheers,

 

pj

Thank you for your quick reply. But the thing is that now I'm not even concerned with the MD 80. I'm concerned with the fact that pretty much nothing works :( . I'm pretty sure it's a problem with the dll.xml file. Here's a quick rundown of my problems. Almost all addons will crash FSX now whenever I click on them and try to use them. Some (like the PMDG 747) will actually tell me it can't find a DLL file (or that it's missing) or something like that. Also, the LVD 767 tells me I must reinstall it. So pretty much, all addons don't work now and I'm almost certain (based on what I've read) that it's a dll.xml problem. Will reinstalling addons and FSX completely fix this? I'm more than ready to do a COMPLETE REINSTALL of FSX to fix the problem.

Hmmm Sounds to me like you've lost the FSX registry entry, and maybe other entries, to, so - go here, download and run these two TweakFS tools. This will verify those xml's and the reg entry.

 

http://dl.dropbox.com/u/52676345/Mark_Javornik/fsx_reg_utility.zip

http://dl.dropbox.com/u/52676345/Mark_Javornik/fsx_xml_toolbox.zip

 

Don't reinstall FSX yet, and don't install, reinstall or uninstall anything else 'till you've run these tools. We can easily fix the xml files from here. It's a two-second job, and no problem.

 

We need to see your system specs, too, Mark - so would you please put them in your profile, and paste your fsx.cfg here, too. The last thing - mentioned in the earlier post - turn off your UAC if you are running Vista or Windows 7.

 

Thanks.

 

pj

The answer to your problem is presenting itself to you. The message about the missing DLL is not a coincidence, it is a key to the puzzle. You need to note which DLL the message refers to and then replace that file. You can find this information in event viewer under the "windows logs" and "application log" section. Of course, you can also find it by closing flight sim and reading the error message.

Again, whenever you have a CTD, you need to download and run App Crash View - http://www.nirsoft.net/utils/app_crash_view.html and post the results here so we can analyze. You can also look in the Event Viewer but this app is quicker.

 

Best regards,

Jim

Thanks for all the quick replies! So I ran the Tweak FS XML Tool and it found 2 out of the 4 xml files. It says that the exe.xml file is not found and that the SimConnect.xml was not found. So, what do I do now, haha? Will I have to do any file changing because I'm not familiar with changing lines of code.

Your next step should be to follow the instructions that either Jim or myself have laid out for you.

I am having trouble finding the FSX.CFG. What is its location (I can't find it in the programsx86 folder). But just to be clear, I have the dll.xml, and the standard.xml files, but am missing the exe.xml and the SimConnect.xml (according to the Tweak FS Tool) I am guessing that those missing files are the cause of my problems. So, how do I get those back? And sorry I didn't post my CFG but I'm not exactly sure where to find it. But once again, is there a way to get those 2 xml files back? Thanks

fsx.cfg and dll.xml are both located in c/users/your username/AppData/Roaming/microsoft/fsx

 

If you don't see that folder, change your folder options. Or quick metod - click on start, in "search programs and files" type %fsx.cfg% and hit enter. This is the quick metod to find anything on your PC

Will a reinstall of FSX recreate those missing files (exe.xml and SimConnect.xml) because I'm not sure how to edit lines of code in the CFG and I really don't want to mess anything up. So will a reinstall of FSX and addons fix this, because if it will I will gladly take the time to do all the work. I just really want to fly again!!

FSX will recreate all those files (except I think exe.xml). It is normal for the exe.xml file not to be installed initially. I think FS Dreamteam uses this file and maybe PMDG). If you want you can copy those directories where the fsx.cfg is located and the one where the scenery.cfg is located (C:\ProgramData) to a temporary folder in case you want to use them again. A clean install sometimes works, sometimes not. If it doesn't (and you really cleaned your system before reinstalling FSX), then most likely you have a system problem. This link is probably the best explanation on how to do an uninstall and reinstall of FSX - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.

 

Best regards,

Jim

Thanks again for the replies. Something weird happened. One of my addons is the QW 757. This was also one of my addons that crashed whenever I tried to load it up. So, I uninstalled it. Then, I found the installer and reinstalled it again. It turns out that I have a corrupted dml.xml file also. PMDG Tech Support told me this but so did the installation of the QW 757. After I installed it, it told me there was an error with my dml.xml file. I clicked OK and it then gave me another message. It said since my file was already corrupted, it could create a new one for me, so I clicked ok. It said it created a new, correct dml.xml file. So, I lauched FSX and the QW 757. It loaded with no problems without crashing for once. I then clicked the ALT key to bring up the menu, and for the first time the addon menu showed up. It didn't before. But, the addon menu only showed titles for FSUIPC and some other software put in by QW. But, there were no options for LVL D, PMDG, Captain Sim, etc. I assumed that this was because the addons didn't recognize the new dml.xml file. But, by this point I thought that I had already solved the problem by creating a new, clean dml.xml file. So, I uninstalled the LVD 767. My plan was to reinstall every addon hoping that it would recognize the new dml.xml and be correctly put into the addons menu. So, I then reinstalled the LVD 767 only to have the same problem I started with. My QW 757 would no longer lanch and would crash again, and the same goes for the LVD. It just said to reinstall it. Another thing to note is that all of my 767 liveries were still there, like if it didn't uninstall correctly. My addons menu was also gone now. So it was like reinstalling the LVD 767 corrupted the new dml.xml file too. I don't know why this happend so I tried reinstalling the 767 again, but nothing changed. Any ideas? To sum it up, reinstalling the QW 757 created a new, uncorrputed dml.xml file that brought back the addons menu back, but as soon as I reinstalled the LVD 767, the problem came back. The problem where almost all of my addons would crash when I try to start it up and the problem where there is no addon manager when I press ALT in FSX. Thanks for all the help so far and any further help that you can give me.

Hi,

 

Have a look into the Module's directory of FSX. Do you have a file named "leonardo.dll' or something similar related to the md80 ? I don't remember the exact name, as I haven't used the md80 since ages, and I am not presently at home in front of the pc.

If yes, rename the file like "leonardo.bak" (without quotes).

See if FSX crashes again.

 

Stéphane LI-THIAO-TE

Envoyé de mon iPad à l'aide de Tapatalk HD

The problem where almost all of my addons would crash when I try to start it up and the problem where there is no addon manager when I press ALT in FSX. Thanks for all the help so far and any further help that you can give me.

 

Ah, where should I begin. You stated QW757 said there was an error with your dll.xml (your post states dml.xml but think that was a typo on your part as there is no dml.xml) and since it was corrupted, it would freate a new one for you. It then said it created a new, correct dml.xml (misspelled again). You go on to state "it loaded with no problems without crashing for once." I have never heard of any program generating a new dll.xml, let alone the QW757. They might have entered their respective entries in your installed dll.xml but generating a new one is not possible as far as I know. It could have fixed its entry and that is why you suddenly saw the Addon Manager but I have never heard of that happening either. If you have a corrupted dll.xml, you need to reinstall all of your addons so the proper entries can be entered. There is one other way of not reinstalling all of your addons and that's looking in the folder where the dll.xml resides (same folder as fsx.cfg), and looking for a backup. Most addon developers make backups like, backup_p751_dll.xml or before_addon_manager_dll.xml. So, you can simply go in there and rename one of those backups to dll.xml and you will have many of your addons showing up. You simply have to reinstall the rest.

 

I removed my dll.xml file from my fsx folder, ran fsx and everything worked great except I had no Addon tab in the Menu. After running fsx without a dll.xml, I returned to my fsx folder where the dll.xml file should be located and it was still not there so FSX does not create a new dll.xml. It's impossible. Not to worry though as in your case it appears you have some items that were successfully installed in your dll.xml. If you have no options for LVLD, PMDG, CS, etc., you will have to run these programs and run a repair for each or reinstall them (you won't have to ininstall/reinstall).

 

Make sure you have your UAC disabled before installing addons. Your anti-virus program should also be temporarily disabled too as these programs are there to try to protect you from evil people and sometimes they think an addon is a virus and won't install it properly. If you are unfamiliar with disabling the UAC, click on the Start button and type User Access in the Search bar then look up and click on How do I disable the UAC (or something like that).

 

Best regards,

Jim