Floating P3Dv5 jetways at some locations.

[srcooke]

Hello Umberto,

At some addon airports in P3Dv5 such as LIMC developed by David Rosenfeld and published by Aerosoft and also EDDB by Limesim Team, 29Palms again published by Aerosoft when reloading the sim GSX jetways are floating way overhead. Both scenery's are published for v5.

When added via GSX customization they are in the correct location and correct elevation indicated in the gsx dialogue. Having reloaded the sim and with the jetways floating opening the gsx customization reveals no change in the airport elevation at 233.78m, applying a gsx airport elevation adjustment only results in adding trailing zero ie 233.780. Having applied this the jetways then load at the correct location once again.

This is occurring for other users also.

[alpha117]

Same issues here also

Thanks

[virtuali]

Same issues here also

With "same issue here", you mean on that SAME airport ?

Do you have something from OrbX installed ? Are the OrbX layer correctly set *BELOW* all your airports ?

[alpha117]

Yes same airports and no ORBX installed

[srcooke]

Here it can be seen that some second jetways remain in place at LIMC but the majority are floating until the altitude is reset in the airport customization.

Only a few ORBX airports and Global installed, Pilots 2020 mesh.

[virtuali]

but the majority are floating until the altitude is reset in the airport customization.

But that's precisely what you are supposed to do to fix those altitude conflicts caused by different sceneries in conflict setting different altitudes. Of course, if you Apply, it will saved for the next time in your custom GSX .INI profile.

[srcooke]

Of course, if you Apply, it will saved for the next time in your custom GSX .INI profile.

There is no change in the gsx .ini file as the entry is exactly the same at 233.78 ( 233.780 in the customization tool ) for the LIMC file as attached above.

On next load the jetways are in the air despite the .ini entry except for the odd one or two again as per the image above.

[srcooke]

I have loaded the P3Dv4 file ADEP4 afcad and everything works perfectly ok.

Using the supplied ADEV5 format appears to cause the issue, EDDB is also ADEV5

[virtuali]

Using the supplied ADEV5 format appears to cause the issue, EDDB is also ADEV5

GSX surely supports the P3D V5 .BGL format, otherwise it wouldn't be able to open default airports. But as I've said, if you said the issue is fixed by clicking the airplane icon on the Ground elevation tab, then how's supposed to work, when there's an altitude conflict.

[srcooke]

There is an obvious issue with the ADEV5 file supplied by different developers for LIMC, EDDB, GCLP and published by Aerosoft .

ALL of these airports have floating jetways.

Using the adjust elevation tool DOES NOT fix the issue, it temporarily brings the jetway to ground level until the scenery is loaded next time.

[virtuali]

ALL of these airports have floating runways.

Ok, that's beyond GSX abilities to fix...

[srcooke]

TYPO = Jetways

[alpha117]

Using the supplied ADEV5 format appears to cause the issue, EDDB is also ADEV5

GSX surely supports the P3D V5 .BGL format, otherwise it wouldn't be able to open default airports. But as I've said, if you said the issue is fixed by clicking the airplane icon on the Ground elevation tab, then how's supposed to work, when there's an altitude conflict.

The format of the P3D V5 AFCAD has changed, and as already pointed out it looks like the way handling the elevation data for the airport. In V4 the elevation data in the GSX .ini is set to 2 decimal places (233.78), now in V5 it looks like it is now set to 3 decimal places (233.780), yes that zero seems to make all the difference. The  can be confirmed by looking at the ground elevation tab before press the airplane and you will see it has 2 decimal places. Now press the 'airplane', not that the 3rd decimal place is added and the jetways will now descend to their correct places. Now look in the .ini file what do you see?. Close the SIM and restart, now look in the ini file again back to 2 decimal places not 3, and the circle starts again.

Could this be investigated to confirm that GSX now needs to save 3 decimal places and not the 2

Many Thanks

[alpha117]

Hopefully test confirms the issue

Before starting  SIM
1. Open GSX.ini for airport and change the elevation form 233.78  to 233.780
2. save and close ini
3.start SIM and load at gate..do not change anything..note jetways are 'cleared final'
4. Open airport 'Customise airport positions and compare the ini elevation and the airport position elevation
5. Why has GSX not read the elevation data from the ini, or has it and truncated the data to 2 decimal places?



6. Now press the airplane and notice the elevation change to 233.780  and the jetways safely land and taxi to the correct positions
7. Also note tha GSX has written to the ini file (file modified time updated)
8 Look at the elevation data it says 233.78 and NOT what was in the airport screen(233.780)

[virtuali]

I would like to know what's the mathematically difference between 233.78 and 233.780 and how this could result in a visible change of altitude since, even if GSX truncated the last 2 decimal places, it's 1 cm difference in the worse case.

But of course we'll check this.