John Dowson

As well as what Pete has said, depending upon how your button 1 functions (i.e. if its an always on button or not), then your button 1 may not be read as pressed when pressing button 2 (as you are doing this before you pressing button 2). If this is the case, you can use the button flag functionality to toggle a flag when you press button 1, then check the flag status when pressing button 2. This is also explained in the Advanced user Guide, P20.

@yvesbPlease try the attached version, v7.2.2a. This has an additional Reload WASM (FSUIPC7) control, as well as an additional lua function ipc.reloadWASM() FSUIPC7.exe I have also changed the default value of LvarScanDelay from 2500 to 5000, and have increased the max allowed for this parameter from 10000 to 60000. However, as these are WASM module updates, they won't be released until I release the updated WASM module, which will be done when I make 7.2.2 the official/latest release. John

Assign your axis to a free FSUIPC offset (e.g.A000), and use the lua event.offset function to call your handling function when the offset/axis value changes. Your handling function will receive the axis value - you can adjust that value as needed (i.e. calibrate) and then send on to the FS using ipc.control, using the control number for THROTTLE1_AXIS_SET_EX1 (which is 67103 - see the document Controls List for MSFS Build 999.txt) together with your calibrated value as the parameter. You should also auto-start the lua, using the [Auto.xxxx] (where xxxx is your profile name) section of your FSUIPC7.ini file.

You can also determine your installation folder by using the 'Open Installation Folder' button, in the FSUIPC6 logging tab. And please see the FSUIPC7 Installation and Registration.pdf for details on where things are installed - nobody seems to read this or pay attention to where they are installing....

The problem is that there is no event that can be caught that tells you when a plane is fully loaded (or ready-to-fly) which can then be used to start the lvar scan. There is an ini parameter that you can set in the WASM ini file (FSUIP7_WASM.ini, in the WASM folder under your MSFS Community folder) that can delay the scanning of lvars. The parameter is called LvarScanDelay, and is documented in the Advanced User Guide. The parameter is in milliseconds, with the default being 2500 (2.5 seconds). The (current) maximum allowed value is 10000 (10seconds), so you could try adding that (you will need to restart MSFS). I thought I had added am fsuipc control and/or lua library function to initiate a WASM reload call, but it looks like I missed this. I will add a control + lua function for this (no need for a specific offset). John

No, sorry.... It may be useful to you if/when you eventually upgrade from FSX to to MSFS...

Sorry, I was mistaken - you don't need to add the lvar to an offset to use the lua script. Just download the latest version (attached), and place it in your FSUIPC7 installation folder. Then add an entry to your FSUIPC7.ini [Auto] section, or, preferably, your [Auto.xxxx] section (where xxxx is the profile name for your A320. If you don't know how to do that, check the Advanced User Guide, section Automatic running of Macros and Lua plugins (P36). A320ParkBrake.lua

The solution has already been posted. Download the lua and use that. Don't forget to add the lvar to the offset you are using. Are you sure? I released v7.2.1 an hour or so ago...

First, you posted in the forum for Paul Henty's .net/c# client. If you are using VB.net, you should use the main support forum. I will move your post. Also, it is not clear to me what you want to achieve. Do you want to set-up the initial flight conditions via FSUIPC? You can do this by setting the required information to the relevant offsets. You will need to look at the FSUIPC Offset status document to work out which offsets you need to set to achieve what you require. There may also be other software available that does this sort of thing that you could take a look at. There is FSFlyingSchool (https://www.fsflyingschool.com/) and FS Flight Control (https://www.fs-flightcontrol.com/en/) that does this type of thing (and more). It will be quite a large task to write something similar from scratch.

I'm not sure I fully understand your issue....If your yoke moves through the full 90 degrees left and right, and so does the virtual yoke in the C172, I would have thought the visuals would match if you set a linear response curve... Not knowing this yoke or software, nor do I I'm afraid. If your yoke is recognised by windows as a hid joystick type device, you could try assigning and calibrating in FSUIPC7 without the software. If you need the software for the device to be recognised, then you will just have to try it to see how it works with FSUIPC7. I suggest you just try an assign/calibrate your yoke in FSUIPC7 to see if it works for you. You can find a trial license for you to try the assignment facilities here: John

When you say MSFS, that is distinct from FSX. i.e. MSFS is the MSFS released in 2020. FSUIPC7 only works with MSFS, it is not compatible with FSX. You cannot run both FSX and FSUIPC7 at the same time, as they share a windows class name.

Solved?

The lvars-to-offset facility is (currently) for registered versions only. 7.2 has been released - you should use that version, not the beta. I will also be releasing a minor update later this evening or tomorrow morning, 7.2.1. If using the FSUIPC SDK, you should use the WAPI (the WASM API) for lvar/hvar access. Not sure how you would do that in VB.net though. There is a static lib as well as a dynamic dll available, maybe you can use that, but I would not know how to do that via VB, sorry. However, if you are using a registered version, be aware that lvars are only available once an a/c has been loaded, and not when in the MSFS main menu.

Sorry, I think I misread what you are trying to do. So the hvar macro is working, and you now want to assign a button or switch to Autopilot On/Off? If so, you don't need a macro for that, its a straight-forward button assignment. There are also two distinct controls, Autopilot On (65792( and Autopilot off (65791). Neither take a parameter. If you have a single button that you would like to assign to both and add an offset condition, then assign to the first control and save (close the UI panel), comment out that assignment in your FSUIPC7.ini (place a semicolon after the index number in the assignment line created, e.g. '5;=....', where 5 is an example index number), open the button assignment panel again and click on Reload all buttons, then assign the same button to the second control and click Ok. Then open up your FSUIPC7.ini again, remove the semicolon previously added, then add your offset condition to the tje assignment lines. Once done and saved, open up the Button & Switches assignment panel again, and Reload all buttons.again to reload your changes.

