Hi, I am using the A32NX from FBW aircraft, and it happen near everytime : in the customize aircraft menu, there is no Developer-provided data, it's very rare for it to appear, so it's only Internal GSX database.
Are you using a livery variation? If yes, that's normal, since the developer-provided GSX.CFG is read from the main airplane folder.
I also have this error in the log file "Airframe-specific GSX.CFG file for YEEHAW not found in SimObjects\Airplanes\FlyByWire_A320_NEO, using a default GSX.CFG file", I wonder why because the file does really exist at this very specific location, it is exactly called GSX.cfg, it is the one I copied.
That's normal either, and it's not an error, it's just an indication that, since you don't have an airframe-specific configuration for the loaded airplane, it will use the standard one.
I also find this line in the log file : pathToUserCfg() DOES NOT EXIST!!! "<path not found>\Usercfg.opt" it is everywhere in the log file, it's nearly spamming. Any idea why ?
This is not normal instead, and it means the Usercfg.opt file hasn't been found in both the MS Store and the Steam path, and it's very likely caused by the fact you have installed MSFS with one user account, and are running GSX with another one.
Also, why couatl need to be started with admin priviledge ?
It doesn't, and we don't install it that way.
The thing is that couatl is automatically started with MSFS, but since my user account is not admin, it is showing a "GSX has been disabled on this airport by user settings" message
That's a completely different issue and, it's not related to the Couatl engine, which doesn't require an admin account, it's caused by the activation, which is made from the FSDT Installer when you installed it, and that one always requires admin permissions to install so, the real issue, which is basically the same that cause the Usercfg.opt path not being found, is you activated the product with one user (the "Administrator") but when you run as your limited Windows account user, it's not the SAME user, so there won't be any activation there.
The easiest solution is, grant Admin permissions to your limited user account, and reactivate again there, so you won't have to start Couatl as Admin, because you WILL be an admin.
The more complex solution, if you don't want to become Admin, is to manually activate in the limited user, as explained here:
https://www.fsdreamteam.com/forum/index.php/topic,28730.msg187338.html#msg187338Also, do you plan to make it possible to have GSX jetways replacement with 3rd party airports?
It might be possible for non-encrypted (non-Premium or World update) handcrafted airports but, for anything that is encrypted, it won't be feasible from a possible legal point of view, because we would end up distributing files containing data that was actively protected from being dumped.
And to finish, I have a problem with sounds played by GSX, some of them are only playing in my right speaker. For example, all the sounds effects played with the Catering service are played on my right speaker, it's like right-mono channel and it's not 3d localized, so I can move my cam anywhere, I can go very very far with the drone camera, but the volume doesn't change, and it's playing on my right speaker only.
The problem is that we don't have the actual Camera position in MSFS, because there's no Camera API like P3D, and because we want to be absolutely sure to not touch the MSFS .EXE and potentially cause crashes, we don't use in-memory hacking like we did in FSX to extract it (FSX didn't had a Camera API either).
Without the position of the camera (eyepoint = your ears) in real time, the positional audio the audio engine normally support, doesn't follow the eye position if you move it.
Right now, the Camera API is the most requested feature in the MSFS devs forum, so we can only hope it will eventually arrive so, it should be very easy to add it to the MSFS version, like we had in FSX/P3D, since the audio code is identical, but it needs the actual camera position to work fully in 3d.
