John Dowson

I suspect that it this is happening then it is the lvar that is not changing value. but I will take a look. Is this in the Asobo or FBW A320. and if the latter which version (stable, development, experimental)? Btw, please also update to the latest beta, if not using this already: John

Yes. Use the messaging functionality provided - click my name/avatar and then use the message function. Please explain your use (in the PM/DM) and we can take it from there. Regards, John

First. make sure that you are using the "JoyLetters" facility in FSUIPC7 on your old PC - this should be active by default. Install the latest version of FSUIPC7 on your new PC. You can skip registration, and then copy across the following files from your old PC FSUIPC7 installation folder to the one on the new PC: FSUIPC7.ini, FSUIPC7.key, *.dll, *.lua, *.mcro. Also copy across the Profiles folder, if using profiles in separate files. It is quite possible that the GUIDs of your controllers are different on the new PC. To check and correct for this, run FSUIPC7 once and then exit. Then open the updated FSUIPC7.ini file in an editor and find the [JoyNames] section. If your GUIDs have changed, you will see some entries marked as "<< MISSING JOYSTICK >>". For these entries, you need to change the GUID entry for that matching entry (i.e. with the same letter as the missing device), which will be listed later with a new device letter (the names will match). So, change the GUID entry of the missing device entry to the new one, and remove the new device entry. Do this for each missing device. Then if you run FSUIPC7 again, everything should be ok. If you have any difficulties or issues, please post/attach your FSUIPC7.ini once it has been updated by FSUIPC7 on your new PC, together with your FSUIPC7.log file. John

It should be ok to run MakeRunways while MSFS is still open/running. However, please note (from the provided README.pdf): John

Is this the same error as reported here (Pegasus): If running MSFS as admin, make sue you have set the FSUIPC7.exe to be ran as admin (in Properties->Compatibility) as it may not run automatically as admin. otherwise./

Thanks for the update. Are you tunning Pegasus on a client PC then? Using WideClient or FSUIPC7 on the client PC?

When you list the lvars, they are also logged to the FSUIPC7.log file in id order, with the id given. The list in the main FSUIPC7 window is in alphabetical order, and the ids are not shown (as not normally needed for most users). Try listing the lvars with the logging console window open (Log -> Open Console...). Just FYI.

B vars are "input events" - see https://docs.flightsimulator.com/html/Additional_Information/Reverse_Polish_Notation.htm (section Variable Types). We can only provide access to the variable types permitted in the SDK - A type (simvars) and k type (events) via simconnect, and L type (lvars) and h type (hvars) via the gauges API using the WASM. You may be able to use other variable types via calculator code, but you cannot read/know their value - if they have one. As a b-type variable is an input event, I doubt it has a value - it is what you input.... Then again, I know nothing about b type variables - maybe ask about those on the Asobo forums.... As I said, they are input events, whatever that means, and there is no provision in the SDK to access or know about such variable types. I think the b var is for control. as it is an input event. Try listing the available lvars to see if the state is held in one of those. As I don't have this aircraft, and it isn't listed in the MF presets, I can't really help with this. Ask Asobo / MSFS - it has been very difficult for us 3rd party developers to try and provide what we can with the APIs that they provide.... John

The lvars-ready callback is performed once all lvars have been loaded (i.e. the names known), not when they have received an initialisation value. All lvars are initialised to 0.0, If you need the values initialised, you should set a timer in this callback (200ms or so should be ok)and perform your actions in the timer callback. I guess I could delay the callback until the first set of values have been received - I will look into this. I really can't see how this can happen...the code doesn't know anything about any particular lvar, they are all treated the same. Try setting Debug level logging in the WAPI - this should tell you when am lvar is flagged for callback when values are received. If you can generate a log showing your issue (it will be large so will need to be compressed/zipped) I will take a look. Only the lvars that you register to receive a callback when changed will be monitored. There is currently no way to deregister an lvar for a callback - this could be added if needed. But you can use whatever method works best for what you are trying to achieve. Cheers, John

You can't - but if you need to know this, then as it is on before you start to toggle it on/off, you can keep track of this yourself if needed. You just need to initialise a free FSUIPC offset to 1 (on) and then also toggle this offset value each time you toggle auto-save (i.e. overload the button you gave assigned to auto-save to also toggle this offset va;ue). There is also a flight-save counter that is incremented each time a flight is saved, at offset 0x3BD2. You could monitor that if you want to know when a flight is saved. John

Ok, thanks for the update. John

No - that control should be the one you need. Can you please activate logging for Buttons & Keys as well as Events (non-axis controls), and generate a short log file showing your issue - i.e. load an aircraft and press the assigned key to switch com1 active/standby, then click the button in the VC that does this, then exit the FS and show me/attach your FSUIPC ini and log files.

You should try listing the lvars when this occurs, to check if those lvars are available or not. Then reload and check again. Do those ;vars have high ids? The log file you posted is useless - it is from a running FSUIPC7 and ends after 41 seconds. By the way, you posted in the main support forum. There is a specific sub-forum for FSUI{C7 / MSFS issues - I will move this topic to that sub-forum. John

Yes! John

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