John Dowson

Maybe better and easier to assign to the custom controls #define EVT_CONTROL_STAND_FLAPS_LEVER_0 (THIRD_PARTY_EVENT_ID_MIN + 5071) #define EVT_CONTROL_STAND_FLAPS_LEVER_1 (THIRD_PARTY_EVENT_ID_MIN + 5072) #define EVT_CONTROL_STAND_FLAPS_LEVER_5 (THIRD_PARTY_EVENT_ID_MIN + 5073) #define EVT_CONTROL_STAND_FLAPS_LEVER_15 (THIRD_PARTY_EVENT_ID_MIN + 5074) #define EVT_CONTROL_STAND_FLAPS_LEVER_20 (THIRD_PARTY_EVENT_ID_MIN + 5075) #define EVT_CONTROL_STAND_FLAPS_LEVER_25 (THIRD_PARTY_EVENT_ID_MIN + 5076) #define EVT_CONTROL_STAND_FLAPS_LEVER_30 (THIRD_PARTY_EVENT_ID_MIN + 5077) using the right-hand side of the axis assignment panel. i.e. set the detent position (custom) control when the axis lever range is around the detent position for both up and down. The control will then be sent to set the detent position when your axis lever enters the range set.

I think this is because the PMDG aircraft do not use the standard P3D controls for flaps. What have you assigned to, and does this assignment actual work, i,e, can you see the flaps lever move with this assignment? PMDG provide their own custom controls for many actions, including flaps: See the following FAQ entry on how to use custom controls for PMDG aircraft: However, you can only assign custom controls to buttons and keys, not axes. If you want to use a custom control for an axis, you would have to write the axis value to an FSUIPC offset, and use a lua script to monitor/read that offset and send the appropriate custom control with the value read. John

Yes - you will automatically get a discount of 5euros on check-out if you have previously purchased another version of FSUIPC. The current trial license is valid until 1st October. This will be updated to 1st November when there is less than 7 days available on the current trial license. I generated a new trial license when there is < 7 days (approx) left on the current one. John

There are two ways to set a simvar (or A-type variable0 that is not already held in an FSUIPC offset: 1. Use calculator code, e.g ipc.execCalcCode("50 (>A:LIGHT POTENTIOMETER:84, Number)") 2. Add the simvar to a free/spare FSUIPC offset, and use the provided lua offset functions to read/write to the offset. How to add a simvar to a spare FSUIPC offset is described in the Advanced User guide. John

string.match will return a string, not a number, so you need to convert the results to a number (using tonumber). Also, the match will stop after the first non-digit character is found (after a digit), so "Mach 0,78" will return 0 (due to the comma). If you want to extract decimals, see https://stackoverflow.com/questions/38140434/lua-how-to-retrieve-a-decimal-number-from-string. Otherwise, maybe take a look here: https://stackoverflow.com/questions/46794989/extracting-number-from-string-using-lua But it would be better to just read the offsets holding the values you want to extract. For example, if its the mach speed, that will be in offset 0x11C6 (or 0x35A0 or maybe 0x07E8 for AP mach value).

Please see the example TripleUse.lua script, which will be in the Example Lua plugins.zip file in your FSUIPC7 documents folder. This shows how to use a button for single press, long press and double press. There is also a user contribution that expands on this, available here: John

License sent via PM. John

Just to let you know, I have raise this on the P3D developer support forums but have yet to receive a response - I will update again if/when I hear anything,,,

What is your issue? Have you read and followed the network configuration section in the WideFS User Guide? All the information you need is documented there, so please follow that. If you still have problems with connections, try disabling your firewalls (server, client and router) and see if it connects then. If so, then enable the firewalls one-by-one to see which is causing the issue, and then configure that firewall to allow the connection. Also try adding the ServerName (or ServerIPAddr) ini parameter to your WideClient.ini - again, see the documentation. Note that you can also use FSUIPC7 on a client PC instead of WideFS / WideClient. This does not provide the same functionality as WideFS/WideClient (it will not communicate with the FSUIPC7 version running in the FS PC) so this depends on what you want to achieve on the client PC. Instructions on how to set this up are in an appendix in the Advanced User guide. John

You need to use presets. First, please update your FSUIPC7 version to the latest version, 7.3.23, if you have not done so already. This version contains a new feature that makes finding presets a lot easier. In the assignments panel, check Select for Preset and then click the Find Preset... button. you should then see presets for both of these buttons, e.g, Note that you can also use the MobiFlight hub-hop site (https://hubhop.mobiflight.com/presets/) to search for presets. John

Neither of these are showing where? Did you check 'Send Preset to FS'? Your log file shows 11085 presets have been loaded, so you should see at least that that many entries in the drop-down when you select 'Send Preset to FS'. Can you first update to v 7.3.23, which was released a few days ago. In this version, there will be far fewer entries in the axis assignment drop-downs when 'Send Preset to FS' is selected as only those accepting a parameter will be displayed. How many presets do you see loaded (check your FSUIPC7.log file, near the top)? You should see 11090 +the number in your myevents.txt file.

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