Skip to content

fix(pmdg): read all 737 landing switches, add logo and wing - #35

Merged
nabeelio merged 1 commit into
releases/2.0from
fix/pmdg-737-lights-2.0
Nov 16, 2026
Merged

nabeelio merged 1 commit into
releases/2.0from
fix/pmdg-737-lights-2.0

Conversation

@nabeelio

Copy link
Copy Markdown
Member

Summary

Follow-up to #30. The PMDG 737 FSUIPC config read only the left fixed landing switch (0x64F6), so flights flown on the retractable lights, or with only the right fixed light on, logged landing lights off. Logo (0x64FF) and wing (0x6502) switches exist in the NGX offset map but were disabled.

  • Landing: one 4-byte read at 0x64F4 covers LTS_LandingLtRetractableSw[2] (on when 2) and LTS_LandingLtFixedSw[2] (boolean); any of the four lit counts as on.
  • Logo and wing: 1-byte reads, on when 1.

Evidence

Addresses and widths from Offset Mapping for PMDG 737NGX.pdf (bottom overhead block: 64F4 retractable[2], 64F6 fixed[2], 64FF logo, 6500 position, 6501 anticollision, 6502 wing). npm run build passes; the compiled dist/aircraft/PMDG_737_FSUIPC.js carries the new offsets.

Merge Danger

Low. Only the 737 FSUIPC config changes. Pilots who previously got landing lights "off" with the retractable lights on will now get "on"; no other feature changes. Ships to 2.x clients on the next release tag.

@nabeelio
nabeelio merged commit 722dc99 into releases/2.0 Nov 16, 2026
2 checks passed
@nabeelio
nabeelio deleted the fix/pmdg-737-lights-2.0 branch November 16, 2026 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant