Products Support > GSX Support FSX/P3D
Couatl scripting engine - unrecoverable error
Aumkem:
Dear Umberto,
Thanks for the help on it.
In my case , i have added a custom texture so on Jetway_logo line i have = SIXT BIARRITZ
The error is there in that case .
Do you recommand i wait for an update from you or do the custom logo needs a specific ratio or other cause add it cause the issue also ?
Thanks
Best regards
virtuali:
--- Quote from: Aumkem on September 08, 2021, 03:26:03 pm ---In my case , i have added a custom texture so on Jetway_logo line i have = SIXT BIARRITZ
--- End quote ---
You can't have a custom logo in P3D V5, this won't change, because that would require DirectX 11. Now, the problem is existing profiles originally made for P3D V4 that CAN have custom textures. I'm afraid these would have to be changed manually to be used in V5.
You never noticed the problem before, because before any kind of texture was completely disabled in P3D V5 but now they are back, but can't be custom, they MUST be one of the ones provided with GSX. The issue is, to fix this automatically, GSX would ideally have to check for EACH jetway, if the associated object *really* exists before trying to create it. Now, considering that we have over 500 different LOGO variations ( combinations of models multiplied by liveries ), on an airport with 100 jetways, GSX would have to do 5000 checks, which would slowdown the process of generating jetways at startup.
In fact, we always had the same problem with FSX: if you tried to use a GSX profile made for P3D V4 using custom textures, it would result in the same error.
We'll probably add a new parameter in the [General] section of the .INI file itself, which will identify it as requiring RTT ( so it will only be used by P3D V4 ) or to be "P3DV5-only" ( so it will be used by P3D V5 only ), the 2nd case will be required to cover for another issue: almost all default airports in P3D V5 has been updated with different parking spots compared to V4, which had the same database as FSX. However, they have the same names so, right now, if you load a GSX profile for a default P3D V4 airport in P3D V5, parking spots won't match, and GSX will malfunction. Even worse, if you go back and forth between the two simulators and edit the profile in each one, it will create some kind of mix-up which will make things worse.
That's why, we have to start adding options to separate profiles between the various simulators, especially if you use more at the same time. We'll have to do it anyway for the MSFS version...
Aumkem:
Ok thank you very much Umberto.
We have provided a fix and everything is working well in P3DV5 with your default SIX logo now .
Thanks for the help on it
Best regards
bwbriscoe:
You haven't solved the problem.
I've run the live update and I'm still not getting any jetways at KJFK and the unrecoverable error message. Please see attached log.
ChuckOman:
--- Quote from: ChuckOman on September 08, 2021, 02:06:02 am ---After the latest LiveUpdate, boarding/deboarding and pushback all work with my other aircraft, e.g. PMDG, but for some reason when I call catering in the Majestic Q400 in P3D5, GSX immediately throws a Couatl error (see below). whereas it didn't do this before the recent liveried vehicle update. The problem is unique to P3D5 - the P3D4.5 catering call works fine..... If there was a problem with P3D5 GSX catering, I'm wondering why it should be with the MJC, and not with e.g. the PMDG777. I see from older posts that you are a real expert on the MJC!
Any suggestions of other things to try, or thoughts on what might be causing the problem?
--- End quote ---
Umberto - Guessing my earlier post (above) got lost in all the discussion about logos ...
Any suggestions on how to resolve this?
Chuck O
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version