• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA Jetway AircraftParameters

N

nz255

Messages
393
Country
newzealand
Hi Jeff,

I've been trying to test the jetways in FSX as I can't get it going in p3dv2. I think it's because it doesn't ask me to allow the dll?

Anyway, to adjustments to the AircraftParameters file update on the fly? Or is the jetway hardcoded to those parameters?
I've been trying to add 3rd party aircraft using the atc_model tag (eg the PMDG 737 which has the tag of '737-800' for the 738) but on trying to activate the jetway I get the error messages, "Target out of leg length range (extension)". It has exit listings in the aircraft.cfg.
I've used the same parameters of the default 737 that come with the samples. The default 737 docks fine.

Another thing, it seems the repaints for the NGX (through the PMDG operations centre) add more and sometimes different atc_model tags to the repaint variant than what's in the [General] area. How would code handle this? A lot of people will have this issue so probably can't rely on them updating their aircraft.cfg's.
SprVMEH.png



Note, I've jumped between using the 738 as an example but using the 737 for testing.
Here's my AircraftParameters.ini trying with both atc_model codes but I still get the message "Target out of leg length range (extension)".
Code: 
[737-700]
1L = 2.0, -0.2, 7.0, 1.1, 1.35

[B737]
1L = 2.0, -0.2, 7.0, 1.1, 1.35

lkvUcVw.jpg




Also I can't get the dll connection test text to display, but the jetway move for the default aircraft so I figure that shouldn't matter.
 
The parameters are not dynamic, they are hard coded in this file. The jetway system just reads it out. Also, it only takes the atc_model value from the [General] section, as this represents all models variants.

The default B737-800 uses B738 (which is the correct ICAO aircraft type designator) and this sample entry is provided in the SODE v1.2 release. So in theory, when you change the aircraft.cfg of the PMDG 737-800 to have atc_model=B738 in the [General] section, the system would have all information it needs.

Or you can make a new section in the AircraftParameters.ini having another parameters...which shouldn't be the case, because all 737 should have the same door dimensions, shouldn't they ;)

The entire system should still move, even if it doesn't find the door parameters, because they are only needed for the hood animation. The docking itself is computed by the door position which is stored in the aircraft.cfg [Exits] section.

Concerning the leg length message: This is shown when the jetway is reaching its lowest or highest point and still can't reach the door. One scenario would be that the aircraft is too near to the jetway. But you said the default 737 was served ok, so I suspect the exit position of the PMDG aircraft is lower than the default one?
The exit position should be in the middle of the door, also the stock FSX jetway makes this assumption.
Try to move the aircraft a bit away and see if the jetway is then able to dock.

[EDIT]
I have uploaded new installers thanks to your report of broken dll.xml paths. Uninstall and reinstall please and I hope it will work in P3D then.
[/EDIT]
 
Thanks. I understand now, I didn't realise the parameters file was just for the hood.
I'll have a look at the pmdg exit parameters in the aircraft.cfg

Also I can crash fsx and p3d if I use the reset all button from the sode menu after having used the jetway.
 
I got hold of the aircraft.cfg of a PMDG B737. Compared to the default B737, the PMDG version sits a tad lower on the tarmac. This minor difference (about 2 feet) was enough that the jetway model is hitting its geometric limits. I have created a more "flexible" jetway model for you and I hope this one will get low enough.

Unzip both files into SimObjects/Misc/SODE/model.jetway

So it's about how the jetway model is designed in gmax.

Reload all button: Strange, I can hit that button all day long, but that's like everything on the developers machine, it works:D...anyone else experiencing this?
 

Attachments

Jeffrey Stähli said:
The entire system should still move, even if it doesn't find the door parameters, because they are only needed for the hood animation. The docking itself is computed by the door position which is stored in the aircraft.cfg [Exits] section.
Click to expand...
Just so you know to update the document, this statement contradicts the manual.
2.1 AircraftParameters.ini
SODE uses that entry in the aircraft.cfg to retrieve the door parameters from the AircraftParameters.ini. If it doesn't find the parameters, the jetway won't move!
 
Good catch! I changed the jetway behaviour in the last minute before release. I'll update the document with SDK v1.1
 
You must log in or register to reply here.
Back
Top