John Dowson

The license available from SimMarket is for personal use. Commercial use requires a different license and I should be contacted to discuss requirements. For educational (not including paid pilot training!) and charity use, you can use a single-user license (from SimMarket) and I will allow this to be used in an educational environment. You will not get an answer from Pete as he retired a few years ago. It is me that develops and supports FSUIPC these days. Regards, John

No you don't. As I said, FSUIPC5 is for P3Dv4. You need FSUIPC4 if using FSX. That is because FSUIPC5 is installed for P3Dv4. As you need FSUIPC4 (for FSX), you need to look at the installation guide for FSUIPC4, not FSUIPC5. Forget about FSUIPC5 and download and install FSUIPC4.

I have moved your question to the main support forum as you posted in the sub-forum for the .Net client DLL. FSUIPC5 is not compatible with FSX - you need FSUIPC4. FSUIPC5 is for P3Dv4. I do not understand - you said you are running FSX and now ask about P3Dv4. Which sim are you using, or planning on using? I cannot give advice on what type of P3D license you require - that is for you to decide.

Then it should be the same key binding in P3Dv5. If you are upgrading from P3Dv4 to P3Dv5, you can use the same ini file, although it will need renaming if you also update from FSUIPC5 to FSUIPC6. I can't read what that button says - is it the button to switch standby to active? If so, then use the Com Stby Radio Swap control.

How are you expecting to change the COM1 frequency with a single button press? Usually you would assign keys to inc and dec the existing frequency, using either the standard slow inc/dec controls COM_RADIO_FRACT_INC, COM_RADIO_FRACT_INC_CARRY or COM_RADIO_WHOLE_INC (got inc, with similar controls available for decrement). See the auto-generated text document Controls List for ... which will be in your FSUIPC documents folder. If you want to set (i.e. hardcode) a specific frequency yo a ley press (which is a strange thing to want to do!), you can use the COM_RADIO_SET control

Or maybe create a new profile for each of those, based upon your "Jet Two-engine" profile, as needed. You can reverse your spoilers in the spoiler calibration section, on page 6 of the calibration tab. For the DUMP area, you can use the right-hand side of the axes assignment tab, to send the appropriate control(s) when entering and/or leaving the DUMP area.

You have to assign in FSUIPC, not P3D, if using the FSUIPC PFC drivers. Did you click Rescan before moving another axes? Once one axes detected, you have to click the Rescan button to detect another. If the same axes keeps showing, you can also click the Ignore Axes button to ignore that for the rest of the session (i.e. while the Axes assignment dialog box is still open).

Please see the provided document FSUIPC Lua Plugins.pdf. You cannot assign to a specific lua function, only to one of the provided lua controls (from that document): The controls added for each Lua program are: Lua <name> to run the named program LuaDebug <name> to run the program in debug mode (more below) Ths is actually superseded by the Trace Lua option in FSUIPC4’s Logging Tab. LuaKill <name> to forcibly terminate the named program, if it is running LuaSet <name> to set a flag (0-255 according to parameter) specifically for the named program to test LuaClear <name> to clear a flag (0-255 according to parameter) specifically for the named program to test LuaToggle <name> to toggle a flag (0-255 according to parameter) specifically for the named program to test LuaValue <name> to set the ipcPARAM variable to the given parameter, or the axis value when so assig You can extract what you need - but you really need to understand what you are doing of you do this. However, there are easier methods. There are custom controls available which allow you to either set the EFIS NAV1 mode directly or to inc/dec the current mode: You can either use the Rotor Brake control with an appropriate parameter (mouse action) to use this: see Or a custom control number: see If you want a single key to cycle through the modes, then you will also have to handle the move from vor to adf To do this, you need to add the lvar L:switch_358_73X to an fsuipc offset, overload your key assignment to also use the preset PPMDG_B737_EFIS_L_VOR_ADF_ADF1 and then add an offset condition to send the rotor brake/custom control with a left mouse-click parameter when the switch is in the off or adf position, and to send the preset PMDG B737 EFIS L VOR/ADF OFF when in the vor position. where the current position is indicated by the value of that lvar held in an FSUIPC offset. In fact, maybe better to just use the presets and overload the key with 3 assignments, one for each value of the offset/switch position. So, first add the lvar to an offset, by adding the following to your FSUIPC7.ini file: where xxx is your profile name (or just use [LvarOffsets] if not using profiles). This adds the switch position to offset 0XA000 - you can change this if already using that (free for user assignment) offset, Then, your key assignments will look something like the following - here I have assigned to the M key: So, when the offset is 0, the switch is in the VOR1 position and the keypress will send the preset PMDG_B737_EFIS_L_VOR_ADF_ADF1 which will move the switch to the ADF1 position. When the offset is 100, the switch is in the ADF1 position and the keypress will send the preset PMDG_B737_EFIS_L_VOR_ADF_OFF which will move the switch to the OFF position. And when the offset is 50, the switch is in the OFF position and the keypress will send the preset PMDG_B737_EFIS_L_VOR_ADF_VOR1 which will move the switch to the VOR1 position, John

Lvars don't 'stop' - they are either available or not. Your FSUIPC7.log file would tell you if they were not found when the [LvarOffsets] section was processed. This can occur with some lvars that are created after the WASM has scanned for lvars (and will be the ones with the higher ids), which occurs 5 seconds (by default)) after your aircraft is loaded and the READY TO FLY button is present. You can increase this delay by using the LvarScanDelay WASM ini parameter (see Advanced User guide for details). In the next release (7.3.17), the WASM will automatically rescan and push any new lvars out to clients, so this should no longer be an issue. This release is currently available as a beta release if you would like to try it: John

👍

You only need to install the WideClient component of WideFS on a client computer if toy want to run FSUIPC client programs on that computer. How to install what? I cannot give advice on setting-up/configuring specific controllers in FSUIPC- that is why I provide documentation - start with the User guide. If you have any difficulties I can answer specific questions, but please check the documentation first, and also check/search this forum - most questions have already been asked and answered. If you get stuck you can post a question - but not in this topic. Please either find a relevant/related topic or create a new one, and give it a relevant title. If it is assignment related, also specify the aircraft for which you are trying to configure (as well as what you have already tried). John

You can add it to a free/spare FSUIPC offset using a lua script and then use that in the offset condition. To add it to an FSUIC offset, use the following lua script (this adds to offset 0xA000 - you can change if already using that offset): function addLvarToOffset(varname, value, userParameter) ipc.writeUB(0xA000, value) end event.Lvar("L:ASD_C172SP_SWITCH_AVIONICS_L", 200,"addLvarToOffset", 0) Save that to a *.lua file (e.g. addLvarToOffset.lua) in your FSUIPC installation folder and then have it auto-started in your C172 profile - see section Automatic running of Macros or Lua plugins on page 41 of the Advanced User guide for details on how to do this.

All there is is the full aircraft title from the aircraft.cfg file, available in offset 0x3D00. It is up to you how you interpret that - for example, FSUIPC uses a substring match for that in the aircraft names in a profile to match to a profile, which is why we recommend changing the aircraft name in the profile section to be a substring match to catch the same aircraft with different liveries. I also allow matching based on the folder name of the folder where the aircraft.cfg file is located (see ini parameter UseAirLocForProfiles) which should catch the same aircraft regardless of livery, but this is not held in an FSUIPC offset. You can't. as that is created and being updated by the Fenix (or GSX), so you cannot stop it being updated. What you can do is just copy the value to your own lvar, and then it is up to you to reset it. Just execute the calculator code "L:lvarToBeSaved (>L:myLvar)" to save the value of L:lvarToBeSaved to L:myLvar. Alternatively, you can always save it to an FSUIPC offset (using Lua). Note that in the current official version of FSUIPC7 you will have to issue a WASM reload to get visibility of the lvar you create. In the next release, any new lvars found by the WASM will be automatically pushed out to the clients (including FSUIPC). This version is currently available as a beta release (7.3.17a) in the Announcements sub-forum. Btw, Pete retired a few years ago now. John

This will be due to FSUIPC's calibration. This was disabled when assigned outside of FSUIPC in version 7.3.9 (due to an SDK change), but then re-enabled in version 7.3.13. You should update to 7.3.16 and then remove the throttle calibration in FSUIPC. To do this, go into the axes assignment panel, go the the Joystick Calibration tab, check the Profile Specific checkbox (if using a profile for the PMDG 737, which you really should), then click the Reset button on either the Throttle calibration on page 1 and/or the separate throttle calibrations on page 3.

Which 737? If its the PMDG 737, you can either use the provided custom control: or the MF preset PMDG_B737_MCP_SPD_INTV_BUTTON To use PMDG custom controls, please see For a list of available MF presets, please see https://hubhop.mobiflight.com/presets/. All MF presets are available for assignment in FSUIPC7 by checking the Select for preset checkbox. Please see the Advanced User guide for further details on presets. John

