John Dowson

Sorry, but it is not clear to me what you are asking...why do you need to use lua? Are the lvars used for reading (displaying values) or for updating (sending values), or both? You can also use lvars via macros, or you can add them to a free/spare FSUIPC offset (using lua) and use that for both reading and writing/updating. Do you mean the G1000 is displaying the wrong values? Where is it getting the value of 1400 from? what holds the correct value of 2500? if you have any specific questions I can try and answer those, but I cannot advise on how to configure hardware that I do not know for am aircraft that I do not have.... John

TOGGLE_EXTERNAL_POWER is a control/event, not an lvar. To send this event, you can use the the facilities provided at offset 0x3110 to send any control to the FS, using the control number 67090. Alternatively, controls are also known as k-type variables, so you can achieve the same by sending the calculator code "1 (>K:TOGGLE_EXTERNAL_POWER)". John

The spoilers assignment will be triggered whenever button 2 on joystick 0 is pressed. The reverse thrust assignment will be triggered when button 2 on joystick 0 is triggered, but only if button 0 on joystick 0 is pressed. If you want to prevent the spoiler assignment from also being triggered, then you have to add another compound condition to only send this when button 0 is not pressed, i.e. 1=CP(-0,0)0,2,K191,8 ; (spoiler) John

Is FSUIPC7 actually running? i.e. can you see it in your system tray? If it is not auto-starting with MSFS, have you tried starting it manually? Note also that if you have re-installed Windows 11, you may also need to download and install the latest combined VC++ redistributables. Not having these installed can prevent FSUIPC from starting. Instructions are provided in the FSUIPC README.txt on this issue. Other than that, If you have a problem with sim-acars, then you should contact support for that program. I only support FSUIPC.

Ok....that was the first thing I asked you to try.... I don't know how that can happen... if you are using profiles-in-separate files only the aircraft-specific ini should be used. Looking at the FSUIPC4.ini you posted earlier, the following should be removed (or moved/copied) to your F18.ini: I don't know - this shouldn't happen., Just manually correct - not worth me looking into this. John

That is a compound button control and can only be added by editing the ini file. I am not going to go into details on how FSUIPC implements assignments, but key and button press events are not stored in memory. The events are received from either windows or via SimConnect when they occur and are then acted upon. These events are not "stored in memory". Why do you want to know this? You don't "access/track and use or manipulate key press events". You just assign an action to be performed on a key press/repeat/release event. As a user, you should concentrate on how to use the functionality, not how it is implemented. What are you actually trying to achieve?

Can you please also show me your FSUIPC7.log file, generated with logging for Buttons & Keys and Events activated, as well as WAPI debug logging. Also please list the lvars before pressing the button(s) assigned to update the lvar. But that doesn't use the offset. Please also try this before exiting FSUIPC7 and attaching your log file. John

Ah, sorry - for FSUIPC6 it will be the OptionsDialogOffset line, not the Window one (that is FSUIPC7).

Different sections and even specific parameters are read when needed, others are only read at start-up. I am not going to go through each parameter to see when it is read. Just assume they are read wither at start-up or aircraft load, unless explicitly stated otherwise in the documentation. But there is no value associated to a key press - there is a key press event and a key release event. Well, there is a flag associated to every button (Button Flags) of that is what you mean, but a button press is an event. In the line below, the modifier key I'm referring to are in bold. Is there any way I can assign this in the FSUIPC panel (and not have to manually edit the .ini file)? <Entry number> = <Action><Joy#>,<Btn#>,K<key>,<shifts> That is not a modifier key, but the format of a button assignment line when assigned to send a key press or release. This is set when using the left-hand side of the button assignments window, where you enter the key press (combination) to be sent on the button press.

You can use: Cheers, John

Only if the spoilers don't fully deploy when the lever is in the up position, as I said... Yes. Once you have set the multiplier, you can calculate the addition parameter so that full deflection (lever up) of 16383 gives 16383 once both the scale multiplier (m) and addition (a) have been applied, so (16383 * m) + a = 16383 a = 16383 - (16383 * m) Make the changes with FSUIPC open and the axis assignment panel showing. When you have saved your changes, click the Reload all assignments button to reload the changes.

