P3D 2.5 Crash On Startup With Fsl Spotlights 1.0.0.11 (And 10)

[Michael Freeman]

Hello

I have downloaded the beta - and would like to test it in p3d at lgav.

Sadly a CTD happens after p3d 2.5 loads the scenario screen.

Nothing in the app log - and no UAC

Possibly a clash with another addon - my dll.xml is listed below if thats useful.

Well done in any case, it's a very exciting product.

Michael

[Lefteris Kalamaras]

Michael,

no DLL.XML here - can you attach as text?

[Michael Freeman]

Sorry mate - here we are:

<?xml version="1.0" ?>

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

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

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

<Launch.Addon>

<Name>Migration Tool Plugin</Name>

<Path>MigTool.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>Addon Manager</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>bglmanx.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>PMDG HUD interface</Name>

<Disabled>False</Disabled>

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

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>PMDG Interface</Name>

<Disabled>False</Disabled>

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

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>RAASPRO</Name>

<Disabled>False</Disabled>

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

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>Flight Recorder</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

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

</Launch.Addon>

<Launch.Addon>

<Name>FSUIPC 4</Name>

<Disabled>False</Disabled>

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

</Launch.Addon>

<Launch.Addon>

<Name>VAInterface</Name>

<Disabled>False</Disabled>

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

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>VistaMare Core</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>VistaMare\ViMaCoreX.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSForce DLL</Name>

<Disabled>false</Disabled>

<ManualLoad>false</ManualLoad>

<Path>C:\Program Files (x86)\FSForce 2\FSForce.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>SODE Animation Module</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Sode\SimObjectAnimationModule.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>as_connect</Name>

<Disabled>False</Disabled>

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

</Launch.Addon>

</SimBase.Document>

[Lefteris Kalamaras]

Hello

I have downloaded the beta - and would like to test it in p3d at lgav.

Sadly a CTD happens after p3d 2.5 loads the scenario screen.

Nothing in the app log - and no UAC

Possibly a clash with another addon - my dll.xml is listed below if thats useful.

Well done in any case, it's a very exciting product.

Michael

Can you try disabling all other addons in there and seeing if it loads? then enabling one by one to see which one clashes?

[Michael Freeman]

sure - trying now, stand by

[Michael Freeman]

Found the culprit - it's the P3D Migration Tool.

Disabled that, and no more crashing on startup

Not sure if I can get the lights working yet however, as when following page 7 of the manual - trying to create a new group doesnt yield any further settings. (pmdg 738)

Will keep trying, and test other AC too.

Thanks for such a speedy response.

Michael F

[Lefteris Kalamaras]

Nice find!

Thanks for letting us know!

Is that tool still necessary after all the devs are coming out with new versions of their products?

[Michael Freeman]

I'm wrong - sorry. I changed the incorrect <disabled> tag, and ended up turning all addons off

After disabling all dll individually though the tags, and the exe.xml too... there is nothing running aside from the spotlight. And it still crashes at this point.

Would you like me to try anything else?

---dll.xml----

<?xml version="1.0" ?>

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

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

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

<Launch.Addon>

<Name>Migration Tool Plugin</Name>

<Disabled>True</Disabled>

<Path>MigTool.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>Addon Manager</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>bglmanx.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>PMDG HUD interface</Name>

<Disabled>True</Disabled>

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

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>PMDG Interface</Name>

<Disabled>True</Disabled>

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

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>RAASPRO</Name>

<Disabled>True</Disabled>

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

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>Flight Recorder</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

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

</Launch.Addon>

<Launch.Addon>

<Name>FSUIPC 4</Name>

<Disabled>True</Disabled>

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

</Launch.Addon>

<Launch.Addon>

<Name>VAInterface</Name>

<Disabled>True</Disabled>

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

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>VistaMare Core</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>VistaMare\ViMaCoreX.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSForce DLL</Name>

<Disabled>True</Disabled>

<ManualLoad>false</ManualLoad>

<Path>C:\Program Files (x86)\FSForce 2\FSForce.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>SODE Animation Module</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Sode\SimObjectAnimationModule.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>as_connect</Name>

<Disabled>True</Disabled>

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

</Launch.Addon>

<Launch.Addon>

<Name>FSLSpotLights</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>FSLabs\FSLSpotLights\DLL\FSLSpotLights.dll</Path>

</Launch.Addon>

</SimBase.Document>

----exe.xml----

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

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

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

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

<Launch.Addon>

<Name>Couatl</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

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

</Launch.Addon>

<Launch.Addon>

<Name>EZdok camera addon</Name>

<Disabled>true</Disabled>

<Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path>

</Launch.Addon>

<Launch.Addon>

<Name>as_btstrp_config_manager</Name>

<Disabled>True</Disabled>

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

</Launch.Addon>

<Launch.Addon>

<Name>FSForce</Name>

<Disabled>True</Disabled>

<ManualLoad>false</ManualLoad>

<Path>C:\Program Files (x86)\FSForce 2\FSForce.exe</Path>

<CommandLine>/FS</CommandLine>

<NewConsole>true</NewConsole>

</Launch.Addon>

<Launch.Addon>

<Name>SODE</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\SODE\SimObjectDisplayEngine.exe</Path>

</Launch.Addon>

<Launch.Addon>

<Name>XHT.APController</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

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

</Launch.Addon>

</SimBase.Document>

[Lefteris Kalamaras]

Can you clear your shader cache please?

[Michael Freeman]

Hi, strangely enough, that folder is missing.

IE here: C:\Users\P3D\AppData\Local\Lockheed Martin\Prepar3D v2\

Just "Effects" and the default flight files.

[Lefteris Kalamaras]

And what aircraft are you loading?

[Michael Freeman]

Good morning, I'm just loading up the default LM F-22.

The scenario screen opens (but not the preview of the plane) - and then after approx 5-10 seconds the screen vanishes OR reports that Prepar3d needs to close.

Oddly nothing reported in the logs to offer. Sorry about that.

I'll have a another look tonight. Tomorrow I'm flying from 7am for 24 hours straight on a vatsim charity gig - however I'm happy to try more stuff on this between legs.

Have a lovely day.

Michael

[Michael Freeman]

Still struggling with this - but I might wait to install v3. Just waiting for the right time to move across (IE when I have the time).

New prepar3d.cfg no help either... nor disabling addons, nor loading a saved frlight from the desktop with different aircraft.

All CTD - but aircraft preview stays black in scenario screen before it vanishes.

Must be something peculiar on mine i guess

[Lefteris Kalamaras]

Do you have any DX enhancers, like ENB Series, Shade or some such?

[Michael Freeman]

No sir - I have none of those things.

It must be a rare issue, as no one else seems to be having this on their setups.

I'll update gfx drivers just in case.

[Lefteris Kalamaras]

Can you try the latest version to let me know if it works for you now?