John Dowson

Could you list the available lvars for the Fenix please: Add-ons->WASM->List Lvars and paste/attach here from the FSUIPC7.log or FSUIPC7 main window. Please wait for a minute or two after the aircraft is loaded before doing this. Also, could you activate logging in FSUIPC7 for events and turn the avionics on in the cockpit UI and see what, if anything, is logged (in FSUIPC7.log), and also post that here. Thanks, John

Why are you creating a new topic when there is already a topic about this which you have already posted in? Please use that topic. I am closing this one. You can re-post your question there. John

I do not understand why you are buying everything twice...you only ever need a single license - it is per user not per machine, so its gine to install on multiple PCs if needed. But thanks anyway! You can use your FSUIPC7 license if/when you move to MSFS2020... The WideFS7 license is needed if you want to activate WideServer in FSUIP4. However, as I said, you will need to use the WideClient from WideFS6 if running on a 32-bit OS. John

Re-reading the support forum post (which I have just moved from the User Contributions sub-forum to the FSUIPC7 / MSFS support forum btw), I am slightly confused about your issue... You say your issue is with an assignment to 'power up my PFC Radio Shack'. But that is your hardware - you power that up by pressing the power button on the hardware itself, no? Assignments are for linking your hardware controls to a cockpit UI control. You ask what to assign to, so I presume the controls on your hardware are being recognised by FSUIPC, no? But what is the cockpit UI control that you are trying to assign to? You say you this is working for all planes apart from the Fenix A320, so what, for example, is the assignment you have for this in the Asobo or FBW A320? That may help me (and others) to understand your issue.... John

From the Advanced User guide, P37: Your macro file is therefore (obviously, I hope...) not correct for various reasons, and should be and if you want to add the right pump. it would be: Alternatively, it is probably easier to use presets to control lvars these days as they are more powerful. To create presets for these, create a file (in your FSUIPC7 installation folder) called myevents.txt, and add the following content: You can then assign to the controls Preset:Milviz C310 Left Fuel Pump and Preset:Milviz C310 Right Fuel Pump giving an appropriate parameter in the assignment. Again, i advise you to consult the documentation provided. Maybe, but the format of the files you are posting is obviously incorrect if you check the format against that specified in the documentation. I am suggesting that if you find that things are not working, check the format against the documentation before posting. This would save us both some time! John

A license is only needed for the registered facilities - assignments, access to the lua interface, etc. No license is needed for the unregistered facilities (access to offsets for third-party programs and developers using the FSUIPC SDK, logging facilities). Of course, people can keep using the trial license and never purchase FSUIPC, but this is not the intention and I obviously do not approve of doing this. I always leave a few days after the expiry of a trial license before generating a new one, and I will not generate a new license on the request of a user who has obviously already been using the previous trial license. Thanks, but I have only been developing/supporting FSUIPC for around 4 years now - previously this was done by Pete, my father, who deserves most of the credit! Regards, John

I doubt they are following this...just me I'm afraid...and, as you say, FSUIPC is just the middleware in this set-up, and I don't think there is anything I could do to help with this... John

You don't need to download the MobiFlight connector - you can export the preset file (events.txt) from the MobiFlight HubHob site (https://hubhop.mobiflight.com/presets/) - this is mentioned several times in the documentation. You need to create an account, and that site is the community reference for presets, so you should familiarize yourself with that (and create an account!). Yes. This is documented in the Advanced User guide, under Using Calculator Code Presets: Ok, but maybe you could explain what your issue was in case others have the same problem... John

Those entries are incorrect - you also need to specify the size if the offset, This tells me that you have not read (or have not understood) the documentation. I therefore suggest that you read the documentation on adding lvars to offsets which is in the WASM section of the Advanced User guide. This should also tell you what you need to assign your button to. Please always check the documentation first before requesting support. John

You can always download and use the latest events.txt file from MobiFlight. That's ok in this instance, but usually better to use the myevents.txt file to add your own presets, as the events.txt file will get overwritten on the next FSUIPC7 update. Do you have the WASM module enabled (Add-ons->WASM->Enable) - if not, do that - you only need to do this once (you will need to disconnect/reconnect to MSFS when you do this). To test presets, you can use the Add-ons->WASM->Execute Calculator Code... menu option. Try that - if it doesn't work, then the preset is invalid and I can't reallu help you with that (try the MobiFlight Discord channel, or support for the aircraft). Ifthat is working, then there is something wrong with your assignments. Try activating logging for Buttons & keys and Events, open the logging console and see what is happening when you press the assigned button. You can attach your FSUIPC7.log and FUIPC7.ini files here if you require further help. John

Note there is also a user contribution to get keyboard input via lua for FSUIPC7 / MSFS - see No keys should go through to the sim if the sim does not have the focus - you should give (or acquire) the focus to your input window to prevent this. And I can't understand how some keys assigned in FSUIPC can go through, others not...could you please elaborate and perhaps provide an example. Anyway, I presume you are using the event.key lua function to get keyboard input, no? If so, then if you look at the documentation for this function you will see the following: I am not sure how relevant this ini parameter is now (as FSUIPC7 receives keyboard input from the FS when the FS has the focus), but you could try that. Otherwise, please show me your lua script and provide more details and I will take a look. John

No, you don't need WideFS6 and that is also no longer available for purchase (a free license is available, as with FSUIPC3). However, if you need a 32-bit WideClient, you can get that from the WideFS6 package/download. But I am now confused...I thought your connection problem was with FSUIPC4/FSX, not FSUIPC7/MSFS2020... Please check the files yourself before sending them to me. For example, have you configured the server name or IP address for WideClient? If you had this working for FSUIPC3/FS2004 and WideFS6, the configuration / set-up should be the same/similar for FSUIPC4 and FSUIPC7... You should also check the WideFS documentation first for connection issues and solutions, although this is only available in English I'm afraid. Note that FSUIPC7 can also be used on a client computer - details on this are in the Advanced User guide (appendix 4), which can be used instead of WideClient (on a 64-but machine). John Regards, John