It gets read at various points, but not when you press a button. You can also force a reload by pressing one of the reload buttons in the assignment panels. Sorry but I don't understand this....what do you mean by "value"? There is no value associated with a button press. A repeating button will just send button press events until the release is sent. You can have multiple assignments to set the view mode based upon the current view mode, using offset conditions (see Advanced User guide) on offset 0x8320 (current view mode). If there are multiple assignments to a button or key press, then they are executed in index number order. There is only logging - for example, logging for Buttons & Keys will show you which assignments are executed, as well as those not executed due to compound button conditions or offset conditions on an assignment. Not sure what you mean....there are no "modifier keys" for button and switch assignments. Again, there are no "modifier keys" for button and switch assignments. Not directly, but you can achieve this using flags or offsets. You would set a button flag (one for a button/device that you are not using) on the key press, and clear it on key release. Then, on the button assignment, you would use a compound button condition on the state of the flag. Alternatively, you could write a value (1) to a spare FSUIPC offset on the key press, and clear the value (0) on key release, and use an offset condition on the button assignment to check the value of the offset. John

The FSUIPC window is most probably being positioned off-screen. To correct this, remove the ini parameter Window from the [General] section of your FSUIPC6.ini file, which is what holds the main window size and position. Do this before you start P3D/FSUIPC. John

Yes. I had noticed this but hoped it was temporary... I will either include the image or use/upload one to a more permanent location...depending on copyright.... Thanks for reporting. Regards, John

You can first try just decreasing the addition parameter, e.g. CZ,256,F,66382,0,0,0,*0.6428227,+5200 -{ TO SIM: AXIS_SPOILER_SET }- This will send a lower value when the lever is in the down position, but the higher value sent when the lever is in the up position will also be reduced, and so the spoilers may not be fully deployed when in this position. If this is the case, you will also need to adjust the multiplier, so try: CZ,256,F,66382,0,0,0,*0.65,+5733 -{ TO SIM: AXIS_SPOILER_SET }- or for an even larger range: CZ,256,F,66382,0,0,0,*0.66,+5570 -{ TO SIM: AXIS_SPOILER_SET }- or even CZ,256,F,66382,0,0,0,*0.7,+4915 -{ TO SIM: AXIS_SPOILER_SET }-

Can you please see the Advanced User guide on how to use the axis scaling facilities. The axis scaling parameters go on the axis assignment line, not in the calibration section. You need to add profile-specific axis assignments to your 737 profile, then change the spoiler axis assignment to 3=CZ,256,F,66382,0,0,0 ,*0.6428227,+5851 -{ TO SIM: AXIS_SPOILER_SET }- i.e. change the assignment from, 'Send direct to FSUIPC calibration' to 'Send to FS as normal axis' and also delete/remove the spoiler calibration entry.

Why do you have a maximum spoiler axis range of only 5851? As we are scaling the axis, best to just remove the calibration - click the Reset button and try again. And check that you have those axis scaling parameters in your ini.., using that should send a value of around -4681 when your throttle is at the lowest position of -16384: (-16384 * 0.6428227) + 5851 = -4681 If you still have issues, please attach your FSUIPC .ini and .log files (not pictures!).

You can have multiple assignments to the same button or key press. Make the first assignment, then open your FSUIPC ini file in an editor. Also open fsuipc and go the button assignment tab. Then comment out the first assignment in your ini by placing a semi-colon (;) after the equals sign (=) on the assignment line and save. Then click the Reload all buttons button in FSUIPC to reload your updated ini. You can now assign the second action to the same button and click Ok. Now reload the ini file in the editor and also open FSUIPC's button assignment window again. In the editor, remove the semi-colon you previously added (to comment-out the assignment) and save the changes, and then click the Reload all buttons button again to reload the ini file. You should now have multiple assignments to the same button. Note that you will only see one assignment in the FSUIPC assignments panel, and it will be grayed-out there. The only way to update/change such assignments is by manually editing the ini file.

