MSFS2020 FSLabs A321neo Door Problem

[RaZerWarfare]

I am using the FSLabs A321neo and noticed something. I am using Self-Loading-Cargo and noticed that SLC does not recognize the Doors when I am using GSX Stairs, but when I am using the Jetway it detects it and opens the Door in SLC. It's just that when I am using Stairs in GSX, nothing happens in SLC. SLC should use the Data from FSUIPC. Any help?

[John Dowson]

SLC probably uses FSUIPC's doors offset, 0x3367. This is th ecomment on that offset:

Quote

This byte shows doors that are open, one bit per door:
    2^0 = Exit1 … 2^3 = Exit 4.
Doors' states depend upon aircraft position (e.g. ramp, gate, or connected to jetway) and don't respond. Further information / Asobo support required. See 

for further info

Take a look at that referenced post - this looks to be the same issue. You could try logging offset 0x3367 (as U8 in hex) to see if/how it updates both with and without GSX.

Not sure if this is a GSX issue or an Asobo issue. If there is something else that holds the doors state when using GSX, perhaps some lvars, you could use these and write a lua script to spoof the reading of the doors offset to the correct value.

I don't have GSX (or SLC) so I can't really look at this in details If you can log that offsets values for when using GSX and not, and can find something else that does hold the correct door state, I can show you how to use this in a lua to spoof the reading of that offset by SLC,.

[John Dowson]

I have looked into this further and the EXIT OPEN simvar is now deprecated in MSFS2020, and marked as legacy in MSFS2024. It may still work in some aircraft, but may not be reliable.

It looks like you now have to use the INTERACTIVE POINT OPEN / INTERACTIVE POINT GOAL simvar(s) instead, and the key event TOGGLE_AIRCRAFT_EXIT / TOGGLE_AIRCRAFT_EXIT_FAST  to open/close the doors. Both are indexed (I presume) either by door number or by the following:
        0: Main exit
        1: Cargo exit
        2: Emergency exit
        3: Fuel hose
        4: Ground Power cable

I have made a note to look into this further when I have time, probably at least not until November.

John

[John Dowson]

For the next release of FSUIPC7, I have added:
     INTERACTIVE POINT GOAL at offset 0x341B
     INTERACTIVE POINT OPEN at offset 0x3424
both are 1 byte, with each bit indicating the index number (e.g. 0x341B bit 4 is INTERACTIVE POINT GOAL:4).
This won't help your problem at the moment, but if you could log these offsets, as well as offset 0x3367 (EXIT OPEN), all as U8 in hex, this may shed a light on what is being used.

It is possible to spoof the reading of the existing door offset (0x3367 for EXIT OPEN) to these new offsets, but most probably the bits referenced will be for different doors.

I don't have the FSL A321neo, or GSX/SLC, so cannot test with these. I looked at the FSL A321, but that just seems to use the EXIT OPEN offset.

Anyway, maybe try the attached and add the offset logging for those 3 offsets (all as U8 in hex), and we can see what this tells us.

John

FSUIPC7.exe