John Dowson

That is not going to happen I'm afraid. All lvar values are just treeted as 8-byte/64-bit values. It is up to the user to know the actual type and treat accordingly. No. The Java Native Interface (JNI), which is what is used to call narive C/C++ code from java. See https://www3.ntu.edu.sg/home/ehchua/programming/java/javanativeinterface.html. There may be other frameworks built on top of JNI that are easy to use, but I don't know about them. I was a java/J2EE programmer/architect for many years, but now I'm back in the C/C++ world I haven't touched java for 3-4 years or so....

Would you be populating these offsets yourself, or via some third party program? Although the information to populate the weather offsets is not available, I'm not sure its possible to write to them directly at the moment. You could try this, and if it doesn't work let me know and I can maybe look into free-ing those offsets to allow them to be used as free user offsets. Alternatively, you could write your weather data to a free user offset area, and spoof the actual weather offsets you want to use (replacing them with the data in your user offsets) using the spoofing offset at 0024. There are a couple of recent support requests where I have shown how to use this offset to spoof data - you can take a look at this support request (for spoofing the Parking Brake offset for the A320):

Event files (*.evt) should go in your FSUIPC7 installation folder. You may also need the MobiFlight WASM module installed, although I'm not 100% certain if the A32NX events are handled by the MF WASM module or the FBW A32NX itself. Once the event file is recognised, you should see the custom events in the controls drop-down menu, in the assignment panels. FSUIPC will just log the events it receives from MSFS. As custom events are handled by the add-on, I am not sure if you will see them logged in FSUIPC. Which version of the FBW mod are you using? This is the comment on that event (in the MF spreadsheet): dev version, soon on experimental, this does not work on the stable version. See A32NX_FCU_AP1_PUSH i.e. only on the dev version at the moment.

Before you buy, download and try it first. You can download from www.fsuipc.com, and there is a trial license available here: FSUIPC7 should be all you need. For the FBW A320, you need to use lvars and hvars to control many functions, sometimes by simply setting a value to an lvar, or activating a hvar, and sometimes more complex code is needed that can be ran using the FSUIPC lua ipc.execCalcCode function. There are various examples/support questions in this forum, as well as user-contributed lua scripts, on how to do this. Some people find it easier to use the MobiFlight WASM module, in conjunction with FSUIPC event files (to make the MobiFlight events assignable in FSUIPC7), so that they can use events rather than lvars/hvars/calc code directly. There are a couple of topics in this support forum that show you how to do this. A good resource for available hvars and calculator code id the MF spreadsheet: https://docs.google.com/spreadsheets/d/1jTXlcHaJWx0B7TB63Pmma7bKwpxsxXJO6EJ3ECt7zpc/edit#gid=373655063 If you decide that you wish to purchase a license for FSUIPC7, it is available from SimMarket: https://secure.simmarket.com/john-dowson-fsuipc7-for-msfs.phtml John

I thought this was done automatically when you set the com/nav buttons. How are you doing that? You could try using hvars. These are the ones available for the GN530: and these for the GN430: To test them (before adding them), you can use the Add-ons->WASM->Execute Calculator Code... menu option. So, for the GNS530, you can try to execute the following: That should switch between Com and Nav/VLOC. and highlight the frequency that is controlled by the inc/dec knob.. If that works, you need to add an *.hvar file for the C172 (e.g. Skyhawk.hvar) containing the hvars you wish to use (preceded by 'H:') to the FSUIPC7 WASM folder (under modules). You can then trigger the hvar via either lua or using a macro - details are in the Advanced User Guide.

Just took a look and I think I know what you mean... The UI yoke seems to behave as if a response curve has been applied, or at least doesn't appear to move linearly with the input through the whole 90 degree rotation (in each direction). It will be with Asobo not brunner - you can ask on the Asobo forums for MSFS.

Yes, this is something I could add. I am planning to refactor aa few areas of the WASM in the coming weeks, so I will also look into adding some sort if automatic lvar refresh. For the time being, you can now easily do this with a simple lua script- just a matter of using event.timer to call a handling function at regular intervals, then in the handling function just call ipc.reloadWASM(), i.e. local period = 600 -- period in ms, adjust as needed function reloadLvars(time) ipc.reloadWASM() end event.timer(period, "reloadLvars") Save that to a file called reloadLvars.lua, then add a line to the [Auto] section of your FSUIPC7.ini (create section if you don't have it): [Auto] 1=Lua reloadLvars Wow - impressive! If using the Java SDK, you could also access lvars directly using the WASM API (WAPI). There is a dynamic library available that you can use (via the Java Native Interface). Using that, your program would have access to an internal table of all lvars/hvars directly.

You have an additional comma after the condition, should be: 24=CP(-B,1)C,2,C66587,40002 Pete accidentally added that - I will correct his post...

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.