You can use FSUIPC's axis scaling facilities to achieve this, described in page 46 of the Advanced User guide. You want to scale the range -16384 to + 16383 to the range -4681 to +16383, so you would need to use the following scaling parameter: ,*0.6428227,+5851 Just add that to the end of the spoiler axis assignment line in your 737 & CRJ700 profiles.

I don't know why you say this... I have a long list of user requests and I process and implement them as time permits...unfortunately, most of my time is taken up by support requests, which take priority. I also have an issue with my eyes - I have a genetic degenerative eye disease (Retinitis pigmentosa -RP) so I am certainly willing to improve the visual aspects of the software I provide, but there are only so many hours in a day and I have to prioritise, which doesn't leave me much time. If I could only spend less time on support questions, especially those that could be answered if people actually consulted the documentation I provide and used the resources available before posting questions.... this would save me a lot of time and I would have more time available to implement such features... That is, of course, up to you. SPAD.next is also a great tool - I also use this occasionally. But it doesn't provide the power and control that you can get with FSUIPC, but is generally easier to use for novice users. I don't mark threads as solved - they need to be open if someone has a similar issue that they need to discuss. Regards, John

But why? Yes, that is where they are installed.... unzip/decompress that file, and copy or move the lua file you want to use to your FSUIPC7 installation folder, which is: C:\FSUIPC6 it will then be available in the assignment menus to be started on a key or button press. Or you can start it automatically using the [Auto] or [Auto.xxx] (where xxx is a profile name) in your FSUIPC7.ini file - see the Advanced User guide for details. John PS. Please see the provided FSUIPC Lua Plug-Ins document...

Your log file does not show anything untoward. I have also just checked here using the FBWA320 (stable version) and do not see any noticeable drop in FPS. If you start MSFS without FSUIPC7 (with the FPS counter window open), load the FBWA320 and wait a few minutes, what does your FPS settle to? If you then start FSUIPC7, again wait a minute or two for everything to load, what does your FPS then settle to with FSUIPC7 running? You can also take a video of this test and show me so that I can see any performance degradation. Can you also try without the FSUIPC7 WASM module running - just (temporarily) move the fsuipc-lvar-module folder out of your MSFS Community folder before you start MSFS. Do you still get the same performance issues without this running? John

To get hvars recognised by the WASM and FSUIPC7, you need to use *,hvar files and place them in a specific location. Some *.hvar files are installed by default (for A320, DA40 TDI, DA40-NG, DA62, Skyhawk, TBM) and others are provided in a sub-folder of your FSUIPC7 installation folder called HvarFiles. To use these you must copy/move them to one of the folders where they are recognised, and also make sure that the name if the file is a sub-string of the aircraft name/title. Please see the section Using Hvars in page 47 if the Advanced User guide for details. However, it is far easier to use hvars via calculator code or presets, and they do not need to be made known to FSUIPC with these methods. John

Licenses have been sent via PM. John

Lua scripts, by default, just go in your FSUIPC6 installation folder. Note that you seem to have installed FSUIPC6 under your windows Documents folder: C:\Users\adm_local\Documents\Prepar3D v4 Add-ons\FSUIPC6 This is not a good location, as that is the location of your add-on.xml file that is used by P3D to auto-start FSUIPC6 with P3D. Better to re-install into a non-windows protected folder really - but this is not related to your issue. If you can't see the script in the drop-down (prefixed by Lua, LuaDebug, etc) then it is not in your FSUIPC6 installation folder with a *.lua extension. Check the extension - sometimes people find that a .txt extension has been added... You can do this either using the ipcinit.lua or ipcready.lua files (see the FSUIPC Lua Plug-Ins document for details), or, better, use the [Auto] or profile-specific [Autp.xxx] section in your FSUIPC6.ini file - see the section Automatic running of Macros and Lua plugins on page 41 of the Advanced User guide for details. John