You posted in the .Net client dll sub-forum - I have moved your post to the main support forum. The WideFS version for FS2004/FSUIPC3 was WideFS6. You need WideFS7 for FSUIPC4, which requires its own license. However, if it shows up as registered, I guess you are using WideFS7, no? Note that if running WideClient on a 32-bit computer, you will still need to use the 32-bit WideClient from WideFS6 on your client machine. What do you mean by 'cannot connect to Flight Simulator'? WideClient connects to WideServer (built into FSUIPC4), not to the Flight Simulator. It is FSUIPC4 that connects to the Flight Simulator. If WideClient cannot connect to WideServer/FSUIPC4, then you may need to configure the server name or address in your WideClient.ini file. Check the documentation for details. If you have any further issues, please show me your WideServer.log, FSUIPC4.log and FSUIPC4.ini files from your server/FS computer, and your WideClient.log and WideClient.ini files from your client computer. John

top-left of the calibration page... Ah, ok...

But you don't need hvar files to use presets - just the events.txt file installed (by default) in your FSUIPC7 installation folder. You only need (FSUIPC) hvar files for direct access to hvars (via lua or macros) - they don't need to be made known to FSUIPC is activating them via calculator code, such as used by presets. That is fine but it is more usual to send the control on a press ('P') rather than a release ('U'). Having small increments can also be a pain when you have to change the amount by a large number, which is why its usually to also assign buttons to the fast controls. If using a 2-button rotary (ie. one button in each direction), then there is a lua script you can use to convert this to 2 virtual buttons in each direction, where one is used for slow (1) increments), and the fast button for larger (10 or more) increments. John

First, you have PropPitch1 assigned to two axes: This invariably causes issues due to different/conflicting values being sent by each axis. Also, this is incorrect: Hence the error in your log file: This (most probably) should be: Please see the Advanced User guide for details on the format and size designators you should be using. And always check your log file if/when adding lvars to offsets to check that it is being added as expected. Apart from that, the log shows the PropPitch axis behaving as expected. It would be useful to see the second log, but I think your issue could be that you are calibrating with a reverse zone - if there is no reverse zone, you need to check the No reverse Zone checkbox in the Prop Pitch calibration panel - try that. John

👍 Thanks for reporting back.

The [Auto] section is used to start/run the lua. This is used for luas that are not ran activated on a button press, but use one of the lua event.* functions to wait for an event. The Rotaries.lua uses the event.timer function to poll for the button states. Of course, you don't have to auto-start the lua if you don't want to, but it needs to be started somehow so that it can poll for the state of your rotary buttons. You usually do this from the [Auto] profile-specific [Auto.xxx] section, but you can always start it on a button or key press, but it makes more sense to have this script auto-loaded. John

👍

You should not manually change that section - it is automatically managed by FSUIPC by scanning for lua files in your installation folder. What works? Then add/create one! What is your lua file called - isn't it Rotaries.lua? If so, then it is not in your FSUIPC7 installation folder. If you called this file currheading.lua (which you shouldn't, as it controls/changes the rotary, not what you have assigned the rotary to do) then it should automatically appear under your [LuaFiles] section, and you should not need to add this manually... John

You are using v7.3.4 - please update to the latest version, v7.3.6, and try again. There was a fix in that version that could cause a crash (timing issue related to WASM use). If you still get a crash with this version, please also attach your FSUIPC7.log (zip it if too big to attach as-is) as well as the crash event information. Thanks, John

Well, it won't as it is an ini parameter for the FSUIPC WASM module, not for FSUIPC itself, i.e. it goes in the FSUIPC_WASM.ini file, not the FSUIPC7.ini file. Please read the documentation as suggested, the WASM section in the Advanced User guide. The ini parameters and file locations are explained there. John

Do you have the FSUIPC WASM module enabled (Add-ons->WASM->Enable)? If not, do that (you only need to do this once) and then disconnect and reconnect to MSFS. Otherwise, please show me your FSUIPC7.ini and FSUIPC7.log files, the latter generated with logging for Buttons & Keys as well as Events activated. That preset just activates a hvar - you can also check this is working by using the Add-ons->WASM->Execute Calculator Code... menu item, entering the text: (>H:H145_SDK_ECP_MAIN_1_FLIGHT) If that doesn't work, then the preset is not correct....You can use that menu option to check the preset code is working and should be the first test to check a preset. If its working using that, then it is a problem with your assignments. John

You have to edit the Rotaries.lua to specify the correct device/joystick id and also the button numbers that your rotary uses. You also have to have the lua auto-started by adding it to the [Auto] section of your FSUIPC7.ini file (see the section Automatic running of Macros or Lua plugins in the Advanced User guide). Once the lua is configured and running, you can then assign to the virtual buttons you see in the Buttons assignment panel when you turn your rotary. If you see the original button numbers instead of the virtual ones, you can use the IgnoreThese ini parameter (in your [Buttons] or profile-specific [Buttons.xxx] section) - again, see the Advanced User guide for details). John

Can you show me your FSUIPC7.ini and FSUIPC7.log files please. For the log file, activate Axes control logging, load your aircraft and move your assigned propeller axis through its full range, then exit FSUIPC before attaching (zip it if its too big to attach). A 2nd log file would also be useful, also with Axes logging activated, but this time use the cockpit UI controls to move the propeller levers through their full range. John