Products Support > GSX Support FSX/P3D

Aiframe specific config

<< < (2/4) > >>

virtuali:

--- Quote from: CS-TMT on April 04, 2022, 03:09:41 am ---It would be useful if there is a note in the manual that when using the airframe specific config, the main/built-in gsx.cfg should be removed for it not to be used instead of the specific config.
--- End quote ---

That's not how's supposed to work. By design, the specific config will have an higher priority over the generic one. I just re-checked it now, and it works as it should.

What you must keep in mind, is the location of the airplane customization file matters more than the generic/specific config. Which means, if you have an airframe-specific CFG file in the Airplane own folder, and a generic CFG in the %APPDATA% folder, the one in %APPDATA% will ALWAYS take precedence, even if it's "generic", and this if of course correct because, if it wasn't like that, you would lose the ability to customize an airplane that came with an airframe-specific config from the developer.

The airplane own folder should only be used by developers to supply a GSX configuration, but everything YOU do, should always be placed in the %APPDATA% folder ( as for my previous instructions ), because everything located there will always get the highest priority, regardless if it's specific or generic and, of course, *within* the same location, the specific will get higher priority of the generic so, consider the following situations:

1)
GSX.CFG in P3D\Simobjects\Airplanes
GSX-F-WWBA.CFG in P3D\Simobjects\Airplanes
NO folder for that airplane in %APPDATA%\Virtuali\Airplanes

GSX will use GSX-F-WWBA.CFG, if you select that variation, because the airframe config takes precedence over the generic config, and there's *nothing* in %APPDATA%


2)
GSX.CFG in P3D\Simobjects\Airplanes
GSX-F-WWBA.CFG in P3D\Simobjects\Airplanes
GSX.CFG in %APPDATA%\Virtuali\Airplanes

GSX will use GSX.CFG, EVEN if you select the F-WWBA variation, because anything in %APPDATA% will take precedence over any file in Simobjects\Airplanes.


3)
GSX.CFG in P3D\Simobjects\Airplanes
GSX-F-WWBA.CFG P3D\Simobjects\Airplanes
GSX.CFG in %APPDATA%\Virtuali\Airplanes
GSX-F-WWBA.CFG in %APPDATA%\Virtuali\Airplanes

GSX will use GSX-F-WWBA.CFG, if you select that variation, because the airframe config takes precedence over the generic config, since they are both in the highest-priority folder.

CS-TMT:

--- Quote from: virtuali on April 04, 2022, 09:30:16 am ---What you must keep in mind, is the location of the airplane customization file matters more than the generic/specific config. Which means, if you have an airframe-specific CFG file in the Airplane own folder, and a generic CFG in the %APPDATA% folder, the one in %APPDATA% will ALWAYS take precedence, even if it's "generic", and this if of course correct because, if it wasn't like that, you would lose the ability to customize an airplane that came with an airframe-specific config from the developer.
--- End quote ---
Dear Umberto, thank you for the extensive explanation! I was not aware of this part that I quoted from you, regarding the priorities.
However, the issue I am having is going against what you say.
So, I have the generic/built-in configs for the FSLabs Airbuses in %APPDATA% (none of them in P3D\Simobjects\Airplanes), that is, the gsx.cfg. Now, having the Airbus house colours for test flights, it's somewhat unrealistic for me that the Aircraft that only loads the crew gets a set of stairs in both door 1L+4L, the same for the catering/service doors 1+4R, so I created a specific config gsx-F-WWBA.cfg (being F-WWBA the registration as shown in the atc_id line) removing doors 4L+R from GSX services for that particular registration and placed the cfg file in the same folder where the generic gsx.cfg is, on %APPDATA% then launched the simulator (P3Dv4.5 HF3). Albeit having the customised specific cfg for that aircraft, it loaded the main generic config. Removing the generic cfg then it loads the customised specific config ???
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)?

virtuali:

--- 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 ---

Then, assuming you want to apply the same modifications to both, you must copy the airframe-specific .CFG in both folders.

CS-TMT:
Yes, I would imagine that, but the airframe-specific is not working on either of the two. Could it be because of the repeated registration?

CS-TMT:
So as you cansee, I haveloaded the FSL A320 with sharklets (CFM version), seen both in the texture as well as in the atc_id of the aircraft.cfg.
I have the specific GSX config file in %APPDATA% with both passenger exit 4 (door 4L) and Service 2 (door 4R) removed. However when calling GSX, both stars appear and move to doors 1 and 4L and two catering trucks appear and dock to doors 1+4R. In fact you can see that both exits are still active in the customization menu.The only way for these changed to take effect is if I change the generic GSX.CFG ???
I tried reinstalling/updating GSX but it didn't change anything. Tried both a saved flight (done with Lorby-SI WAMA) and a fresh flight and it didn't matter.

Navigation

[0] Message Index

[#] Next page

[*] Previous page