John Dowson

Did you make any progress with this?

Any feedback Luke? Is it working as expected?

It was clear what your issue was - was my response/previous comment not clear? Your problem can be caused by several things, and so I need to see your log and ini files to determine what the issue is. However, I did notice some issues in the ini you posted, so I corrected those. Therefore you need to try with that updated ini file I attached and then show me your ini and log files with the recommended logging activated.

Why are you using offset 0xA350/0xA358? Those are in an area documented as Reserved. Not sure what that offset area is reserved for without checking, but can first try with offsets free for general use. If you get the same issue, please attach your FSUIPC7.ini and FSUIPC7.log files, the latter generated with WAPI debug level logging activated, as well as offset monitoring for the offsets you are using. Just load the aircraft, list the lvars, then exit.

Of course, but please at least consult the documentation first, and search the forum as your questions may already have been answered. Cheers, John

I have corrected a few things in your ini (missing joystick for your Alpha due to a change in GUID, substrings for profiles) so please try with the attached, although this may not fix your problem - see later): FSUIPC7.ini I see you are also still using the hidBravoButtons.lua script. This was previously needed to recognise the button numbers > 31, but FSUIPC7 now (and for 2 years or so) recognises these buttons natively without this script. You should remove this at some point and update your assignments accordingly, assigning to the actual button numbers rather than the virtual button flags. The same is true of the hidAlphaButtons.lua script, but you don't seem to be using that one anymore. If you get the same issue, please activate logging for Buttons & Keys and Events, and generate a short log file showing your issue, and attach that together with your ini file again. John

The latest official release is 7.3.24. There is a beta in one of the forums for 7.3.25a, 7.3.25b and 7.3.25c, but 7.3.25 has not yet been released. I don't know why it would say that when that version is not yet available. Try using 7.3.24, and if you get issues then try the support of your acars provider. The only changes from 7.3.25 to the latest 7.3.25beta are: - WAPI updated to 1.0.3 to prevent a thread issue that can cause the WAPI to stop functioning (very rare timing isssue) - minor correction to the simconnect re-connect functionality that prevent FSUIPC7 from shutting down in certain situations (again, rare) - updates to the pause states indicator in offset 0x0264 I can see why your acars would need any of these changes. John

Read the section Adding Lvars to Offsets - it is not that complicated, and your use case is verry similar to the example given. As all the lvars you are using hold integers < 255, you can add them all as unsigned bytes, and then use the Offset Byte Set control, giving the offset and value, for your assignments. You should really be using profiles, so if you have a profile for this aircraft (lets call it 'xxx'), then you would add the following to your FSUIPC7.ini: [LvarOffsets.xxx] 1=L:EMB110 BATTERY SWITCH POSITION=UB0xA000 2=L:EMB110 WIPER L POWER SETTING=UB0xA001 3=L:EMB110 WIPER R POWER SETTING=UB0xA002 Then assign your button or key to Offset Byte Set using offset A000 for the battery, A001 for the left wiper, and A002 for the right wiper. If you want to control both wipers with one button/key, you can either overload the assignment or assign one to the press and the other to the release.

The functions provided by Asobo to save and load flights (and also flight plan)s are still not 100% working, and are documented as 'NOTE: The current status of this function is NO ERROR, NO RESPONSE.', So not much can be done about this at the moment i'm afraid. Although the plan should be saved and loaded with the flight, you could try explicitly loading the plan again after loading the flight to see if that works.

For the Battery Master Switch, you can use the lvar EMB110 BATTERY SWITCH POSITION, which takes the values 2 - Bat 1 - Off 0 - External Power (this seems to be momentary, and goes back to the Off position once set) To use this lvar, add it to a free FSUIPC offset (see the Advanced User Guide on how to do this) for both reading and writing/updating. You can then assign a button or key to set the value to the offset (or inc/dec/cycle the value) using the provided offset controls, and this will then change the value of the lvar. For the wipers, you can use the lvars EMB110 WIPER L POWER SETTING and EMB110 WIPER R POWER SETTING, which take the values 0 - Park 1 - Off 2 - On John

Ok, your ini file shows the Rotaries.lua is recognised but you do not have it running. You should add the following to get this lua auto-started: [Auto] 1=Lua Rotaries Once this is running, this will enable "virtual buttons", converting the single button, in each direction, of the rotaries to a slow and fast button. You should remove (delete or clear) your assignments to the original buttons, and assign to the fast/slow virtual buttons. You should use the IgnoreThese ini parameter in your [Buttons] section so that the physical button press is not registered, only the virtual ones. Also, looking at the rotaries script you attached: This cannot be correct - you cannot have button 28 paired with both 29 and 27..... Remember, each pair of entries corresponds to the two buttons, one in each direction, of one rotary encoder.

You need to first check to see if any lvars are available to control these functions. Try listing the lvars (Add-ons->WASM->List Lvars) and see if any look appropriate. You can then change the control (in the VC) and list the lvars again to see if the value has changed. Once you have found the lvar and the values for each position, try changing the value using the provided facilities (Add-ons->WASM->Set Lvar...). If there are no lvars (or custom controls), then things get complicated. You will need to look at the xml code for each switch and try to determine how it is controlled. I don't have this aircraft so I can;t really help with this, but take a look at this tutorial: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/ I can see if I can get hold of this aircraft and if so can take a look. John

