Constant Crashing

[Jim Young 2,356]

I have them in programdata and also one in appdata/roaming 

 

which ones should i disable the ones in programdata or appdata or does it not matter so long as one lot is disabled ?

 

thanks 

Both of them are valid files and they will work.  It does not matter where the modules are loaded from, from App Data or from Program Data.  In order to determine if a crash problem exists with a module, you need to rename or move the dll.xml and exe.xml from BOTH locations.  I was having many StackHash errors recently and I have fixed by problem as I determined the cause was from one of the modules.  It came down to the fact that one of the ASN entries was missing in the dll.xml so I added it back and all is well again.

I get the error box stating that P3D has stopped working and Windows will search for the cause of the problem...etc..etc...etc. Thats pretty much it.

 

I am debating on just doing a WIndows10 install if I have a corrupt .NET runtime problem.

Brian,

 

Just making sure you see that I fixed my StackHash errors.  Hopefully you will have the same luck.  It turned out not to be a problem with Sode or North and South Calif but an entry in the dll.xml as I stated above.

 

Best regards,

[Brian_A_Neuman 198]

Jim,

 

I honestly bit the huge bullet. I uninstalled everything and deleted all folders/sub folders. I upgraded to Windows 10, P3D 3.3.5, and am about 60% back installed. I disabled my AV while downloading and installing, made an exception to my P3D root folder. I did NOT install EMT...

 

So far, so stable....I am hoping it stays this way, I will let y'all know when I am back to 100% with all sceneries and aircraft.

[Jim Young 2,356]

 

 

I honestly bit the huge bullet. I uninstalled everything and deleted all folders/sub folders.

 

I've had to take that huge bullet too a couple of years ago.  Just could not find what was wrong.  That was for FSX (so far no issues with P3D).  I took the reinstall of FSX very, very slowly and made sure I ran FSX before adding another add-on.  Good luck with the new installation!

 

Best regards,

[fluffyflops 1,858]

Bumping this one... my two exe.dll and dll.xml have different stuff in both...have a look jim 

 

programdata files..

 

<?xml version="1.0" encoding="Windows-1252"?>

 

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

    <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>

        <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>

 

 

 

<?xml version="1.0" encoding="Windows-1252"?>

 

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

    <Descr>AceXML Document</Descr>

    <Filename>exe.xml</Filename>

    <Launch.Addon>

        <Name>SODE</Name>

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

        <CommandLine>P3Dv3</CommandLine>

    </Launch.Addon>

    <Launch.Addon>

        <Name>Couatl</Name>

        <Path>fsdreamteam\couatl\couatl.exe</Path>

    </Launch.Addon>

    <Launch.Addon>

        <Name>XHT.APController</Name>

        <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Aerosoft\AirportController\APController.exe</Path>

    </Launch.Addon>

</SimBase.Document>

 

 

 

 

and then appdata 

 

<?xml version="1.0"?>

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

  <Descr>Launch</Descr>

  <Filename>dll.xml</Filename>

  <Launch.Addon>

    <Name>Migration Tool Plugin</Name>

    <Path>MigTool.dll</Path>

    <DLLStartName>module_init</DLLStartName>

    <DLLStopName>module_deinit</DLLStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>STB Sim Plugin</Name>

    <Path>C:\Program Files (x86)\FlyingWSimulation\SuperTrafficBoard for Prepar3D V3\STBServer\STBServer.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>PMDG HUD interface</Name>

    <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>

    <DLLStartName>module_init</DLLStartName>

    <DLLStopName>module_deinit</DLLStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>PMDG Interface</Name>

    <Path>PMDG\DLLs\PMDG_Interface.dll</Path>

    <DLLStartName>module_init</DLLStartName>

    <DLLStopName>module_deinit</DLLStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>RAASPRO</Name>

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

    <DLLStartName>module_init</DLLStartName>

    <DLLStopName>module_deinit</DLLStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>ObjectFlow_P3D</Name>

    <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>VistaMare Core</Name>

    <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\VistaMare\ViMaCoreX.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>FSUIPC 4</Name>

    <Path>Modules\FSUIPC4.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>as_connect</Name>

    <Disabled>False</Disabled>

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

  </Launch.Addon>

</SimBase.Document>

 

 

 

<?xml version="1.0" encoding="windows-1252"?>

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

  <Descr>Launch</Descr>

  <Filename>exe.xml</Filename>

  <Disabled>False</Disabled>

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

  <Launch.Addon>

  </Launch.Addon>

  <Launch.Addon>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Name>UT2</Name>

    <Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Flight One Software\Ultimate Traffic 2\UT2Services.exe</Path>

    <NewConsole>True</NewConsole>

  </Launch.Addon>

  <Launch.Addon>

    <Name>as_btstrp_config_manager</Name>

    <Disabled>False</Disabled>

    <Path>as_srv\as_btstrp_config_manager.exe</Path>

  </Launch.Addon>

</SimBase.Document>

 

 

is there anyways someone clever can merge the 2 so i can delete the one i dont need.  A million thanks in advanced.

[Jim Young 2,356]

I would not merge the files.  There are some programs that install in the new location like FSDT/FlightBeam entries.  That's okay as long as they are not also in the old location (where the P3D.cfg is located).  I had a StackHash when messing with mine as I somehow got the ASN entries in both locations.  Just make sure there are no duplicate entries.  One of these days everyone will be putting the entry in the new location (where the scenery.cfg is located).

 

Best regards,

[fluffyflops 1,858]

I think I've sussed it Jim... The aerosoft vistamar.dll seemed to be the culprit

[Jim Young 2,356]

Good news Pete.  The vistamare.dll was a major cause for a CTD several years ago.  Hope this is it and you can again enjoy flying.