p3d v3 crashing before full start after v2 disinstall

[rajeev]

Dear Sirs
I have both the V2 , V3 professional versions . both were working fine.
I have deleted V2 and now the V3 at start up shows the logo screen but then closed with error. This has happened only after I disinstalled V2 using the programs in control panel.

Sequence of events
1) both V2 , V3 running ok in D drive ( main drive is c: win 7 64 bit proff alienware m/C)
2) disinstalled various add-ons using the prog control panel , their disinstallers.
3) disinstalled the v2 using the control panel remove programs
4) removed the folders as required of p3d v2 in 3 locations
5) started p3d v3 .. get start up screen but it terminates in between giving msg “ p3d has stopped working “ multiple times
7) run p3d v3 repair option
8) rerun , but same result as above.
9) addnl details given by Windows is as follows :
for p3d v3

Files that help describe the problem:
C:\Users\anmol\AppData\Local\Temp\WER148.tmp.WERInternalMetadata.xml
C:\Users\anmol\AppData\Local\Temp\WER1CC4.tmp.appcompat.txt
C:\Users\anmol\AppData\Local\Temp\WER1DBF.tmp.mdmp

Screen shot attached for your ref.
10) this was a clean install with all my add-ons working ok till this error after V2 disinstall.
11) fsx also stopped working , but now is ok and running ( pl see note below if it helps )
fsx stop

Files that help describe the problem:
C:\Users\anmol\AppData\Local\Temp\WER7FF8.tmp.WERInternalMetadata.xml
C:\Users\anmol\AppData\Local\Temp\WER9B17.tmp.appcompat.txt
C:\Users\anmol\AppData\Local\Temp\WERB58A.tmp.mdmp

for p3d v3

Files that help describe the problem:
C:\Users\anmol\AppData\Local\Temp\WER148.tmp.WERInternalMetadata.xml
C:\Users\anmol\AppData\Local\Temp\WER1CC4.tmp.appcompat.txt
C:\Users\anmol\AppData\Local\Temp\WER1DBF.tmp.mdmp


Pl advise , help me for fixing this.

Thank you
Rgds
Rajeev Dhawan

[rajeev]

could a reason be the FSDT addon manager deletion , which can cause this deletion. I had read about it somewhere during research on this ?

Could you pl guide me to tackle this .
rgds '
Rajeev

[Poppet]

Hello Rajeev

First, lets check the Integrity of your Prepar3D v3 Install

Navigate to your Control panel "Programs and Features" Can you see Prepar3D v3 Client, Content and Scenery there ?

Navigate to your Prepar3D v3 Install Location can you see all 17 Default yellow folders below ?

Licences, propdefs, Scaleform, ShadersHLSL, trinton, redist, SimObjects, Weather, Scenarios, Ecosystem, Fonts, Autogen, Effects, gauges, Sound, Texture, Scenery


============================

Once you confirm the above questions, Here is a Test you can do

Click and Drag Both dll.xml files out of both locations below onto your Desktop, Launch Prepar3D v3 and test

If Prepar3D launch's Ok , We can then take a closer look at the Entries in your dll.xml file's

====

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

Location: ► Local Disk (C:) ►ProgramData ► Lockheed Martin ► PreparD v3 dll.xml

====

Note: You will need to Insure you have the Box Ticked for Show hidden files, folders and drives to find these folders

[rajeev]

I Have verified the two folders and also removed the dll files as mentioned from the two paths . I restarted p3d v3 . it is ok now . got the default screen. default airport on clicking ok and it worked.
Thank you very much.
Pl advise if anything else is reqd.
rgds
Rajeev Dhawan


The following is the dll from the 1st location - roaming folder
<?xml version="1.0" encoding="WINDOWS-1252"?>

-<SimBase.Document version="1,0" Type="Launch">

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>


-<Launch.Addon>

<Name>ObjectFlow</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>D:\P3DV3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>

</Launch.Addon>


-<Launch.Addon>

<Name>as_connect</Name>

<Disabled>False</Disabled>

<Path>as_srv\as_btstrp.dll</Path>

</Launch.Addon>


-<Launch.Addon>

<Name>RAASPRO</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>.\RAASPRO\RAASPRO.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

</SimBase.Document>

NO2 following is from the program folder
<?xml version="1.0" encoding="WINDOWS-1252"?>

-<SimBase.Document id="dll" version="3,0" Type="AceXML">

<Descr>AceXML Document</Descr>

<Filename>dll.xml</Filename>


-<Launch.Addon>

<Name>SODE Animation Module</Name>

<Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll</Path>

</Launch.Addon>


-<Launch.Addon>

<Name>Addon Manager</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>bglmanx.dll</Path>

</Launch.Addon>


-<Launch.Addon>

<Name>TargetInfo</Name>

<Path>Gauges\TargetInfo.dll</Path>

</Launch.Addon>


-<Launch.Addon>

<Name>Fury_1500</Name>

<Path>Gauges\Fury_1500.dll</Path>

<DLLType>PDK</DLLType>

</Launch.Addon>


-<Launch.Addon>

<Name>Flight Recorder</Name>

<Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>

</Launch.Addon>

</SimBase.Document>

[rajeev]

Apologies for the delay in response as I was travelling.
rgds
Rajeev Dhawan

[Poppet]

Hello Rajeev

Ok, So your Issue is in one of the dll.xml files.

Move both dll.xml files back into the ProgramData and Roaming path, Note: You will have Delete the Default dll.xml file that has now Generated in the ProgramData folder, Delete it and move your old dll.xml file back in

I see from your second dll.xml file you are running FSDT Software, Download and Run the Add On Manager Link below
https://www.fsdreamteam.com/products_addonmanager.html

Now Launch Prepar3D and test after you run the Add On Manager

===========================================

If you are still having Issues, You can turn off each Entry in your dll.xml file Indavidually and then launch each time and test, By doing this you will find the problematic Entry

Change this <Disabled>False</Disabled> To This <Disabled>True</Disabled>

Here is an example below, Go through each one of your Entry's like this, Make sure you save it.

When Prepar3D launch's Ok we can then take a closer look at the problem Entry


<Launch.Addon>
<Name>ObjectFlow</Name>
<Disabled>TRUE</Disabled>
<ManualLoad>False</ManualLoad>
<Path>D:\P3DV3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
</Launch.Addon>