Products Support > GSX Support FSX/P3D
Floating P3Dv5 jetways at some locations.
virtuali:
--- Quote from: srcooke on May 07, 2020, 03:53:46 pm ---ALL of these airports have floating runways.
--- End quote ---
Ok, that's beyond GSX abilities to fix...
srcooke:
TYPO = Jetways :(
alpha117:
--- Quote from: virtuali on May 07, 2020, 03:37:07 pm ---
--- Quote from: srcooke on May 07, 2020, 02:56:14 pm ---Using the supplied ADEV5 format appears to cause the issue, EDDB is also ADEV5
--- End quote ---
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.
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version