FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: dlr1984 on September 07, 2021, 03:37:52 pm
-
Apologies, second post in one day.
I've a new installation of P3Dv5.2 (used the complete installer, the hotfix is included). Now when I load P3D I see that it starts, briefly. I see the message in green that the airport cache has been rebuilt. Then I immediately get a popup that says "The Couatl scripting engine has encountered an unrecoverable error and will be restarted. Please run live update." It then asks me if I want to view the error log. A second prompt asks me if I want to restart Couatl. If I press yes I get the same error again and again. The only way to use P3D is to select no to quit Couatl.
Things I've tried:
Excluding the addon manager from the antivirus and running the live update
Restarting the PC
Starting a flight at different airports.
The error message comes back every time I load into P3D.
Thanks,
Dominic
-
Are you loading an unsupported airplane ( one that doesn't have a GSX configuration ) ? If yes, it's a known problem that has already been discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,25476.msg167445.html#msg167445
-
I'm using the Aerosoft Airbus. GSX worked with it before the reinstall.
-
Hello,
I have exactely the same issue there.
Just did the last update ( 2 times after a P3D restart in case )
No jetways or GSX services
All products are in trial Mode .
My airplane have a GSX profile (always flight the same > JHFMGS A320)
What do you advising me ? register once again with serial ?
Can you help with that .
Thanks
best regards
-
If with "same issue", you mean the error discussed in the linked thread, it has already been fixed, by getting the FSDT Live Update. That error resulted in an error only when selecting an airplane without a GSX configuration, like the default F-35, and shouldn't happen anymore.
If, instead, you simply don't see GSX at start, the usual suggestions:
- Be sure you configure the antivirus to exclude the whole Addon Manager folder.
- Run the FSDT Live Update again
- Check with the Task Manager if a copy if Couat64_p3D.exe is not running from the previous session. If yes, Terminate it and start the sim.
-
If with "same issue", you mean the error discussed in the linked thread, it has already been fixed, by getting the FSDT Live Update. That error resulted in an error only when selecting an airplane without a GSX configuration, like the default F-35, and shouldn't happen anymore.
If, instead, you simply don't see GSX at start, the usual suggestions:
- Be sure you configure the antivirus to exclude the whole Addon Manager folder.
- Run the FSDT Live Update again
- Check with the Task Manager if a copy if Couat64_p3D.exe is not running from the previous session. If yes, Terminate it and start the sim.
Say I've done these steps several times, what's next? Seems like at least a couple of us are seeing the same issue.
-
Say I've done these steps several times, what's next? Seems like at least a couple of us are seeing the same issue.
What do you mean with "same issue" ? There are several different issues discussed here and in the linked thread. Which one is yours ?
-
Say I've done these steps several times, what's next? Seems like at least a couple of us are seeing the same issue.
What do you mean with "same issue" ? There are several different issues discussed here and in the linked thread. Which one is yours ?
I just see a couple other people who aren't seeing GSX start up after getting the latest update. This is my thread: http://www.fsdreamteam.com/forum/index.php/topic,25476.0.html
-
I just see a couple other people who aren't seeing GSX start up after getting the latest update.
So you are not getting the "unrecoverable error" due to having used an unsupported airplane like the default F-35, which is the subject of this thread and has been fixed already ? If your issue is in another thread, then please, post only there.
-
After running the Couatl update this morning, when I next started P3D I got this unrecoverable error and it asked it said something was causing Coutl to constantly restart, so it asked if I wanted to turn off Couatl. I answered yes. Now Couatl won't restart. GSX doesn't work and it's not showing the Add Ons menu. And the Coutl updater says it can't update.
-
After running the Couatl update this morning, when I next started P3D I got this unrecoverable error
Assuming the unrecoverable error is exactly the same as the one discussed here, which happened only when selecting an airplane with no GSX profile, like the default F-35, as already discussed in this thread, this particular error has already been fixed, by running the FSDT Live Update again.
-
It was the PMDG NGXu
-
It was the PMDG NGXu
Then you should post your error log, because it seems to be a different error.
In any case, you said you ran the update this morning so, this morning the error was surely there, it has been fixed later so, could you please run the updater and see if it happens again ? If it does, please post your error log.
-
I have the same issue.
Did once again the live update few minutes ago, no jetways or GSX services and unrecoverable error.
I see there is 2 updaters in addon manager folder , what version do we use ?
Thanks
regards
-
unrecoverable error.
As I've said in my last post, please post your error log.
I see there is 2 updaters in addon manager folder , what version do we use ?
Always the first one, Couatl_updater.exe because, if you start the other one, you are not getting the latest version of the updater *itself*. But normally, it's not like if you have to wonder which one to start. When installing any FSDT product, an ICON on your Desktop it created, linking to the correct Couatl_updater.exe program.
-
Same with me. I've tried it at a couple of different airports. I even uninstalled and reinstalled GSX and still the issue. I get the airport cache loaded successfully message but then it keeps going back to "The Couatl Scripting Engine has encountered an unrecoverable error and will be restarted. Please run Live Update".
Here is my error log:
couatl v4.0 (build 4579)
panic log started on Tue Sep 7 13:32:49 2021
problem raised by engine or unspecified addon
{'Airport': 'KLAX', 'User Pos': (33.94095955197128, -118.40633390379861, 42.8845 m, 4.48049 m, 281.0328703767474, 0.003121366025879979, -0.0, -0.0001795659855255106, 4.572, 1.0)}
-
Here is my error log:
That's not the detailed log, which doesn't help me much, you need to enable logging in the Troubleshooting section of the GSX Settings to see it.
-
Ok here you go
-
I think the problem might be the custom profile you have for KLAX. Try to remove it.
-
Ok back to you ,
Yes the issue come from the custom profile , after delete it , GSX is working now
Any chance to fix it or we need to redo all our profiles ?
Thanks
-
Yes that fixed mine too. I appreciate your help!
-
Any chance to fix it or we need to redo all our profiles ?
That profile must have some kind problem, please post it or send it to me using the support email. Zipped, please.
-
Any chance to fix it or we need to redo all our profiles ?
That profile must have some kind problem, please post it or send it to me using the support email. Zipped, please.
Here is mine.
-
Dear Umberto
Here is my profiles (working since 3 years on P3DV4 and P3DV5)
Thanks for the help
Best regards
-
No need to send any more profile, I think I know what's happening.
You are using profiles made with a fairly old version of the editor, one that saved "None" as the name of the jetway logo, if no logo was assigned. Recent versions of the editor don't do that anymore, but profiles made for it will cause the error ONLY with the new version, which introduced multi-liveries with P3D V5.
Before the update, it was just ignoring logos, and if that profile was used with P3D V4, it would have just failed silently to create a non-existing "None.DDS" texture, which showed no logo, which was in fact the expected result. Now, it's trying to find an object for an operator called "None", which doesn't exists, causing the error. I guess that profile wouldn't have worked in FSX or P3D3 either.
Yes, of course, we need to recognize this case to handle old .INI files to ignore that but, in the meantime, you should be able to fix it by doing as follows:
- Open the .INI file with a text editor.
- Do a Search & Replace and Search this string:
jetway_logo = None
and replace it with:
jetway_logo =
Save the file and it should be ok.
-
Same Error. Addon manager folder is on the exclude list. Using a GSX configured aircraft, PMDG NGXu, at KORD with the default profile. Please see attached log.
-
Same Error. Addon manager folder is on the exclude list. Using a GSX configured aircraft, PMDG NGXu, at KORD with the default profile. Please see attached log.
Have you read my last post, which started with:
"No need to send any more profile, I think I know what's happening."
And continued with an explanation of what is likely happening, and a suggestion what to do, until we come up with a proper fix ?
-
Apologies for giving you more data.
-
Apologies for giving you more data.
Actually, I had a look at your log anyway and I'm not sure the issue is exactly the same, because the object FSDT_SODE_JW_JBT_2_5_LOGO_UA definitely exists, if you installed the upgrade.
Are you possibly using some kind of external utility that manages the add-on.xml ? The updater needs to update it with the additional path of the new liveries so, for any reason the add-on.xml is restored to a previous version ( which should only happen when using external managers ), it will surely fail, since the new Simobject folder is not active in the sim with the old add-on.xml.
Check your Documents\Prepar3d v5 addons\Fsdreamteam Addon Manager\add-on.xml and see if it contains these lines:
<AddOn.Component>
<Category>SimObjects</Category>
<Path>C:\Program Files (x86)\Addon Manager\Simobjects\PBR_P3D5</Path>
</AddOn.Component>
They should be added by the FSDT Live Update. If they aren't there, try running it again, and check if they are added. If they are, the error should go away so, in that case, you'll have to check if another utility has altered the add-on.xml ( possibly restoring it from its own backup ) to a state BEFORE the update, when that path was missing.
-
I've read these posts and I'm still confused. At Drzewiecki Design KJFK I get an error message as it loads up "The Couatl Scripting Engine has encountered an unrecoverable error and will be restarted. Please run Live Update" I've run live update twice and nothing is working. I currently have the following at KJFK which was FINE until your update. https://imgur.com/dihIdBL How do I get jetways back now??
-
At Drzewiecki Design KJFK I get an error message as it loads up "The Couatl Scripting Engine has encountered an unrecoverable error and will be restarted. Please run Live Update
The screenshot is not very helpful. To confirm the problem is in fact the one I already explained above, you should have posted your error log instead.
Be sure you have Logging enabled in the Troubleshooting section of the GSX Settings, otherwise the log won't be detailed enough to be useful.
-
Hi Umberto - Great to see you've been able to push all the customized liveries for P3D5 GSX out to all of us this week. Great to have them in both P3D4.5 and 5.1 now. Did the live update, and it seems to be working well overall. But have a question:
I often fly the Majestic Dash-8 Q400 in both P3D4.5 and P3D5.1 My GSX uses the internal database numbers for the MJC Q400 with no customization. The database numbers are the same in both sims, and have been working fine.
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. At first I suspected it might somehow be related on an avsim aircraft.cfg mod for the door locations (http://majesticsoftware.com/forums/discussion/101/jetways) that makes the doors work at SODE jetways that I'd installed in both sims. But I've removed the mods and found it isn't a fix for the P3D5 MJC catering problem. My GSX catering works in my GSX4.5 MJC Q400 but crashes couatl if I call it in P3D5.1 to the Majestic's Door 4. Have also confirmed problem is present at different airports, and have tried varying the service vehicle livery choice. Still throws the error in P3D5, but not P3D4. 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?
Regards
Chuck O
couatl v4.0 (build 4579)
panic log started on Tue Sep 7 19:15:38 2021
problem raised by engine or unspecified addon
{'Airport': 'KSEA', 'Requested assistance services at': 'Gate Q 6', 'User Pos': (47.444599438211625, -122.30420536169977, 134.356 m, 2.37797 m, 90.81449045009762, 0.025314984804922197, 0.028797931969165802, -4.3224517850059954e-07, 2.5908, 1.0)}
-
At Drzewiecki Design KJFK I get an error message as it loads up "The Couatl Scripting Engine has encountered an unrecoverable error and will be restarted. Please run Live Update
The screenshot is not very helpful. To confirm the problem is in fact the one I already explained above, you should have posted your error log instead.
Be sure you have Logging enabled in the Troubleshooting section of the GSX Settings, otherwise the log won't be detailed enough to be useful.
My error log is attached. Please send a fix as one of my favourite routes to fly is into KJFK and now that isn't possible.
-
My error log is attached. Please send a fix as one of my favourite routes to fly is into KJFK and now that isn't possible.
I can confirm you have the same identical problem that has been already reported in this very thread, which I provided two different solutions for:
1) If you just want to fix the problem and use KLAX:
http://www.fsdreamteam.com/forum/index.php/topic,25477.msg167520.html#msg167520
2) If you want to keep using Cartanya's profile, this is how to fix it ( again, while we found a solution to deal with these old profiles )
http://www.fsdreamteam.com/forum/index.php/topic,25477.msg167546.html#msg167546
-
Thanks for the reply. The ini file was the source of my problem too. Changing the entries to "jetway_logo = " fixed things.
-
Where is the .ini file?
-
I've checked in the folder
Appdata/Roaming/Virtuali/GSX
and the file kjfk-hgqdod
On nearly every gate it sats jetway_logo = HSBC and on some it says jetway_logo = JETBLUE
I don't have any jetway_logo = none
-
and the file kjfk-hgqdod
That's because you are checking the wrong file. My reply was based on the log you posted, which showed the error when you were at KLAX:
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_JBT_2_5_LOGO_None'
and you were using this .INI:
Loading user customizations from C:\Users\FlyBoyAz\AppData\Roaming\Virtuali/GSX\klax-cartayna-v5METAL.ini
So yes, I'm sure the KLAX profile does have some lines with jetway_logo = None and you can fix them as explained above. If you have a problem at KJFK too, then you should go there, and if you have the error, post again a log taken when you were at KJFK
-
We posted a fix for this specific error now, get with the FSDT Live Update. With this fix, it will no longer required to manually fix existing profiles with "None" in the jetway logo name.
-
and the file kjfk-hgqdod
That's because you are checking the wrong file. My reply was based on the log you posted, which showed the error when you were at KLAX:
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_JBT_2_5_LOGO_None'
and you were using this .INI:
Loading user customizations from C:\Users\FlyBoyAz\AppData\Roaming\Virtuali/GSX\klax-cartayna-v5METAL.ini
So yes, I'm sure the KLAX profile does have some lines with jetway_logo = None and you can fix them as explained above. If you have a problem at KJFK too, then you should go there, and if you have the error, post again a log taken when you were at KJFK
That is my ini file, he was using JFK I think. But thank you for info on how to fix it in the time being. I appreciate your help!
-
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
-
In my case , i have added a custom texture so on Jetway_logo line i have = SIXT BIARRITZ
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...
-
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
-
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.
-
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?
Umberto - Guessing my earlier post (above) got lost in all the discussion about logos ...
Any suggestions on how to resolve this?
Chuck O
-
Guessing my earlier post (above) got lost in all the discussion about logos ...Any suggestions on how to resolve this?
To confirm the problem is in fact the one I already explained above, you should have posted your .LOG file, not the .ERR file. Be sure you have Logging enabled in the Troubleshooting section of the GSX Settings, otherwise the log won't be detailed enough to be useful.
-
Guessing my earlier post (above) got lost in all the discussion about logos ...Any suggestions on how to resolve this?
To confirm the problem is in fact the one I already explained above, you should have posted your .LOG file, not the .ERR file. Be sure you have Logging enabled in the Troubleshooting section of the GSX Settings, otherwise the log won't be detailed enough to be useful.
Apologies, Umberto. (Knew that but forgot!)
Chuck
-
Your log file comes from a session in which you didn't had any errors.
Please replicate the situation which would cause the error, exit the sim ( don't restart it, otherwise a new log will be created, overwriting the previous one ) and post the log again which will surely contain the error.
-
Your log file comes from a session in which you didn't had any errors.
Please replicate the situation which would cause the error, exit the sim ( don't restart it, otherwise a new log will be created, overwriting the previous one ) and post the log again which will surely contain the error.
Sorry ! Done. (I confirmed that this one does show the Failed To Create Object Exception that triggered the couatl error.)
Chuck
-
As expected, your problem is the same as discussed in this thread, for which several solution has been already provided, some posts before:
http://www.fsdreamteam.com/forum/index.php/topic,25477.msg167564.html#msg167564
In your case, instead of jetway_logo, you should remove custom textures from containing cateringtexture lines. As confirmed multiple times in this thread, we release shortly another update which will filter out these automatically.
-
I've run the FSDT Updater twice today and I still received unrecoverable error. I've read parts of this thread and cleared all of the jetway logo settings to just "jetway_logo= " then killed the running couatl64.exe with process explorer.
I was under the impression that you pushed an update via FSDT Updater to resolve this, so we don't have to manually edit every one of the hundreds of airports I have configured GSXL2 for. The Updater is not solving the problem. The error in my error log is "Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_JBT_2_5_LOGO_AAL'
{'Airport': 'KDFW', 'User Pos': (32.91518926527237, -97.050696853549, 189.015 m, 3.88306 m, 180.25013937769458, -0.006348775699734688, -0.00017453292093705386, 0.0, 3.98068812789917, 1.0)}"
I am still troubleshooting your problem. Any advice is appreciated.
Dan Downs
UPDATE: I believe the object that fails to create is a AddonManager\simobject\pbr_p3d5\fsdt_sode_jetyway_logo..... I see one that is FSDT_SODE_JW_JBT__2_5_LOGO mdl folder with a TEXTURE.AA folder.... No AAL. What is calling the wrong texuture?? How do i fix it??
I've searched for the text 'FSDT_SODE_JW_JBT_2_5_LOGO_AAL' in my gsx\kdfw_xxxxx.ini file, your scenery\kdfw_fsdt.ini file and none found. I don't know what is calling the model or texture that doesn't exist. I copied the TEXTURE.AA texture and cfg file and name it TEXTURE.AAL and it's still failing to load KDFW.
Out of ideas, just must quit using FSDT products until this is understood and resolved.
Now 90 min into troubleshooting your problem, I turned off my .ini for kdfw and all systems are working. I don't know how this is connected.... I've been using fsdt kdfw almost daily without problem and then running fsdt updater broke it. See attached.
-
Now 90 min into troubleshooting your problem, I turned off my .ini for kdfw and all systems are working. I don't know how this is connected.... I've been using fsdt kdfw almost daily without problem and then running fsdt updater broke it. See attached.
I can only confirm your problem would have been fixed by removing the line that contains a jetway_logo with AAL code, which is not the correct code in GSX for American Airlines, that would be AA.
The reason why this error happens, has been discussed several times in this very thread. The update that would automatically ignore these textures hasn't been released yet so, it's normal you would still see the error and the solution is either editing the .INI file or removing it (again, while waiting for the fix), something you already discovered, but was explained here in post #33:
http://www.fsdreamteam.com/forum/index.php/topic,25477.msg167564.html#msg167564
-
Umbreto, I had changed all jetway_log values to = . The instances of AAL that remain are jetwayairlinecode = AAL and airlinecode=AAL. I presume then that infact ALL instances of AAL need changed to AA?? What about AALX, is that now an invalid code?
-
As expected, your problem is the same as discussed in this thread, for which several solution has been already provided, some posts before:
http://www.fsdreamteam.com/forum/index.php/topic,25477.msg167564.html#msg167564
In your case, instead of jetway_logo, you should remove custom textures from containing cateringtexture lines. As confirmed multiple times in this thread, we release shortly another update which will filter out these automatically.
OK, understand now. I'm not using a custom aircraft profile, and would prefer a general solution rather than editing each airport .ini file. So happy to wait for the filter release. Many thanks for the support!
-
Umbreto, I had changed all jetway_log values to = . The instances of AAL that remain are jetwayairlinecode = AAL and airlinecode=AAL. I presume then that infact ALL instances of AAL need changed to AA?? What about AALX, is that now an invalid code?
Both AAL and AALX has always been invalid, the one and only code for American Airlines handling has always been AA, nothing has changed.
Those files were always wrong but, if used with P3D4, which tries to load any texture with any name, they would just result in a blank logo texture (unless you HAVE added a custom texture with an AAL code ) and, in P3D5 before the multi-liveries update, GSX won't even try to create a logo, because it wasn't supported.
The same error would have happened if you tried to use that .INI in FSX so, now that P3D5 has multi-liveries using the standard ( non-RTT ) method, like in FSX, for each livery there must be a different Simobject so, .INI file with custom textures used in V5 should be filtered out, which is what the next update will do.
-
LOL really, always invalid. This file worked without error before running FSDT Updater. Don't be so defensive man, it's okay. And believe me, I never manually edited the gsx ini files, those values were placed there by your application. For example, look at the kdfw-fsdt.ini in the product's scenery folder. It uses AAL and AALX through out the file.
My question remains, do I need to change instances of AAL and AALX to AA in both my and your gsx ini file??
-
LOL really, always invalid. This file worked without error before running FSDT Updater.
You don't seem to understand, the file was always invalid for ANY of the several supported simulators that used multiple liveries instead of Render to Texture, which means:
- It was invalid for FSX and it would have generated exactly the same error, even before.
- If was invalid for P3D 1, 2 and 3 and it would have generated exactly the same error, even before.
- In P3D4 it would not generate an error, but it required for you to have a custom texture named "AAL", otherwise it wouldn't appear.
- In P3D5 BEFORE the multi-livery update, it would have just ignored any logo, regardless how it was called, that's why it would have "worked".
- After the Update, P3D5 behaves like all the other simulator with multi-liveries ( all, except P3D V4 ), which means a texture that doesn't exists (because it's custom) would cause an error, because when multi-liveries are used, for each operator, there must be a matching Simobject preinstalled.
Don't be so defensive man, it's okay
I don't know what you are trying to say here, I'm just explaining the facts, you are the one being "defensive", since nobody accused of having edited the file.
And believe me, I never manually edited the gsx ini files
Nobody said you did anything like that.
those values were placed there by your application
Of course they were, nobody said otherwise. They were MADE for P3D4 and in P3D4 they are still valid, because there we supports custom textures (assuming you have that custom texture installed).
For example, look at the kdfw-fsdt.ini in the product's scenery folder. It uses AAL and AALX through out the file.
You are now CONFUSING the parking airline codes with the custom textures! The parking codes use the AFCAD standard and they can DRIVE the selection of a texture. Meaning, an AAL or AALX parking code will give an higher preference to select American Airlines handler, which has a GSX of AA.
My question remains, do I need to change instances of AAL and AALX to AA in both my and your gsx ini file??
Your are making this question, only because you confused the parking codes with the handler, catering and jetway logo codes. As you can read from my previous posts, the codes you need to search for are:
jetway_logo
handlertexture
cateringtexture
Nowhere I said to change the "airlinecodes", which are fine as they are, and they won't create any errors, since they don't DIRECTLY create the name of a Simboject, which might not exists if the custom texture is not stock.
In any case, the issue is now obsolete, since the fix that ignores custom textures made for P3D V4 in V5 is already out.