Author Topic: P3Dv4 using GSX customizations intended for P3Dv5  (Read 1816 times)

w6kd

  • Full Member
  • ***
  • Posts: 107
P3Dv4 using GSX customizations intended for P3Dv5
« on: September 11, 2020, 02:24:50 am »
I've got two parallel installations of P3D, one is P3D v4.5HF3, the other P3D v5.0 HF2.  I have Imaginesim's KATL installed into both, and the AFCAD file is named the same in both (KATL_ADEX_ADE_med.bgl) but with different directory paths to each

I have two GSX ini files, one for each version of P3D with the appropriate afcad_path specified in each:

The ini file for P3Dv4 is named KATL-rjs4.ini, and specifies afcad_path = P:\P3Dv4_Ext\Imagine Simulation\KATL Atlanta P3Dv4\scenery\KATL_ADEX_ADE_med.bgl

The ini file for P3Dv5 is named KATL-rjs5.ini, and specifies afcad_path = X:\P3Dv5_Ext\Imagine Simulation\KATL Atlanta P3Dv5\scenery\KATL_ADEX_ADE_med.bgl

When I run P3Dv4, it is loading the customization file for P3Dv5, and not the one for v4...I turned couatl logging on and it says:

Loading user customizations from C:\Users\Bob\AppData\Roaming\Vistuali/GSX\katl-rjs5.ini

When I make customization changes in P3Dv4, it loads and updates the (wrong) KATL-rjs5.ini file.  When I make customization changes in P3Dv5, it also loads and changes the same katl-rjs5.ini file.

So...how do I make P3Dv4 use its respective GSX .ini file?

Regards

Bob Scott


virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: P3Dv4 using GSX customizations intended for P3Dv5
« Reply #1 on: September 11, 2020, 12:28:09 pm »
Are those AFCAD files incompatible with each other, when GSX is concerned ?

Incompatible usually means they have different parking spots, renamed or moved parking spots, or parking spots that exists in a file but not in the other. Or different taxi/vehicle path layouts, or different runways.

If this is the case, perhaps naming the .BGL with the same name is not a very good choice, because GSX assumes that, if an AFCAD is really different, it should have a different name, which is usually the case with the vast majority of sceneries out there. For example, a common practice is to offer different AFCADs, one for AI usage, and one with Static planes and, since the main difference lies in the parking spots, the "static" AFCAD always has a different name, and this works perfectly with GSX, which associates an .INI file with its own AFCAD.

So, in your case, it might be enough to rename one of the AFCAD files, and perhaps make a copy of the GSX.INI with a different name, and edit the AFCAD name in the [General] section of it, to match the renamed file so, from now one, the files will be independent. Or, you can just rename one of them, and start a new GSX profile from scratch, your choice.

It might be worth suggesting to Imaginesim to use different names for their AFCAD, if they are really that different.

If, instead, the differences are minor, and don't affect parkings, taxi layout or runways but only, for example, different Exclusion zones for default objects ( this is the main thing developers have to fix when adapting a scenery to P3D V5: having to deal with a different default scenery ), it's not really a problem using the same profile with GSX and, in fact, it's best this way, so you won't have to do twice the work, just because you are using two simulators at the same time.