John Dowson

Your best bet for this is the MobiFlight spreadsheet - see https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=11806850

You have defined the offset to hold SD, a signed double-word of 4 bytes, so you should write it as 4 bytes. But, the size/type of the offset should match that of the lvar, which is a flag (ie. 1 or 0), so define it as UB, an unsigned byte. And write either 0 or 1 to it for off/on.

No, that for this - it does say to use the key code following (or after may be better) the letter 'K'.

Excel can read/write ODS files. I don't have an Excel license, and I generally prefer to use/support Open Software rather than payware. And I'm a unix/linux/ultrix/maxOS guy really - only been developing in Windows for 3 years now, since I rook over FSUIPC dev & support from Pete. Note that this is a temporary document, to be used as a supplement to the Offset Status pdf. I am planning on merging them to generate a new document when I get time, hopefully this month.... No, I said it was contained in the zip archive you downloaded, i.e. in the FSUIPC7.zip or Install_FSUIPC7.zip, depending upon where you downloaded it from. Sorry about the confusion!

No problem - I should have found that User Contribution post earlier to have saved us both some time!

I attached the spreadsheet not an archive! Its a .ods file - an Open Document Spreadsheet. You can open it with OpenOffice (Calc) or Excel.

I attached it in my previous comment! The spreadsheet is included in the zip file, it is not installed into your FSUIPC7 documents folder.

Sorry, I don't understand... Look at that spreadsheet on lines 1545 (0x66C0) and 1589 (0xA000), both documented as 'Free for general use'. I've attached it, in-case you are looking at the wrong file. John offsetStatus-v0.25.ods

I think they work for some aircraft in FSUIPC4 but not all. You will need to define the module as: Module="PMDG_MD11.DLL" This post may help - in fact, this already includes mouse macros for the lights in the MD11, so you may want to use this: John

I meant FSUIPC Mouse-macros, i.e. macros that emulate mouse actions in the UI - see P40 of the Advanced User manual. If you cannot find any events/controls that work, and writing to the lvars doesn't work, then try mouse macros. Do the logging first, as it is also not guaranteed that mouse macros will work in FSUIPC4 as it depends on how the a/c is implemented. Or are you saying that they don't work for the MD11?

If the value changes but the lights are not activating, I suspect that they are read-only (or non-active) lvars. Do the standard light controls not work (or the light offsets)? Have you tried logging Evenbts and operating the lights from the UI, to see what, if any, events are logged? If any are logged, you can use/assign to those. Many PMDG aircraft also come with there own SDK which include custom controls for such things, but I don't know if this is available for the MD11 - please check. If not, you could try using Mouse Macros. May also be worth checking on the PMDG forums as well. Btw, which FS and version of FSUIPC are you using?

It is giving you the error: *** LUA Error: C:\Users\Stu\Documents\Prepar3D v5 Add-ons\FSUIPC6\autorecord.lua:16: 'end' expected (to close 'function' at line 3) near '<eof>' This is a problem in the script that Pete posted: else if agl < 450 and aglhigh then should be elseif agl < 450 and aglhigh then With the space, it expects another 'end'. I will correct.

Did you try logging the lvars to see if the values changed? Maybe also worth logging buttons & keys to see what is happening. Which aircraft are you using? It is also possible that the lvars are read-only, and you need to use another method to control.

Ah, sorry - they are assigned to different buttons - 22 and 23. Try using two macro files (as really an lvar should only appear once in a macro file). Use the set control in both, but with a parameter of 1 to turn on, and 0 to turn off. I'm not sure of the behaviour if using the same lvar multiple times, even if they have separate actions. Alternatively, try logging the lvar values once you toggle or set - do they change?

So now you have it set to both toggle the three lights (assignments 6,7,8), and then set them all to off (using the set control with a parameter of 0 on assignments 9,10,11). Try removing the last 3 assignments (the set ones) and just use the toggle controls.

Maybe try running FSUIPC? You should see something in your log - here's mine: John

If writing as SD (signed Double), you need to read as a FLT32. Alternatively, skip the size: 13=A32NX_HYD_BRAKE_ALTN_ACC_PRESS=0x66D5 and read as a FLT64. S32 is a signed 4 byte value and will be an int, SIF32 is a 16bit/2byte integer + the fractional part in 16bits/2bytes. (see P13 and P43 of Advanced User Guide)

They are available from www.fsuipc.com or from the Download Links -> Useful Additional Programs section of this forum. John

Lua scripts are the way to achieve such things in FSUIPC! Check the User Contributions section - there may be something similar there that you can use or adapt for your use. Also, event.intecept() is probably not the function you need, as this intercepts writes from 3rd party applications, not internal FSUIPC writes. You would need to use the event.offset() function on the plane altitude, offset 0200 or 0B4C.

Sure. You can have a lua script monitoring for events using event.intercept() on offset 0x0570, which is the plane altitude. In the handling function, you can read the ground altitude offset (either at 0x0200 or 0x0B4C, depending upon accuracy required) to determine the AGL. You can then test that value and do whatever you like - e.g. send keystrokes to the FS via offset 0x3200, or send controls to the FS via offset 0x3110. John

Did you get any errors? Can you check the windows event viewer please and see if there is a crash report there, and if so show it to me. Problems with installation are usually due to nor having the correct VC++ redistributables installed. Try uninstalling any of the VC++ redistributables you have installed from 2015, 2017 or 2019, and then download and install the combined packages (both x64 and x86) from https://support.microsoft.com/en-in/help/2977003/the-latest-supported-visual-c-downloads. Then try again.

Yes, thats the latest released one, not v25 - I update the version locally when released, so I'm on v0.26. Sorry about that. Yes, sorry - missed that for some reason... Internally, all lvars are stored as 8 bytes. You can define the type/size as needed to hold the values that you want to use and FSUIPC will convert/cast to that size/type. Makes sense to use the size defined by the lvar I guess, but if its,say, a flag (0/1) and is defined as an int, you are better off just using a byte. As you say, the main thing os to make sure that you are reading the offset with the appropriate size/type function for the defined size/type.

👍 But do you need to go through the CDU menu to operate the doors? The specific (custom) events (or lvars) may be the easier way to assign for this.

It uses the wnd library, so you can use the arrow keys to move the window and the ctrl + arrow keys to resize. Give focus to the window first. The position will be remembered, i.e. stored in your FSUIPC .ini file. You can also directly edit the position and size coordinates in the .ini file if you like, but only when the window isn't being displayed.

Look at the FSUIPC Offset status document, or better, in the offset status spreadsheet provided for MSFS/FSUIPC7 (included in the zip download, but not installed in your documents folder*). If you search for 'Free for general use', you will find: 0x66C0 - 64 bytes 0xA000 - 512 bytes I am looking into making more space available for user offsets. * The offset status spreadsheet is a supplement to the offset status document, as I have not had time to update this yet. I am planning on updating this shortly. For now, best to use the spreadsheet which contains the latest info and is continually updated (v26 now) and consult the offset status documentation for the description only. No. You have to enable to use, and the other menu entries are only available once the info on available lvars/hvars has been received from the FSUIPC WASM module installed in the sim. This usually occurs several seconds (or longer, depending on configuration parameters in the WASM that can be tuned) once you have loaded an aircraft and are out of the menus and loaded and ready-to-go. John