Traffic 360 & KLAX

[72westy]

I was wondering if this can be resolved. The A380's seemed to be parked at the wrong gates. AI traffic is at 20% as is GA traffic. No road traffic. Running FSX w/ Acceleration, (UTX complete series), (GEX comp. series)

System specs:

Windows 7 Ultimate 64bit SP1
Corei5 2500K (non clocked)
GA-Z68XP-UD3 Gigabyte (BIOS F-10)
8GB G-Skill DDR3 RAM
XFX Radeon HD 1GB DDR5 (CCC-12.10)
1TB Hitachi 32mb cache
1TB Maxtor 32mb cache
Sound Blaster X-fi Xtreme Gamer
LG Blue Ray writer DL
Antec 650w PSU
Rosewill Black Challenger tower

[virtuali]

First, be sure you use the KLAX-supplied AFCAD, meaning you should remove any AFCAD that might have been eventually installed by the Traffic program.

Other then that, the parkings in any scenery (this is not really related to KLAX) are assigned by FSX checking the airplane size in the MDL file of the AI airplane, it might be worth checking if is set correctly in those A380, THEN we might check it against the radius in the scenery AFCAD.

But before doing anything, be sure you use the AFCAD that comes with KLAX.

[72westy]

First, be sure you use the KLAX-supplied AFCAD, meaning you should remove any AFCAD that might have been eventually installed by the Traffic program.

Other then that, the parkings in any scenery (this is not really related to KLAX) are assigned by FSX checking the airplane size in the MDL file of the AI airplane, it might be worth checking if is set correctly in those A380, THEN we might check it against the radius in the scenery AFCAD.

But before doing anything, be sure you use the AFCAD that comes with KLAX.

How do I check the AFCAD file/s?

Much appreciated.

[virtuali]

How do I check the AFCAD file/s?

A way could be using GSX parking customization editor, it will indicate what AFCAD is in use.

[72westy]

How do I check the AFCAD file/s?

A way could be using GSX parking customization editor, it will indicate what AFCAD is in use.

Sorry, I do not have GSX.

[virtuali]

Sorry, I do not have GSX.

GSX is entirely free to use at FSDT airports so, there's are no reasons not to install it.

GSX includes all the features that we previously included in the scenery as ParkMe, but it does much more and, in fact, you should consider it as an additional piece of the scenery that must be installed, with the advantage that, instead of enlarging the size of *every* scenery installer to include the GSX features, we have a separate download that will be downloaded only once, keeping the scenery installers smaller.

[72westy]

The AFCAD in use according to GSX is as follows: FsDreamTeam/KLAX_V2/scenery/KLAX_AP.BGL

What next?

[virtuali]

The AFCAD in use according to GSX is as follows: FsDreamTeam/KLAX_V2/scenery/KLAX_AP.BGL

That's the correct one. Now, you should do the other step which I've already indicated in my previous message:

it might be worth checking if is set correctly in those A380, THEN we might check it against the radius in the scenery AFCAD.

So, try an example of a parking at KLAX that accepts an A380 when it shouldn't, and we can check the radius in the AFCAD.

Note that, sometimes the radius in the AFCAD has to be specified on a certain size, otherwise the jetway will not move so, first we need to check this specific case, and then we can decide if it would be possible to make it smaller, assuming the problem IS the AFCAD radius, and not the A380 .MDL file which is too smaller instead.

[Dave_YVR]

 AI parking in FSX is based on the entry wing_span in each models aircraft.cfg. He can simply check his aircraft.cfg from the A380 to see if it says something very similar to wing_span=261.0 .

[72westy]

AI parking in FSX is based on the entry wing_span in each models aircraft.cfg. He can simply check his aircraft.cfg from the A380 to see if it says something very similar to wing_span=261.0 .

Any tutorials/steps on how to do this? I've read over the manual but it's vague to me.

[Dave_YVR]

 I opened the KLAX_AP.bgl file with AFX and it needs some bigger parking. The TBIT has 36m parking and therefore A380's will not use it. The A380 needs 40m.

 Additionally, there is still many gates coded COA, and also USA. To stay up to date, these should be changed to their correct codes.

[virtuali]

I opened the KLAX_AP.bgl file with AFX and it needs some bigger parking. The TBIT has 36m parking and therefore A380's will not use it. The A380 needs 40m.

But the OP reported the OPPOSITE problem, that A380 were parking when they shouldn't, in parking that seemed to be too small for them.

[72westy]

I opened the KLAX_AP.bgl file with AFX and it needs some bigger parking. The TBIT has 36m parking and therefore A380's will not use it. The A380 needs 40m.

But the OP reported the OPPOSITE problem, that A380 were parking when they shouldn't, in parking that seemed to be too small for them.

The screen shot above on the left shows the A380 parked in between 2 others. This was just after starting my flight in the helo (loading of FSX). It did not pull in there it was already there from the get go.

[Dave_YVR]

 Opps, sorry my bad.. Wow, looking again the 380 in your screen it's parked in a 24m spot.. it should be using no smaller than 40m.

 So that being said you should have a look at your aircraft.cfg for your AI A380 (your job to find and edit). Find the entry "wing_span="   and it should read 261.10 or something very similar, if not edit it to say 261.10

[72westy]

Opps, sorry my bad.. Wow, looking again the 380 in your screen it's parked in a 24m spot.. it should be using no smaller than 40m.

 So that being said you should have a look at your aircraft.cfg for your AI A380 (your job to find and edit). Find the entry "wing_span="   and it should read 261.10 or something very similar, if not edit it to say 261.10

Looking in my Traffic 360 AI folder within FSX for the A380 (4) of them I have the following for the wing span within the aircraft.cfg folders for each: wing_span=94.75

The (4) folders are within the folder FSX/SimOjects/JFTraffic360/

JFAI_A380_Cargo_g1
JFAI_A380_Cargo_g2
JFAI_A380_g1
JFAI_A380_g2

As for the actual wingspan I've seen 261.8, 261.10, 261.6 etc...