Ah...apologies - in my previous response I was thinking of MSFS / FSUIPC7 (event though you clearly state you were using P3Dv5. Sorry about that. Please ignore what I said about presets and the MF HubHop site - these will also be for MSFS / FSUIPC7 only. For FSUIPC6, it is on page 36, section Additional Simulator Variables (simvars) to FSUIPC Offsets (v6.1.8 and later only). However, I doubt very much that those simvars exist in P3Dv5. You could try listing the available lvars to see if there is one that holds avionics bus state. There is a control provided for this - List Local Panel Vars - assign that to a button or keypress and use it to list the available lvars in the FSUIPC6.log file (or, better, check the Send to console window checkbox to see them logged). If there is one available, then you can add this to a free FSUIPC offset, although you would need a lua script for that (I can help you with this if needed). John

That seems to be in offset 0x3101 - GENERAL ENG MASTER ALTERNATOR:1 Avionics Bus 2 looks to be in offsets 0x2E80 and 0x3103 (AVIONICS MASTER SWITCH). There doesn't seem to be an offset for bus 1. However, looking at the MF presets for the C172 (https://hubhop.mobiflight.com/presets/): C_172_AVIONICS_BUS_1_ON: (A:CIRCUIT SWITCH ON:24, Bool) ! if{ 24 (>K:ELECTRICAL_CIRCUIT_TOGGLE) } (A:CIRCUIT SWITCH ON:24, Bool) 1 (>A:BUS LOOKUP INDEX, Number) (A:BUS CONNECTION ON:4, Bool) != if{ 4 1 (>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE) } C_172_AVIONICS_BUS_2_ON: (A:CIRCUIT SWITCH ON:25, Bool) ! if{ 25 (>K:ELECTRICAL_CIRCUIT_TOGGLE) } (A:CIRCUIT SWITCH ON:25, Bool) 2 (>A:BUS LOOKUP INDEX, Number) (A:BUS CONNECTION ON:5, Bool) != if{ 5 2 (>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE) } This would indicate that the state of the avionics bus switches is held in the simvars A:CIRCUIT SWITCH ON:24 for bus 1 A:CIRCUIT SWITCH ON:25 for bus 2 These are currently not held in any FSUIPC offsets. You can add them yourself using the facilities to add any simvar to a free FSUIPC offset, described on page 34 of the Advanced User guide. Generally, to find an offset that holds the state of a switch, you should first check the Offset status document to see if anything looks relevant, and then try logging that offset using FSUIPC's offset logging facilities. Then see if the value changes when you move the switch - you can keep the logging console open using the Log->Open Console menu option and you will see the logged offset value change, if it is being used. If there are no offsets that look applicable, you should then look at the preset code that controls the switch (on the MF HubHob site referenced above). This should give you a clue as to where the information is held, either in a simvar (A: type variable) or an Lvar (L: type variable). If there is one, then both a-type and l-type variables cam be added to FSUIPC offsets amd them used. John

Ah, ok....thanks for letting me know. Very strange... John

Ok...then it already sets the FS to the foreground. Strange it isn't wotking as the key presses are being sent, and as the key presses work directly in MSFS. Did you notice when this stopped working (e.g. after what update)? Sorry but I haven't had time to look at this today - will hopefully get a chance tomorrow... Cheers, John

Thanks Paul - I have updated the 7.3.17a-beta downloadable zip with this websocket server update. John

Now available: John

Yes, should be - I will take a look later today - need to pop out for a few hours. I will let you know once I have taken a look. Also, please remember that when you attach log files, please attach a full log file and not a continuation log (i.e. don't use the New log feature). Does it work if you manually give MSFS the focus? Also. please check that you are using the latest official release 7.3.16, or the latest beta 7.3.17a (available from the Announcements sub-forum). Thanks, John

Does MSFS have the focus? MSFS needs to have the focus to receive key events. Alternatively, you can set the following parameter in the [General] section of your FSUIPC7.ini file: SetForegroundOnKeySend=Yes Otherwise you can use ipc.keypressplus with an option parameter of 4 to change the focus to MSFS before the keystroke is sent, or 12 to do this and also return the focus to the original active window after the keypress has been sent. John

They are presets - custom controls are yet another mechanism, and only available if provided by an aircraft (e.g. PMDG). You should get familiar with presets and the MF HubHop site which provides a good search interface, and they are (or should be!) very easy to use in FSUIPC7.

Now available: John