Airframe specific aircraft profiles not working (Fenix | MSFS2024)

[disco79stu]

So I try to use airframe specific GSX aircraft profiles with the Fenix A32x in MSFS2024.

When I use - for example - a specific profile named GSX-D-AIUK.cfg for that specific airframe, and save it into (what appears to be where also the default gsx.cfg is located):

... \Virtuali\Airplanes\fnx_32x\A320

it does not load that .cfg when I load the aircraft, but the default one.

Do I have to copy the specific .cfg into a different location?

Thanks for any advice,
Stu

[disco79stu]

Just a thought:

Could it be that GSX doesn't "recognize" what aircraft (airline & airframe reg) is loaded because this info in 2024 is now stored in the livery.cfg (not the aircraft.cfg, as it was in MFSF2020), thus always loading the default gsx.cfg?

[disco79stu]

any comment, devs?
should this work and the issue is on my end, or is this somehow bugged?
I always likes/used this feature (page 77 of the manual btw).

[daan_vb]

It's not just you, I have also experienced this as well....hope a fix can come soon

[disco79stu]

It's not just you, I have also experienced this as well....hope a fix can come soon

Thanks for confirming mate. Yeah, I hope this gets fixed in an update... Cheers

[disco79stu]

Here's my log for my attempt to load an airframe specific profile.

I added and modified a GSX-D-AEWQ.cfg file inside AppData\Roaming\Virtuali\Airplanes\fnx_32x\A320
but when starting the fight with D-AEWQ it loaded only the defaut gsx.cfg from that folder.

[virtuali]

The problem is caused by the fact the atc_id in the aircraft.cfg is G-FENX, while the one from Simconnect is D-AEWQ, but GSX gives an higher priority to the one in the aircraft.cfg, so it looks for this file:

[00:00:39.500] Airframe-specific GSX-G-FENX.CFG not found

We set the aircraft.cfg with an highest priority, because if you change the callsign in the sim (and maybe forgot you ever changed it), it would keep using the same airframe no matter which airplane you loaded, and this used to confuse users that assumed it was a GSX bug, so we reversed the priority to prevent the custom callsign to take over.

The issue is, with modular aircraft, it might make sense to use Simconnect by preference instead, with the obvious caveats that if you change the callsign, the profile wouldn't work anymore.