FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: bryn on September 01, 2019, 08:57:54 pm
-
I have GSX 2 installed in P3Dv4 and P3Dv3. P3Dv4 is working fine.
However in P3Dv3, the only item in my GSX menu is "Disable".
My Couatl.log (attached) has these lines.
Traceback (most recent call last):
File ".\GSX\__init__.py", line 355, in onAppStart
Exception: [GSX] Objects not found - GSX is disabled
Do they suggest a solution?
I have obviously done the uninstall, reinstall thing a couple of times. Having already spent five hours trying to troubleshoot this, I'm reluctant to go to the next step of uninstalling and reinstalling every FSDT product (it's a difficult and time-consuming process on an internet connection in East Africa).
-
You are using P3D 3.2, which is not supported anymore. The only supported version of P3D3 is 3.4.22, the latest one.
-
Hi,
Thanks for the response, but why do you think I'm running v3.2? I'm running v3.4.22.
The log file also says:
Simulator version: 3 4 22 19868
Running in mode: Prepar3D v3 (bglmanx setting)
There is a line saying couatl v3.2 (build 4251), but isn't that the couatl version, and not the simulator version?
Bryn.
-
Sorry, yes, you are right, the simulator version is correct. Could you please check this file ?
Documents\Prepar3D v3 Add-ons\FsDreamTeam Addon Manager\add-on.xml
ZIP it, and Attach it to your reply.
-
Hi Umberto,
Attached is the zip file with my Prepar3d v3 add-on.xml file.
I guess the legacy models are now gone and P3Dv3 uses the PBR models?
Also, note e:\programs in the addons.xml file is not my %ProgramFiles%.
Bryn.
EDIT: So I uninstalled all FSDT software, and reinstalled Addon Manager and GSX in %ProgramFiles%. It still has the same problem. And now I need to go through the labour of re-installing everything.
-
I'm checking in to see if there is an update on this? Is there anything I can try? Do you have a sense of what the problem might be?
-
Attached is the zip file with my Prepar3d v3 add-on.xml file. I guess the legacy models are now gone and P3Dv3 uses the PBR models?
No, P3D3 doesn't support PBR, so the add-on.xml file that is created for P3D3 is supposed to point out to the Addon Manager\Simobjects\Legacy folder, not the PBR folder. An add-on.xml for P3D4 would be correct, if it looked like that.
Do you have both P3D4 and P3D3 installed ? Is it possible your P3D4 registry is pointing to P3D3 ?
Also, note e:\programs in the addons.xml file is not my %ProgramFiles%.
That's not relevant. We install in the folder you said you wanted to use, which by *default* it's your standard Program Files (x86) folder, but that's just a suggestion, you are free to change it anywhere you like so, apparently, when you installed GSX, you asked to install into E:\Programs so is all normal, assuming you did so.
-
Thanks. Yes, P3Dv4 and v3 are both installed. Everything is working ok in v4.
These registry entries are pointing to the correct locations:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v3\SetupPath
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Lockheed Martin\Prepar3D v4\SetupPath
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4\SetupPath
There is no key at Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3\
Also note that E:\Programs\Addon Manager\Simobjects\Legacy is empty. The folder exists, but there is nothing in it.
Cheers,
Bryn.
-
If I copy all the PBR simobject directories to the Legacy directory and change the add-on.xml to point to Legacy correctly, P3D loads and GSX loads (but obviously a whole bunch of stuff doesn't appear, like jetways).
If I then exit and run couatl live update, it deletes all but about six of the directories in Legacy and only updates the PBR files. It also resets the P3Dv3 add-on.xml to point to PBR.
So my workaround for now is to:
1. Run the gsx_fsx_setup2.exe. This installs Legacy/simobjects
2. Backup Legacy/simobjects when the setup pauses with SODE registration (which fwiw has p3dv3 and p3dv4 directories in all the right places).
3. Cancel the setup the moment coautl_update2.exe is run
4. Check to see if couatl_updater2.exe had time to delete the files, and if it did restore the back-up
5. Make sure P3Dv3 add-ons.xml is pointing to Legacy and not PBR.
Great if you can identify the cause of the problem. I'm looking forward to the marshaller in summer attire(!), but will have to wait until I can stop couatl_updater deleting all the Legacy stuff first!
Bryn.
-
Couatl live update is still deleting the Legacy Simobjects and changing the prepar3d v3 Add-on.xml to point to pbr instead of legacy. Will this be fixed?
-
Couatl live update is still deleting the Legacy Simobjects and changing the prepar3d v3 Add-on.xml to point to pbr instead of legacy. Will this be fixed?
There's nothing to be fixed in GSX. I tried installing in P3D3 now, and it doesn't remove the Legacy objects and it creates an add-on.xml with the correct entries.
It seems your P3D3 is not recognized, possibly because of registry keys wrong, missing, or pointing to the wrong folder.
-
Thanks for looking into this.
Just to confirm, did you try installing into v3 on a computer with both v3 and v4 present?
If so, can you tell me what registry entries the updater is looking for? (You can see my entries above).
Bryn.
-
Just to confirm, did you try installing into v3 on a computer with both v3 and v4 present?
Of course, and with FSX:Se too.
If so, can you tell me what registry entries the updater is looking for? (You can see my entries above).
Those keys.
-
And can you tell me the condition required for updater to delete the content in the legacy directory?
-
And can you tell me the condition required for updater to delete the content in the legacy directory?
They are deleted only when no simulator without PBR support ( FSX, P3D1/2/3 and older versions of 4 ) is found, checking the path in the simulator own registry keys and if its executable is there.
-
This certainly looks like the registry keys are pointing to the right places:
(http://www.brynmwr.com/FSDTisdifficult/v4.jpg)
(http://www.brynmwr.com/FSDTisdifficult/p3dv4.jpg)
(http://www.brynmwr.com/FSDTisdifficult/v3.jpg)
(http://www.brynmwr.com/FSDTisdifficult/p3dv3.jpg)
Bryn.
-
I've worked it out. You don't just check for the existence of the prepar3d.exe file. You must be checking other information as well. Maybe the file date or headers. So the fix is to go to control panel and repair Prepar3d.
-
I've worked it out. You don't just check for the existence of the prepar3d.exe file. You must be checking other information as well. Maybe the file date or headers. So the fix is to go to control panel and repair Prepar3d.
As I've said, the updater checks the registry keys and the existence of the prepar3d.exe file in the locations pointed by those keys. In your screenshots, you only show the registry keys under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node, but there should be also keys under Computer\HKEY_CURRENT_USER\SOFTWARE so, either these were missing, or they were pointing to other folders.
Which explains why repairing the P3D installation fixed the issue, because it restored/fixed the keys under HKEY_CURRENT_USER.
-
Was there a fix to this? I'm having the same issue, but with P3D v2...my v4 installation works fine.
I did, however, get this from Couatl.err:
couatl v3.2 (build 4262)
panic log started on Mon Sep 23 21:20:14 2019
problem raised by engine or unspecified addon
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KOMA'}
reset FSDT_GSX_DEICING_STATE to 0
User collision geometries reloaded
EDIT: And as I saw in another post, I'm attaching a log file in ZIP format if that helps you.
-
If it’s my problem (though it doesn’t look like it with the log), it’s either going to be the registry keys (what Umberto thinks caused it and could’ve created my problem) or unexpected header information in the prepar3d executable (what I know caused it because I had edited it myself). Earlier versions of the updater didn’t check this information or accepted what I had done (changing the productVersion) but the new updates didn’t like that.
-
Earlier versions of the updater didn’t check this information or accepted what I had done (changing the productVersion) but the new updates didn’t like that.
The updater must check the version, otherwise it couldn't possibly know if the version of the sim supports the add-on.xml, P3D3, for example, supports the add-on.xml method only starting with 3.4 so, it's not enough to "just" check if the Prepar3d.exe is there, but we MUST check the version as well.
Same for P3D4, in order to know if PBR is available, the version must be checked, since it's only available starting with 4.4.
Very briefly, don't edit the version of the .EXE manually. If you have a legacy add-on that doesn't install without changing the version, install the add-on and change it back to the original.
-
Yeh, I understand. It’s just some legacy (very legacy!) add ons check the version at runtime. In no way do I expect this to be an FSDT problem though! At some point my rickety setup for older stuff will crumble - this was just an initial tremor.
-
Ok, so, are we talking about the same issue here or do I have a separate issue with my install (it appears similar).
Even after I reinstalled it and put the serial back in P3D2, it still crashes and tells me I need to install the latest version of the standalone addon manager (which, I obviously have been running the FSDT Live Update).
--EDIT--
Just ran the updater again, this time, I'm getting scenery generated with errors...here's the log.