FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Mickey4673 on March 24, 2016, 06:56:36 pm
-
Hi,
yesterday i landed in Washington (KIAD scenery from Flightbeam) and as i deborded at the gate coutl stopped working. I was recommend to install the latest Stand Alone Manager. I did it and now gsx and the Stand Alone Manager causes a crah from P3D V3.1 to the desktop. After uninstalling GSX, Addon Manager and coutl P3D works fine...
Eventmanager shows this:
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 3.1.2.15831, Zeitstempel: 0x5672b60a
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0xffa00027
ID des fehlerhaften Prozesses: 0x1a3c
Startzeit der fehlerhaften Anwendung: 0x01d185ee9d3d51d2
Pfad der fehlerhaften Anwendung: P:\P3D V3.1\Prepar3D.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: 3c5b80be-f1e2-11e5-8364-d8cb8a369c9a
It's a pitty cause i can't use my bought sceneries from FSTD and Flightbeam and can't also use gsx..
Thx for your help in advance...
-
I'm sorry, but I cannot reproduce the problem. The current version of the Addon Manager has been updated only to support P3D 3.2, but it's otherwise unchanged and there's no reason it wouldn't work on P3D 3.1
I can only repeat and confirm all the previous suggestion on the forum:
- Disable any antivirus/firewall program when installing
- Configuring the antivirus to EXCLUDE the following files from scanning:
YourP3DFolder\bglmanx.dll
YourP3DFolder\fsdreamteam\Couatl\Couatl.exe
In any case, is there a reason why you haven't updated P3D to 3.2 ? It's free update. It's more difficult for us to find problems, since we are all using the latest version but, I don't see any reasons why 3.1 wouldn't work.
-
Thx for your quick reply.
I updatedt my SIM from 3.1 to 3.2 last week. It doesn't work because P3D wasn't able after updating to locate/read they key. I started a complete new and clean installation. This didn't also work cause of a .dll error... There was nothings than trouble with 3.2 so that i decided to go back to 3.1... Everything worked fine for me - just up today...
What could i do now?
As attched you can find another error. It happens in the direct order to the other error:
-
As attched you can find another error. It happens in the direct order to the other error:
That TOTALLY clears up GSX ENTIRELY from being the cause of the problem. That error is caused by a .NET application and GSX doesn't have ANY relationship with .NET, any version. There are many 3rd party addons that use .NET, but GSX is NOT one of them.
What is really happening, instead, is that you have a *general* problem with your installation, and BOTH this .NET application that crashed AND GSX are equally affected by it.