I started getting a fatal error and cannot start P3D.  I tried a window's restore and it did not help.  Do you think I could reinstall P3D over the existing program without completely starting over and reinstalling all add-ons?

Thanks a lot,

Howard

If you cannot start up P3D, it is usually a corrupted add-on that uses the dll.xml to load their module.  All modules in the dll.xml are loaded at startup.  The sim will not start up if one of the modules is missing or corrupted.

 

Best regards,

Thanks Jim.. Where can I find these files?

Thanks,

Location:  Local Disk (C:) ► Users ► you ► AppData ► Roaming ► Lockheed Martin ► Prepar3D V3   dll.xml 

Thank you.  Do you think I could reinstall P3D over the existing installation or do I have to start over?

Some People do that alright but You have to Know what you are doing as there is a little configuring afterwards.  

 

Try Jim's suggestion before you do anything else  

How do I know which files are corrupted and can I delete them?   If this doesn't work can I just install the latest Prepar3D_Academic file?  Should I delete the old file first?

 

Thanks a Lot,

Location:  Local Disk (C:) ► Users ► you ► AppData ► Roaming ► Lockheed Martin ► Prepar3D V3   dll.xml 

Don't forget Programdata\LM\P3D

I had the same problem some days ago. I just uninstalled ASN and p3d started again.

Emmanuel Argiropoulos

ASN or AS2016 has to be the last entry in the DLL.XML. Same with FSUIPC. Latest version of fsuipc makes sure this happens when you install new addons that make new entries in the dll.xml

Try checking your Event Viewer, if there was a dll file that P3D found offensive, it should show up there. Just locate it via entering Event Viewer in start/search then go to Custom Views/Administrative Events. Look for the error symbol and see what information you get.

Try checking your Event Viewer, if there was a dll file that P3D found offensive, it should show up there. Just locate it via entering Event Viewer in start/search then go to Custom Views/Administrative Events. Look for the error symbol and see what information you get.

NTdll error is a common one.

There were a lot of errors listed but I don't know what to do with them.   Should I just  reinstall the academic file?

 

 

How do I know which files are corrupted and can I delete them? If this doesn't work can I just install the latest Prepar3D_Academic file? Should I delete the old file first?

 

The AVSIM CTD Guide, page 11, provides a picture and instructions on how to enable/disable modules in your dll.xml to find out which one is causing the issue(s).  But the fastest way to see if it is the dll.xml is to move it to a temporary folder, restart P3D and see if P3D restarts.  If it does, then there is a problem with the dll.xml and you will have to investigate to find out which module is not working properly.  I have seen where the wrong version of the fsuipc.dll will cause P3D not to restart if it is not compatible with P3D. 

 

The link to the CTD Guide is in my signature.

 

Best regards,

There were a lot of errors listed but I don't know what to do with them.   Should I just  reinstall the academic file?

The CTD Guide provides instructions regarding the Event Viewer and how to fix the issues.  Check out the pictures and instructions!

 

You can reinstall the academic file but it will overwrite your p3d.cfg and scenery.cfg.  So you might want to back up those files.  Otherwise, there should be no problems (unless you have GEP3D that replaces the default textures or Orbx Global/Vector products).  Those will have to be reinstalled.

Thank you all for your help.  I finally located and deleted the dll.xml file.  I started P3D and it built a new file and all is well once more.  Thanks again to everybody.

Howard