I am not sure - it has been a long time since I looked at that program - check the available documentation. You don't actually need to use flags - you can have a simple lua script that simply sends the throttle decrement control in an endless loop (with a delay). You then start the lua script on the button release, and kill the lua script on the button press. You should also overload your assignments on the press and also send a throttle cut. Cheers, John

If you want to assign to throttle decr (repeat) on release, and throttle cut on press (which would be opposite to how you would normally assign) then you could do this using button flags, You can set the flag (any random flag for a non-existent joystick button) on button release and clear the flag on button press. You would then have a lua scrpt that monitored the flag and send the required control (or key press) while the flag was set, and stop when the flag is cleared.

You don't make things easy...please paste text rather than pictures, as I can then copy adjust and paste... This is explained in the documentation and I have also explained this - I do not understand why this is so difficult for you to understand... wnd.backcol(w, 0x000) wnd.textcol(w, 0x6c0) wnd.font(w, WND_ARIAL,64) wnd.txt(w, "This text is normal") wnd.font(w, WND_ARIAL,64,WND_BOLD) wnd.txt(w, "This text is in bold") wnd.font(w, WND_ARIAL,64) wnd.txt(w, "This text is normal again")

There is a separate document entitled FSUIPC Lua Plugins From the aforementioned document: John

No. I do not understand what is so difficult - if you want help, show me/attach your FSUIPC4.ini file, and not your FSUIPC4.log file which you have now attached 3 times. Also, please do not start a new log file when posting log files for support. But do you have this lua script running? You would normally have this script started by the [Auto] section of your FSUIPC4.ini file (which you don't seem to be able to find...). Please see the Advanced user guide on how to automatically start lua plugins. John

No, you don't understand in the right way - this is the key paragraph that you seem to be missing: The font details apply for text drawn from then until the font is changed again, so any mix can be used in one window. Yes, of course. You set the font style you want to use, write those lines, set the next font style, write those lines, rinse and repeat.... John

You don't seem to be at all familiar with how lua plugins work. I suggest you read the provided documentation - the FSUIPC Lua Plugins document to start with. Please read the documentation BEFORE asking for support. I provide extensive documentation, and really would like users to consult the documentation before asking for help. This would save everyone time, and give me more time to improve/extend the functionality of FSUIPC, as well as improving the documentation. Currently I am spending almost all of my time on support questions that are easily answered if people had read, or at least consulted, the documentation before posting for help... Not only ia this incredibly boring and frustrating for me, but it also stops me from improving the functionality provided as I just have no time left after covering support. John

Why? That makes no sense - remove that. As I said, any lua file found in the correct place will be added to that section. It will be under 'Lua SetPauseMSFS&P3D' (as well as LuaDebug, LuaKill, etc) - look there... John

Unfortunately LINDA is no longer supported, as the developer is no longer available and has left the FS world. I have heard that is supports both the CDU II and CDU III from VRInsight (from 3.3.5), but you need to check the documentation. Sorry, but I cannot really help with LINDA, and other LINDA users on the support forum on avsim is your best bet. Best to tag the OP for such questions, like @AruzyGaming... John

Yes, you need to be logged in to download files. If it is not listed in the assignments drop-down, then it is either not in the correct place or does not have the correct extension. Why did you add it to be auto-started? You do now want to do this - and that is also incorrect (should be "1=Lua SetPauseMSFS&P3D"). Just remove it. When FSUIPC is started, it scans the installation folder (by default, can change by using LuaPath ini parameter) and adds them to the [LuaFiles] section. All lua files listed there will be available for assignment. Do not manually add the file to that section, as this is maintained by FSUIPC.

This is usually caused by the device' axis being flagged as a digital on/off axis. See this post on how to correct this: John

Updating FSUIPC should in no way affect your assignments, so something else must be going on. Such issues are usually caused by windows assigning a new id or guid to your controllers. Please attach your FSUIPC7.ini file and I will take a look - you should always attach this file if you have issues with assignments. For the landing lights, you can use the lvar L:C310_SW_LIGHTS_LANDING which excepts 3 values: 0 - Extends and turns on landing lights 1 - Turns off landing lights (but does not retract them) 2 - Retracts landing lights There are also three presets available: C310R Landing Lights Off, C310R Landing Lights Extend, C310R Landing Lights Retract You can use the lvar L:C310_SW_PRIMER, or the 3 provided presets: C310R Primer Off, C310R Primer Left, C310R Primer Right

XPUIPC is a different product to FSUIPC, by a different developer. I cannot help with X-Plane or XPUIPC, sorry. I believe the websocket server is an FSUIPC client application, so you do need FSUIPC to use this. From the WebSocket server home page (http://fsuipcwebsockets.paulhenty.com/😞 FSUIPC WebSocket Server is a program that enables reading and writing Flight Sim data via FSUIPC over WebSocket connections However, you should direct all questions on this to its author, Paul Henty, who has his own sub-forum here: https://forum.simflight.com/forum/167-fsuipc-client-dll-for-net/ Sorry, but I do not support this sim. John