Sorry, but what is that? It is certainly not a correctly formatted macro file. You seem to be mixing up macros and assignments. Offset conditions apply to assignments, in your FSUIPC7.ini file, not macros. I have already showed you what your macro file should contain - why don't you just use that? You then assign to your macros, which will add the assignment line to your FSUIPC7.ini file. It is there that you need to uncomment, then make your second assignment. And there that you need to add your offset conditions, not in the macro file. And why are you trying (incorrectly) to auto-run a macro file? Remove those.

There is no difference - macros functionality in FSUIPC6 and 7 is the same, except that FSUIPC7 also allows hvars in a macro, but only with the Set command. It is just a complete log file, not a continuation log file, which you will get if you select the Log->New Log option - just don't use that! No - certainly not! That will generate a huge log file and it will be difficult to find the relevant information. Only activate logging for the logging requested - if you have issues with button assignments, log Buttons & keys and Events, nothing else. Yes of course, apart from the known limitations... So, if you have a problem with a button or switch assignment not working, activate logging for Buttons & keys and Events, load your aircraft, activate the button or buttons that you are having issues with, close down MSFS/FSUIPC7, and then show me your FSUIPC7.log and FSUIPC7.ini files.

Offset values are either received from the FS via simconnect or calculated from such values by FSUIPC.

That control will only list lvars. There is a better method in FSUIPC7 - just use the Add-ons->WASM->List Lvars and List Hvars menu options. There are also other options to allow you to test your lvars/hvars (i.e set lvars and activate hvars) before using/assigning. Hvars have no state - you can only activate them (using the Set command), not toggle. The usual way of having multiple controls assigned to a button to be used for different states of the a/c is to use offset conditions. Program your button for one of the controls (e.g. Autopilot Off), then comment out that line in your FSUIPC7.ini, and then program for the second control. Then you need to uncomment the first assignment, and add an offset condition check to each of those assignments, using the offset which holds the AP status (maybe 07BC Autopilot Master Switch, if that is what the Autopilot Off/On controls change). Adding Offset Conditions is explained in the Advanced User Guide, P22. Regards, John

I'm not sure I understand...you would read them from your lua script, where else? You seem to have answered your own question, i.e. a/c on ground with 0 speed! You could have a lua script that is auto-started (from [Auto] or [Auto.xxx] ini section). In the script, you can use event.timer to call a polling function (maybe every 500ms or so - doesn't need to run too fast). In your polling function, you can check the sim on ground flag (offset 0x0366) and the a/c ground speed (offset 0x02B4) and then, if on ground and speed is 0, read those offsets, do your calculation, and display the text. The timer can keep running until you decide that you want to remove the display, either when the ground speed increases past a certain point, or when you leave the ground (up to you). You can also kill the timer when you do this, so the lua stops running (as I presume its no longer needed once you take off). Alternatively, you could have the lua run on a button or key press, to display the information on a key or button press, and remove it on the next.

Hi John, its just that the view controls have not been available since the release of MSFS. I actually haven't checked these in a while, but I presume this is still the case. You can find the current known limitations in the provided README.txt: I don't expect you to read each and every forum post, but you should always read a file called README....! Of course, such information is also easily forgotten... And i need to see the full log as this contains information I need that is not available in a continuation log, such as the FSUIPC version being used, the current loaded aircraft, any programs that re running (including lua scripts that are auto-started), etc. Just rememeber in future to always show/attach a full logfile when you have issues or need assistance, not a continuation log. Regards, John

www.fsuipc.com will give an unsafe warning, as its http only and not https. I've not added a certificate up till now, as its not really been needed. It will be updated at some point, when I get around to re-vamping the site. For now, just ignore the warnings. John

First, you posted a continuation log. That is of no use to me - I need to see the full log. In future, please only attach full logs - don't ever start a new log file. I am going to remove this option as it is always over used/abused. How have you assigned the camera controls? It is known, and has been since the release of MSFS, that the provided camera control events do not work in MSFS. This is stated in many places. To control the cameras via FSUIPC, you have to assign to the key presses that control the camera views, that are assigned by default in MSFS. Otherwise, you will have to assign in MSFS directly. Any other issues, please let me know and show me your most recent FSUIPC7.ini and FSUIPC7.log files (not a continuation!).

That depends on what you want to do with them! Just to read/log the values first, to see if they are populated and something that you can use, try logging them first with the FSUIPC offset logging facility. If they contain the values you need, or the values that you can calculate what you need, you can then write a lua script to read the values, adjust as needed, and then display them, either using the ipc.display function or the lua wnd library

To register WideFS7, you need to re-run the FSUIPC7 installer, and enter your WideFS key in the appropriate field (labeled WideFS Key). If you have already registered your FSUIPC7 version, the other fields should be pre-populated from your current FSUIPC7.key file. Clicking the Register button will valid both keys and update your FSUIPC7.key file. Use the check-box if your email or address are different between the FSUIPC7 license and the WideFS license, otherwise ignore.

I think there is a cheaper bundled price, but as WideFS7 is still with Pete, I'm not sure if this applies to FSUIPC7, which is one of my products. I cannot see the discounts available with WideFS7. Maybe @Pete Dowson could check and confirm, and maybe add the same discount on WideFS7 for FSUIPC7 as for other FSUIPC versions, if this is possible (i.e. adding a discount from a purchase from another vendor).