John Dowson

License sent - please also see Done. John

How have you assigned your throttle? I have noticed similar behavior when assigned as 'Send to FS as normal axis;', except they remain synced when I move the throttle 1 axis but separate when I move the throttle 2 axis. However, if I assign as 'Send direct to FSUIPC calibration; to Throttle1 and Throttle2 it seems to work - the throttle 1 axis works syncing both throttles and the throttle2 axis has no effect.

Ok - with further testing I have found that you can use Landing Lights On/Off with a parameter of 0 for nose, 1 for left and 2 for right.

Have you tried Landing Light Left and Landing Light Right, with a parameter of 1 for on and 0 for off? To determine what control is used by any button or switch, if any, you can set logging for Events (Log->Events), open the logging console window (Log->Open Console), and then operate the switch in the VC and see what control/event and parameter is/are used, and then assign to that. Later: I have just taken a look and all the landing lights (left. nose, set) are just using the Landing Lights Set control, with a parameter of 1 for on and 0 for off. However, sending this will turn all the landing lights on/off - it doesn't look possible to control them individually... John

There is nothing wrong. Many MSFS aircraft continually send various events/controls, and these are different for each aircraft. You can use the DontLogThese ini parameter to stop such events being logged, best used in a profile section as they are aircraft specific.

Hi Paul. Sorry for the delay with this... I have checked the code and the throttle-sync controls do exactly the same thing as the hot-key assignment in P3D, so I am not sure why it isn't working the same, but probably due to aircraft differences. I will take a look further when I can. What aircraft are you using this with in MSFS?

But why are you trying to use lvars for these? For example, for the beacon lights you can use the standard controls: Beacon Lights On/Off/Set. You should always try standard controls before trying lvars. And some controls require a combination of lvar/hvar/standard controls, and for these it is easier to use presets. I recommend that you always first try any standard controls. If they don't work, the next port-of-call should be the HubHop preset list (https://hubhop.mobiflight.com/presets/) where you can search for available presets by aircraft and sub-system (amongst other search parameters). All MF presets are available for assignment by checking the Select for preset checkbox, If the standard controls don't work, and there are no available presets, you can then start looking at available lvars, and even looking at the aircraft xml files to see if any hvars are available, or at the code that implements the UI to see how the switch works...but this can get quite complicated to understand and is recommended for experts only. You can always post a request in the MF discord channel to ask if someone knows the preset code for a particular button or switch if its not currently available. John

Ok, that is strange - the lvar WASM should not have that much impact in performance. You could try tuning the WASM by setting the following WASM ini parameters: LvarUpdateFrequency=Second -- this will then only send lvar updates every second, rather than at 6Hz LvarScanDelay=10 -- this will delay the initial scan to detect lvars by10 seconds (default is 5) LvarScanFrequency=-20 -- this will instruct to only scan for new lvars every 20 seconds (the default is 2 seconds) It is used to provide FSUIPC and FSUIPC clients with access to lvars, hvars and calculator code. There are also some non-FSUIPC add-ons that also use the facilities provided by this WASM module. I don't know if the apps you use will use this - if they work ok without this then you are probably Ok. As you are using the free version of FSUIPC, FSUIPC itself will not be using the WASM module unless for an add-on. John

Looking into this further, I noticed this on the AS6 page: Advanced radar and precipitation, cloud detection, motion effect, in-cloud visibility reduction and advanced radar API and ASCA cloud structure/texture integration available in legacy (non-volumetric) clouds mode So I turned off volumetric clouds in the P3D options (moved slider in World->Weather->Volumetric Clouds to off) and can now see the correct values in offsets 0x8640 and 0x8641. Could this be your issue? i.e. try disabling volumetric clouds

I finally managed to get a license for AS6... The visibility offset 0x863C looks ok here - this is what I see when I set custom weather as rain: I also get no data in these offsets. I have raised this with AS. The documentation is wrong and will be updated - it uses the as_connect_v5.dll, the same one as for P3Dv5. And the dll does not need to be in the FSUIPC installation folder (my mistake), as FSUIPC links to/uses the one running in the FS. I will check the other data points and let you know if/when I hear anything from HiFi Simulation Technologies. Note however, it is a beta release and it does say: This is a BETA version and it will have bugs, issues and be unfinished. John

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 }-