11/10/2022 0 Comments Pmdg 777 pilot response warningThe example below shows getting the state of the left-hand wiper switch and the EFIS mode selector switch on the pilot and co-pilot side: The pilot and co-pilot MCP values) these are arrays of Offsets. The names are the same as in the supplied FSUIPC Documentation. The class contains all the known offsets for the aircraft. With the connection open, call the RefreshData() method to get the latest data. Private pmdg737 As PMDG_737_NGX_Offsets = New PMDG_737_NGX_Offsets () Private PMDG_737_NGX_Offsets pmdg737 = new PMDG_737_NGX_Offsets () This is best done at the class or form level like normal offsets. These all work the same way - Examples below are for the 737įirst declare a new instance of the helper class. I've just released V3.1.24 which has helper classes for the PMDG 737, 747 and 777 offsets, and adds enums for the 747 and 777 Controls. It has to be split into the separate ones matching where the data had to be split.įSUIPC is all about compatibility. There have been at least three different layouts for the PMDG 737 if you include the NGu and NG3 versions and the updates.Ī structural approach can still work, but not just in one structure as in the PMDG SDK. That meant some manipulations to retain compatibility - moving those additions to the end of the extension area. But, worse, it had more data inserted in the middle. That would be okay - it would be split into a different offset area. There were a number of developments of the PMDG aircraft in which their structure was extended. The structure is read directly into the FSUIPC offset area. Unfortunately, the layout of the FSUIPC offsets doesn't match the header file, so that doesn't work.Ĭan you explain this please? By email Unless the following explains your problem: The page title is always on the first row (index 0). Pos Init for example is always on LSK R6 when that particular page is active.(Indent page 1/2). So you won't need to work that out in real time. I'm pretty sure that all the data and commands on a page appear in the same place every time. You would type in the transition altitude and then press the LSK 5 (on the right) to enter the data. The data for this is displayed under it on the right side of row 10. The field name is usually on the row above where the data is shown.įor example, the field name for the transition altitude will be on the right hand side of row index 9. Then you press the relevant LSK key to move that data into the correct field. So to activate 'Pos Init' this would be LSK R6 (Right hand side, 6th button down).įor data entry, the keyboard below the screen is used to enter the data into the bottom row of the screen (left side). Row index 12 might be showing '' on the right. You need push the LSK button that is aligned with the instruction on the same row. The left option will be in the first half of the row text, the right option in the second half. There are keys on both sides of the screen. Starting at the top with LSK 1, this lines up with the Row with index 2.(The third row). You can get an array of rows from the Rows property. The LSK keys are just lined up to the left and right of a particular row of text of the CDU. Reading one offset will likely perform better than reading 100 though.įor the CDU display, there isn't a 'selected' line, so I don't think you need to worry about that. You'll need to define the entire PMDG structure though, converting it from the C definition, so I'm not sure if it will save you much time. I'll give it a go here with a small struct and see if I can get it working. Then use that value to populate a predefined structure. It should be possible to define a single offset of type Byte.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |