I am running P3D V3 and the unlicensed FSL Spotlights. When Spotlghts was installed I would get a windows error message when exiting P3D. As this would occur a couple of seconds after the program ended, it was not really an issue. More to the point, while I could use Spotlights on the DC8 I am developing, I could not get the Aerosoft Airbus to load -- not just at LGAV, but anywhere. The aircraft would begin loading in 3D and then the program would crash consistently. Only after uninstalling the Spotlight product can I load the Airbus.

I realize the product is still in Beta and look forward to these issues being worked out as it really looks wonderful.

Michael,

which Aerosoft Airbus is exhibiting this behavior please? Also- are you using the latest Spotlights?

I assume I have the latest version of Spotlights as I downloaded it only a couple of days ago.The download file name is: FSLabs_SpotLights_v1.0.0.11_beta. As for the Airbus, it's the A320/321. The install file as the following name: AS_AIRBUS-A320-A321_FSX-P3D-FSXSTEAM_V130 .

I should note that this version of the Airbus is not specifically for P3D version 3, but seems to work fine aside from this problem with spotlights.

Thank you Michael,

We'll see if we can reproduce this problem under P3D v3.

We did, in fact, reproduce this problem under P3D v3.

The crash occurs inside the Aerosoft Airbus_ECAMD2D.dll to which I have no access.

I've sent notes to Mathijs Kok to get his developer in touch with me but so far, no reply. I guess they were all at the FSKonferenz, so it might take a bit.

If you don't see anything here within the next day or two saying we got in touch, send them email too as a customer to ask?

Thanks for looking into that. I will follow up with Aerosoft in a few days if needed.

Michael,

I sent email to Joshua Che, the Aerosoft developer. Mathijs Kok is CC:ed. I will wait for their response.

Hi,

Wondering if there has been any update with this re: aerosoft airbus crashing and not working with spotlights...

Just purchased Spotlights last night for P3D V3 and loving it! Looks so much more natural and dare I say 'volumetric' rather than just textures changing... It feels like a real light.

I asked them for a sample D2D gauge which should cause the same problems but they replied they're quite busy with some professional stuff they're doing and will take a few days to look into the matter.

Hopefully they'll get back soon.

Thanks for such a swift response on this These new lights have given me a new lease of wanting to fly at night and even look good during the day when its all dull and overcast in P3D, so atmospheric

Similar problem with AB 318/319 FSX-P3D-FSXSTEAM_V130. Crashes after installing Spotlight. Have FSLabs_SpotLights_v1.0.0.11_beta. Possible to uninstall Spotlight while waiting for solution?

Not "similar" but "identical" problem - the problem lies with Airbus_ECAMD2D.dll.

You can uninstall spotlights, that's not a problem. However, we'd really love to resolve it with Aerosoft if they can find some time to assist.

Thanks for Your fast reply. Follow the forum and reinstall when when Aerosoft solved the problem.

You might want to bring this up in their forum as well - I am sure they're busy so they might prioritize it a bit higher if you do.

Did anything ever come of this?

It's been fixed awhile ago.

Ah ok - did you fix it in the later version of spotlights? I have it but sill getting the CTD on p3d 3.1

I'm still getting CTD on the airbus - other AC seem ok... seems linked to gfx card, as that pops up with error box at same time (just the generic "graphics drivers encountered an issue" type thing). Have scouted the aerosoft forums to no avail.

I am running nvidia latest drivers in surround (780gtx) , in p3d full screen

Hope you're ok.

Michael-

you are running latest Spotlights? v1.0.0.19 ?

Yes sir - thats correct. Installed last evening.

I just loaded the Aerosoft product in P3D v3.2 and all is well. Perhaps it has to do with NVidia Surround?

Hi Lefteris.

Still crashing with the Airbus I'm afraid.

Have disabled surround, and created a fresh p3d config too.

Below is hopefully helpful - let me know if you have anymore suggestions.

Spotlights is great in the other AC by the way, and the Airbus is upto v1.31, the latest.

Event Log:

Faulting application name: Prepar3D.exe, version: 3.1.2.15831, time stamp: 0x5672b60a

Faulting module name: g2d.dll, version: 3.1.2.15831, time stamp: 0x5672b6cf

Exception code: 0xc0000005

Fault offset: 0x00c7f500

Faulting process id: 0x1f3c

Faulting application start time: 0x01d17d5b26b002c9

Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe

Faulting module path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\g2d.dll

Report Id: a121a1cc-175b-4033-b747-1c7610335c7c

Faulting package full name:

Faulting package-relative application ID:

DLL.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>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>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>True</Disabled>

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

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

<Launch.Addon>

<Name>FSLOptions</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>FSLabs\DLLs\FSLOptions.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSLEvents</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>FSLabs\DLLs\FSLEvents.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSLSounds</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>FSLabs\DLLs\FSLSounds.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSLSpotLights</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

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

</Launch.Addon>

<Launch.Addon>

<Name>as_connect</Name>

<Disabled>False</Disabled>

<Path>as_srv\as_btstrp.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>exe.xml</Filename>

<Disabled>False</Disabled>

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

<Launch.Addon>

<Name>as_btstrp_config_manager</Name>

<Disabled>False</Disabled>

<Path>as_srv\as_btstrp_config_manager.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>

</SimBase.Document>

Can you try updating to v3.2 and seeing if that helps?

Hi,

Good shout on 3.2. I always defer for a few months to allow for the add-on compatibility to catch up, however I'll give this a go shortly and report back either way.

Much appreciated.

Hi Again - 3.2 is now installed and the problem persists. Any further advice?

I disabled spotlights and all ok...

----

Faulting application name: Prepar3D.exe, version: 3.2.3.16769, time stamp: 0x56df48ce

Faulting module name: d3d11.dll, version: 10.0.10586.122, time stamp: 0x56cc01ef

Exception code: 0xc0000409

Fault offset: 0x00149175

Faulting process id: 0x136c

Faulting application start time: 0x01d17d7a2589c2e3

Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe

Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll

Report Id: bb94f702-d031-4434-93c0-7c0bedd0835c

Faulting package full name:

Faulting package-relative application ID:

Michael,

we'll need to debug this issue on your end. Send me a PM with your Skype details and I'll let you know how to proceed through there.

Hi Lefteris,

Many thanks for your kind help last week - I believe I may have solved the mystery (read MAY HAVE), inasmuch there is a setting in the Airbus configurator called "Force ECAM software rendering".

When changing this setting from UNTICKED TO TICKED - the aircraft loaded, and spotlights worked a charm.

I didn't deliberately change the setting - but hopefully anyone else tripping over the same crash might be wise to check.

Perhaps you can untick yours to see if the crash is replicable - if it is.. I guess that's solved.

Can I just add my sincere thanks for taking this issue on - which was evidently nothing to do with your software, but you took ownership all the same. I really am very grateful.

Finally - spotlights is a fantastic add-on, and I can't thank you enough

Michael

Michael,

thanks for the update - I'll check asap on this end!

Hi - still going well here  Did you test yours in the end?

I could duplicate the problem with the settings you mentioned! Good find!

That's ace - thanks again for your help

Really enjoying spotlights.