FSDreamTeam forum
Products Support => Chicago O'Hare V2 for P3D4 => Topic started by: rjlfry on August 28, 2019, 01:21:43 pm
-
It seems the AFCAD is linked to the jetways if you try to edit the gate codes and compile ADE will come up with an error, if you then let ADE fix this you lose the jetways the same is true at KLAX since the last update, I am trying to edit the parking to stop airlines parking at Cargo gates for my AI, this I have done at other FSDT airports.
-
As explained so many times on the forum, the GSX customization, which includes jetways, is tied to the AFCAD name so, if you really want to change airline codes (no need, since they are already correct, and if you think they aren't, please make a list of the things you wanted to be changed), just be sure your AFCAD has the same name as the FSDT one.
I am trying to edit the parking to stop airlines parking at Cargo gates for my AI, this I have done at other FSDT airports.
You won't be able to prevent this entirely. When there are too many AIs and all the non-cargo parking spots are taken, the simulator will start assigning them to every available parking that is large enough to fit the overflowing airplane, ignoring both the parking type and the airline code.
In addition to that, we assigned non-Cargo codes to such parkings, because some popular AI products, like UT Live, have several cargo AI set a non-Cargo code, so they wouldn't appear on the cargo parking spots if they didn't had the matching non-cargo variant of the code.
-
And as I have explained my other FSDT airports I can edit the AFCAD without affecting GSX as it`s the original cad edited placed in the scenery and tuning OFF the other, GSX 2 still works but now the jetways are tied to the AFCAD in KORD and KLAX, I will try the ADE forums to see if they can come up with something that will ignore the xml error without changing it, or in future ADE will be pointless for users.
Cargo gate codes I use "ABR ,CLX ,GTI ,FDX ,CPA ,AZQ ,UPS ,CKK ,ANA ,DLH ,AHK ,CJT
-
More precisely, the jetways are "tied" to the AFCAD, in a way the AFCAD must first match the name. So, if the only thing you want to do is to change airline codes, which is what you said you wanted to do, as long as the AFCAD has the same name, GSX L2 jetways will surely work.
However, if in addition to "just" changing airline codes for existing parking spots, you'll also change their names or numbers, THEN you'll have a problem, because you'll break the association between the GSX customization and the actual AFCAD.
-
I am not changing the name or number only removing the airline code then adding my own, for example outside the UPS building I will use only one code UPS then only UPS will park, an incoming Caro flight finds the Cargo gates full it will park at a gate of the correct size available not just cargo with the code. As I have found cargo parking at jetways.
https://www.flickr.com/photos/154944674@N05/48636027471/in/dateposted-public/
https://www.flickr.com/photos/154944674@N05/48635669023/in/dateposted-public/
The parking code for this aircraft is RAMP_CARGO.
-
I'll repeat it again:
When there are too many AIs and all the non-cargo parking spots are taken, the simulator will start assigning them to every available parking that is large enough to fit the overflowing airplane, IGNORING both the parking type and the airline code.
In addition to that, we assigned non-Cargo codes to such parking spots, because some popular AI products, like UT Live, have several cargo AI set a non-Cargo code, so they wouldn't appear on the cargo parking spots if they didn't had the matching non-cargo variant of the code.
With "non-cargo" code, I don't mean the airplane type code ( ex. RAMP_CARGO ) but the airline code itself.
Lots of 3rd party AIs have non-Cargo airline codes (for example UAL instead of UALC even if they ARE Cargo ) so, if we didn't had UAL on the Cargo parking spots, for example, they wouldn't go there and would start to fill the passenger terminals too.
-
Which takes me back to in future editing FSDT AFCAD`s will be a no no other developers it`s ok without affecting GSX.
-
Which takes me back to in future editing FSDT AFCAD`s will be a no no other developers it`s ok without affecting GSX.
Why you keep repeating this ? I already explained quite clearly: if you change just the parking codes, without changing parking names and keep the AFCAD name the same, it will NOT affect GSX.
The rest of my explanation about parking code was just to point out they are already fine as they are, but that's entirely irrelevant to GSX so, if you really want to change them, see previous the point.
-
Open up the AFCAD make NO changes then compile and this is what you see.
https://www.flickr.com/photos/154944674@N05/48636880137/in/dateposted-public/
IF you then let ADE fix it you lose the jetways.
https://www.flickr.com/photos/154944674@N05/48636736736/in/dateposted-public/
-
Open up the AFCAD make NO changes then compile and this is what you see.
That's not an error, or course. The compiler reports as error the dummy cross-wind runways ADE places by *itself* to allow multiple runway operations, and is telling they are outside the airport TEST range, since they are intentionally placed very far from the airport, which is a normal.
-
Yes then allowing ADE to fix this you end up with no Jetways they are gone.
The AFCAD complied with no changes just fixed by ADE.
https://www.flickr.com/photos/154944674@N05/48636515468/in/dateposted-public/
The airport after using the compiled AFCAD.
https://www.flickr.com/photos/154944674@N05/48637013282/in/dateposted-public/
No jetways.
-
It also comes down to the coding of your airlines, if you code your Cathay freighters with CPA, instead of CPAC or DLH instead of GEC then you are asking for your airline and cargo traffic to mix parking spots. Setting parking spots to RAMP_CARGO vs GATE etc is also nearly useless. First and foremost you want the right sized spots and the correct parking codes. Do that as well as having enough proper spots for your traffic and you will never have freighters parking at the terminal or airliners in the cargo spots unless it's intentional.
I also deleted the dummy cross-wind runways and compiled as a test and didn't lose any jetways.
-
Yes then allowing ADE to fix this you end up with no Jetways they are gone.
Because you changed the name of the AFCAD!!!
Check your files, your edited AFCAD is now named KORD_ADEP4_rjlfry.BGL, while the original from FSDT you backed up is called KORD_ADEX_FSDT.BGL, that's why you lost the GSX customization.
-
OK at least it`s not affecting my other FSDT airports.
https://www.flickr.com/photos/154944674@N05/48637462751/in/dateposted-public/
https://www.flickr.com/photos/154944674@N05/48637110373/in/dateposted-public/
https://www.flickr.com/photos/154944674@N05/48637602857/in/dateposted-public/
-
OK at least it`s not affecting my other FSDT airports.
Because not all of them use GSX L2 jetways created by a GSX .INI file. If I told you you MUST keep the same name, there was a reason for that.
Also, it's not true that renaming the AFCAD has "not affected" other FSDT airports. It might look like that, because you only noticed the jetways, but there's another GSX customization we use, located in \Addon Manager\couatl\GSX\airports, that contains special customization not possible with an .INI file, that are ALSO tied to the original name of the AFCAD, for example the friendly naming of terminals, and if you renamed the AFCAD, you'll lose that one too.
That's why I keep saying do not change the name. If I'm saying something, it's because there IS a reason for it.
-
I don't change the name ADE does so FSDT airports AFCADs cannot be edited then glad you told me ill bear it in mind.
https://www.flickr.com/photos/154944674@N05/48638267052/in/dateposted-public/
-
I don't change the name ADE does so FSDT airports AFCADs cannot be edited then glad you told me ill bear it in mind.
Please stop saying one cannot edit FSDT AFCADs, because it's just not true. ADE by default creates a project with a certain name adding your initials, so it will Compile an AFCAD with a .BGL name that matches the name of your ADE project.
But if you SAVE your Project in ADE, using the File->Save Airport As menu, and name the ADE project the same as the name of the original AFCAD from FSDT, it will Compile it with the correct name.
-
Or just compile it the way you normally do and then rename the resulting .bgl file to what it's supposed to be named. Personally I keep all sorts of different names for my ADE projects at the same airport and then adjust the compiled bgl name.
Incidentally, I've also changed all of the parking at ORD to Ramp GA and then just ensure good airline codes and sizing and it's looking great. I don't even own ORD, just messing around on the demo for now.
-
Incidentally, I've also changed all of the parking at ORD to Ramp GA and then just ensure good airline codes and sizing and it's looking great.
We always set our previous airports to be Ramp GA, and user complained about us being weird doing that. So, we tried to be as standard as possible with KORD.
Also, I would like to know, even privately by PM or email, what changes you made, and the reasoning behind it.
-
PM sent,
I changed it back to how you used to do it as the FSDT logic was sound. I don't want the stock airport vehicles getting in the way and also that in the real world there is no such thing as Ramp_Cargo, Gate_Small, Medium, or Large etc. Code them right, size them right, and have enough parking on the field and you won't have any issues.
-
So, you wanted input on what people change on your AFCAD's'. For me, I shortened runway 10R/28L so only smaller aircraft (basically RJ's) only use that runway ,and most mainline airliners will now use 10C/28C. (spreading out arrival traffic). I deleted all cargo (airline identified) codes. To me it seems pointless to put the same 500 (I exaggerated) codes in every cargo spot. why not just leave them blank? Cargo aircraft will park at cargo spots (if aircraft config. is correct). The only ones I label are FDX and UPS. I changed the radius of all the parking to conform to my personal aircraft sizes. As far as airline codes, JBU parks at G1/G2 (different sizes as they fly E190's and A320). DAL/DALX parks at E7/E9/E11/E14/E16/E17. ASA at G6/G4. NKS at L5/L7/L9/L11. ACA/ACAX/JZA at E1/E2/E3. FFT at M1-M3. At the international terminal (terminal 5), I removed all airline codes because all aircraft that do not have an assigned gate code will park here which is basically all international carriers. I also reduced the size of several terminal 5 gates to 737/A320 size to accommodate CAY AMX BHS CMP AIJ VIV and VOI which fly narrow body aircraft to ORD. I went to "flightaware" to see what gates were being used most often. I also rearranged the order (list) of runways on the runways page. The runway that is at the bottom (from the way I understand it) will determine the landing direction. I want ORD on either a West flow or East flow, so I put 9R/27L at the bottom and revised the other runways accordingly (-7.9 degrees). This is why I appreciate the option of NOT updating the AFCAD on your FSDT updates! Thanks for a great airport!
Jim B.
-
I deleted all cargo (airline identified) codes. To me it seems pointless to put the same 500 (I exaggerated) codes in every cargo spot. why not just leave them blank? Cargo aircraft will park at cargo spots (if aircraft config. is correct).
I think I already explained the reasoning behind this.
Some popular AI add-on products, such as UT Live, sometimes have Cargo planes flagged with a non-Cargo airline codes. So, if we didn't had any airline codes in the Cargo parking, these planes would end up on the passenger terminals, because they have non-Cargo airline codes, they fit the parking and, being usually larger planes, they might steal some of the precious Heavy Gates on the main terminals.