Products Support > GSX Support FSX/P3D
Aiframe specific config
virtuali:
The screenshots are not useful to me, you should post a startup log instead, which is created by enabling Logging in the Troubleshooting section of the GSX Settings. Restart the sim with the airplane you have an airframe-specific CFG file for, and as soon the plane loads, exist the sim and look for the COUATL.LOG file in %APPDATA%\Virtuali.
ZIP the file and Attach it to a post.
CS-TMT:
--- Quote from: virtuali on April 06, 2022, 10:09:57 am ---(...)look for the COUATL.LOG file in %APPDATA%\Virtuali.
ZIP the file and Attach it to a post.
--- End quote ---
Dear Umberto, no Couatl.log exists in that folder, however it is created in the main P3D installation directory. The file is zipped and attached as asked.
Opening the log file I can see the following lines:
Specific .cfg file for not found in G:\Addons\Flight Simulator\FSLabs\SimObjects/Airplanes\FSLabs A320-SL CFM, using standard GSX.CFG file
Specific .cfg file for not found in C:\Users\(...)\AppData\Roaming\Virtuali/Airplanes\FSLabs A320-SL CFM, using standard GSX.CFG file
Found gsx.cfg file at C:\Users\(...)\AppData\Roaming\Virtuali/Airplanes\FSLabs A320-SL CFM\gsx.cfg
It's weird that it doesn't detect the specific CFG... ??? but maybe you can find out why.
CS-TMT:
--- Quote from: CS-TMT on April 05, 2022, 02:31:56 am ---One thing that came to mind but haven't tried yet and may be the issue here is that I have two aircraft with the same atc_id although in different folders (FSLabs A320 and FSLabs A320-SL, that is, same paint/registration for both the classic wing tip fences and the sharklet version. Could this be the culprit, although the aircraft and respective CFGs are in different folders (both of them in %APPDATA%/Virtuali/etc)?
--- End quote ---
--- Quote from: CS-TMT on April 06, 2022, 11:49:52 pm ---(...)
Specific .cfg file for not found in C:\Users\(...)\AppData\Roaming\Virtuali/Airplanes\FSLabs A320-SL CFM, using standard GSX.CFG file
Found gsx.cfg file at C:\(...)\AppData\Roaming\Virtuali/Airplanes\FSLabs A320-SL CFM\gsx.cfg
It's weird that it doesn't detect the specific CFG... ??? but maybe you can find out why.
--- End quote ---
Keeping with the weirdness (at least for me), as I said in one of my first posts regarding my issue, I have two (actually 4) aircraft using the same registration: FSLabs A320 CFM, A320-SL CFM (and A320 IAE and SL IAE). Haven't tried the IAEs, however the specific CFG for the CFM version (not SL) is being detected and working as it should...
--- Quote ---Specific .cfg file for F-WWBA not found in G:\Addons\Flight Simulator\FSLabs\SimObjects/Airplanes\FSLabs A320 CFM, using standard GSX.CFG file
Found a custom GSX.CFG file for F-WWBA in C:\Users\(...)\AppData\Roaming\Virtuali/Airplanes\FSLabs A320 CFM, using this one!
Found gsx.cfg file at C:\Users\(...)\AppData\Roaming\Virtuali/Airplanes\FSLabs A320 CFM\gsx-F-WWBA.cfg
--- End quote ---
virtuali:
--- Quote from: CS-TMT on April 06, 2022, 11:49:52 pm ---
Specific .cfg file for not found in G:\Addons\Flight Simulator\FSLabs\SimObjects/Airplanes\FSLabs A320-SL CFM, using standard GSX.CFG file
Specific .cfg file for not found in C:\Users\(...)\AppData\Roaming\Virtuali/Airplanes\FSLabs A320-SL CFM, using standard GSX.CFG file
Found gsx.cfg file at C:\Users\(...)\AppData\Roaming\Virtuali/Airplanes\FSLabs A320-SL CFM\gsx.cfg
It's weird that it doesn't detect the specific CFG... ??? but maybe you can find out why.
--- End quote ---
The only possible reason I can think of, is you haven't selected the F-WWBA airplane.
--- Quote ---Keeping with the weirdness (at least for me), as I said in one of my first posts regarding my issue, I have two (actually 4) aircraft using the same registration: FSLabs A320 CFM, A320-SL CFM (and A320 IAE and SL IAE). Haven't tried the IAEs, however the specific CFG for the CFM version (not SL) is being detected and working as it should...
--- End quote ---
Which seems to confirm you might have not selected the right airframe in the session you produced that log. I see something strange in your aircraft.cfg, that (1) added to the title, as if you copied it from another section, are you SURE you selected that one ?
CS-TMT:
That (1) is automatically put by the FSLabs internal system when a registration is used more than once. As I said before, I use the same registration in the CFM "standard" (wingtip fences) A320 and in the CFM SL (sharklets version).
The "standard" version is working OK and the sharklet version is not. Both have the atc_id=F-WWBA.
Maybe the specific CFG doesn't work when multiple aircraft use the same registration? Which is weird anyway, because they are in different folders... 🤔
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version