John Dowson

There is no problem having the script ran on a button press. However, this means that a new thread is created & started and the script is compiled (before being ran) an each button press, which introduces a small overhead/delay on each button press. Having the script auto-ran and activating on events is generally more efficient as the the thread generation and script compilation is only done once (and at start-up) rather than on each button press. John

Note also that if you do want to call a preset (available in FSUIPC) from an FSUIPC client app, you can do this by writing the preset name (preceded by 'P:') to offset 0x7C50. John

No problem. Note it would be more efficient if you changed the script to something like: have the script auto-started, and assign your rotary buttons to the LueValue <script> control to set the parameter. Doing this, the lua script is only compiled once and you should get better performance. John

That sounds reasonable... Please activate debugging for Debug/Trace Lua plugins (NOT Log Lua plugins separately) as well as Button and Key operations and generate a log file showing your issue. Please also list the lvars before you move your 8 position rotary so that I can check the lvar exists (you can assign a spare button or key press to do this, either using the List local panel variables control, or the provided Log Lvars.lua), as well as after you have turned your rotary to check if the value has changed or not. Then show me / attach your FSUIPC4.log and FSUIPC4.ini files together with your lua script. John

No! Quite the opposite... From the Advanced User guide: Your filename contains 18 characters, so please rename to something shorter and more sensible. And don't forget that the filename and macro name will appear for assignment (i.e. as filename: macroName), so name both the file and the macros in it accordingly.

Yes. Some users have found that their macros weren't recognised as a .txt extension had been added after the .mcro, so worth checking.

@salsero_at Could you please attach your MakeRwys_Scenery.cfg file - it may need compressing/zipping before attaching. Can you also check the Windows Event viewer to see if there are any events relating to MakeRunwys, especially crash/error events, and also post the details of those. Thanks, John

Check the [MacroFiles] section of your FSUIPC6.ini file - do you see your macro file there? If not, then the macro file is either not in the correct location or it has the wrong extension type. If it is there, then it should be in the menu... You can also check that you have installed in the correct location by using the 'Open Folder' button in the Logging tab - do you see your macro file (and with the correct extension)?

Do you have a steam and and an MS Store version installed on the same PC, or are they on different machines? If they are on different machines, please show me/attach your InstallFSUIPC7.log file for the MS Store version. Also please see the following FAQ entry: If they are installed on the same PC (which I didn't know was possible), then the Installer will first detect the steam installation and install for that. To also use with the MS Store version, you will have to manually update the EXE.xml file for the MS Store version to start FSUIPC7, and if the two versions have different Community folders, then you will also need to copy across the WASM from the Steam Community folder to the MS Store one. Also, please give your posts a relevant and appropriate tile - 'FSUIPC7' applies to every post in this forum and is therefore useless...I will update it. John

👍

License sent. Those values will be held in FSUIPC offsets. Note that you don't need a license if you are writing your own program using the FSUIPC SDK (or WAPI API).

👍

Ah, sorry...you are using the PMDG 737. You can use the custom controls (parameter probably not necessary). The following controls are available: To use PMDG custom controls, please see the following FAQ entry: John

Sent. John

In the FSUIPC Offset status document. Use the FSUIPC offset logging facilities. First, enable logging for offset 0BDC as U32. You do this on the right-hand side of FSUIPC's Logging tab. Make sure you check FS Title Bar, and the offset will be logged in the P3D title bar. Then, move the flaps lever to the position that you want for an assignment, and take note of the value displayed in the title bar - this is the parameter that you need to use for the assignment. Then move to the next flap position and repeat. John

Sorry, I understood that it is not working when you run it as non-admin but is working correctly when you run it as admin. Since Pete has retired, MakeRwys is no longer supported - from fsuipc.com: However, Pete does still pick-up and respond to issues with MakeRwys. Unfortunately he is currently on holiday, back at the end of the month. I can ask him to take a look when he returns. John

Just run it as administrator - from the MakeRwys readme document: John

You can use the Flaps Set control. To calculate the parameter, see the description for offset 0x0BDC: Alternatively you can read/log offset 0x3BFA which will give you the flaps detent increment (i.e. the value between each flaps detent/position) and then use this to calculate the parameter needed for each position. John

What axis? You are defining a preset, not an axis or an lvar. You can see presets in the axis assignment panel once you have selected 'Send Preset to FS'. You should then see the presets you have defined in the axis assignment drop-down. When you list the lvars, you can see the lvars that the presets you have defined are using: INPUT_AILERON & INPUT_RUDDER_S. Note I have just released a new version which, amongst other things, reduces the presets in the axis assignment dialog drop-down menu to contain only those presets which accept a parameter, which drastically reduces the number of presets available and makes them far easier to find and assign. So please update at your earliest opportunity. John

Which version of FSUIPC and what FS are you using? If its FSUIPC7 / MSFS, please use the specific sub-forum for this product. No A-type variables (also known as simvars) can be read via lua. The only A-type variables can be read are those that are held in FSUIPC offsets. Of course, as these facilities are for L-type variables, or lvars, only. You cannot use them for any other variable type. So, A-type variables (simvars) can only be accessed (read/write) via FSUIPC offsets. Facilities are provided to add any simvar to a free/spare FSUIPC offset (see the Advanced User guide) using a file called myOffsets.txt. So you can add them to a spare/free FSUIPC offset, and then use the appropriate lua offset function to read the value.

Yes. just delete it. John

License sent. You can assign to the presets Longitude Eng R Fuel Run Stop Button Press and Longitude Eng L Fuel Run Stop Button Press. There are also presets available for the engine left/right starter - see https://hubhop.mobiflight.com/presets/. Note that tomorrow I will be releasing a new version that contains a UI update that makes finding presets a lot easier, so I suggest you update to this version once released. John

This has now been implemented in the attached version. 7.3.23. This completes the implementation of this item for the time being. The attached version will also be the next release, and also contains a version check at start-up and will notify (display a message) if a newer version of FSUIPC7 is available. John EDIT: the attached file/version has been removed as this version has now been released

What do you mean by this? Lvars are independent from the PMDG offsets. Even if you uninstalled the FSUIPC WASM module (to disable access to lvars) the PMDG offsets would still be available and populated (once activated)..

Please try the attached version: FSUIPC7.exe This should automatically select and show any current preset that is assigned, and also select the parent of the previous selection made if no current selection/assignment available. Note however that it does not remember the previous state if no selection is/was made. John