Paul Henty Posted May 2, 2021 Report Share Posted May 2, 2021 Hi John, I think you uploaded the wrong document - this one you attached doesn't have the arrays and still has COMM_ReceiverSwitches at 6C58. Paul Link to comment Share on other sites More sharing options...
John Dowson Posted May 2, 2021 Report Share Posted May 2, 2021 58 minutes ago, Paul Henty said: I think you uploaded the wrong document So I did, sorry about that - here is the correct/latest version: Offset Mapping for PMDG 777X.pdf Link to comment Share on other sites More sharing options...
Paul Henty Posted May 2, 2021 Report Share Posted May 2, 2021 Sorry John, one more error: FIRE_APUHandleIsUnlocked isn't an array, it should be FIRE_EngineHandleIsUnlocked to match FIRE_EngineHandleIlluminated. I've double checked against the .h file and all the others seem okay. Paul Link to comment Share on other sites More sharing options...
John Dowson Posted May 2, 2021 Report Share Posted May 2, 2021 So it is - corrected: Offset Mapping for PMDG 777X.pdf Link to comment Share on other sites More sharing options...
Paul Henty Posted May 2, 2021 Report Share Posted May 2, 2021 Thanks. I also noticed the addresses for some of the old offsets seem to have changed now... Everything from FMC_CruiseAlt onwards has moved 1 byte forward FMC_PerfInputComplete has typo: 6C20 FMC_DistanceToTOD onwards have been shifted forward 4 bytes. Is this intended? Paul Link to comment Share on other sites More sharing options...
John Dowson Posted May 2, 2021 Report Share Posted May 2, 2021 34 minutes ago, Paul Henty said: Everything from FMC_CruiseAlt onwards has moved 1 byte forward Its the same as it previously was (i.e. in FSUIPC4/5). When I originally did the update, there was no structure packing specified so I updated to 1 byte packing. However, in a later iteration I reverted back to 4 byte packing. 35 minutes ago, Paul Henty said: FMC_PerfInputComplete has typo: 6C20 Ok, corrected. 35 minutes ago, Paul Henty said: FMC_DistanceToTOD onwards have been shifted forward 4 bytes. Is this intended? Yes, due to the 4-byte packing. I am still waiting someone to verify this is correct by checking the data for COMM_ReceiverSwitches[0] at offset 6C5A. If that has the correct data, everything else should be ok. John Offset Mapping for PMDG 777X.pdf Link to comment Share on other sites More sharing options...
Paul Henty Posted May 2, 2021 Report Share Posted May 2, 2021 Quote checking the data for COMM_ReceiverSwitches[0] at offset 6C5A If it is then WheelChocksSet must be 6C60. Paul Link to comment Share on other sites More sharing options...
John Dowson Posted May 2, 2021 Report Share Posted May 2, 2021 Offset Mapping for PMDG 777X.pdf Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now