John Dowson

Please see the README.txt file included in the FSUIPC zip file that you downloaded. This is due to a lua crash: Unfortunately there is no information given about what lua file is causing that. Maybe that is related to linda? Maybe ask on the linda support forum to see if any one else has reported issues when closing down. Otherwise, try disabling the luas you are using one at a time to see which lua is causing this issue.

I have an offset to allow you to set lvars, activate hvars, call a preset or execute calculator code in the attached version, if you would like to try. The offset is at 0x7C50 (64 bytes), and the parameter value is at 0x780 (8 bytes). Always write the parameter first (or write both offsets together), as it is the write at offset 0x7C50 that triggers this. For lvars, the first characters must be 'L:', and the parameter value is an 8 byte string (including terminator). For hvars, the first characters must be 'H:', and the hvar must be known to FSUIPC (if it isn't known to FSUIPC, write as calc. code, e.g. '(>H:hvarName)'). For presets, the first characters must be 'P:', and the parameter is a 4-byte (dword) number (not a string!). Anything not starting 'L:', 'H:' or 'P:' is considered to be calculator code and will be executed as such. Let me know if you have any issues. Note this version has also been built against the latest MSFS SimConnect SDK (v0.17.0.0) and contains additional controls/events. I will publish details when officially released. John FSUIPC7.exe

FSUIPC should now recognise up to 128 buttons. And the encoder buttons are recognised in the assignments, so I don't think that is the issue. What are the button numbers (not assignment indexes) for the unrecognised encoder buttons (i.e. the numbers you see in the assignment panel)? Your FSUIPC7.ini would tell me - still waiting to see that... You could try an assignment to your button numbers 63 and 64 to check that there is not a limit somewhere that makes it fail after button number 63 (which will be your 64th button). Unfortunately I don't have any devices with so many buttons so difficult for me to test. i will look into this in more detail, probably at the weekend - I need to finalise and release the next FSUIPC version (v7.2.17 or possibly v7.3.0) in the next day or two, and I will look into this in more detail once that is released. John Later: you could try activating all of your buttons with numbers > 57 to se which ones are logged (open the logging console and see if recognised when pressed, although you will only get the joystick values logged if not assigned. I'll test with a virtual device at the weekend.

👍 If you have not yet updated to 7.2.16, please do as this includes direct access to the Mobiflight presets (i.e. you can assign to them directly). These are probably easier to use than using lvars/hvars in macros, and you can use the MobiFlight HubHob site to search for existing presets by aircraft and subsystem (as well as key words). You can also create your own presets using lvars, hvars, etc. John

The additional lua libraries/functions provided by FSUIPC are defined in the document FSUIPC Lua Library, which should be available in pdf format in your FSUIPC documentation folder. John

Glad you found the problem! Good to hear! Regards, John

If you had checked your ini file you would find that your key assignments to control 1070 are invalid and have been ignored: The 'C' character is not needed in key assignments. Remove those and try again. Attach your ini and log file (keyboard keys) again if any issues. John

I've tested here and cannot see any issues. Try setting the ServerName parameter in your WideClient.ini file rather than using the address (maybe this has changed?). Also, if you still can't connect, try disabling any firewalls on both the client and slave PCs.

Sorry, it is buttons 157 and 156, for assignments with indexes 82 and 80. I understand your issue but do not understand why the other encoders aren't being logged - at least the button numbers should be logged when triggered. It is normal for the encoder button numbers to be n and n+1. The assignment indexes don't matter really - they will only be logged if there is an assignment to the button. I'm not sure why nothing is being logged for some of your encoders - i will take a look at the code to see if there is any further logging I can activate or add. John

There should be no change to WideFS between those versions. Can you attach your WideServer.log and WideClient.log files, as well as your FSUIPC7.log file.

That won't work and I don't understand why you would even do that. There is no such section as [L:vars]. Please read the documentation and not invent your own syntax. To assign to an lvar, you need to create a macro file (*.mcro), or add it to an offset and assign your button to one of the offset controls. John

Your code doesn't make much sense. To define the table you should use: TableA = { ... } Why are you using the io library? For logging, use ipc.log. Your readTableA function also makes no sense - I am surprised that doesn't give an error as the for loop syntax is not correct... Try an on-line lua tutorial to understand the basics, and take a look at some of the example lua scripts provided.

Can you please attach your FSUIPC7.ini so that I can see your assignments. Your log shows the AP_VS_VAR_INC and AP_VS_VAR_DEC being sent on buttons 82 and 80. There are no AP_MACH_VAR_DEC or AP_MACH_VAR_INC controls sent from your "working" encoder.

Sounds like Asobo haven't connected the simvar to the visuals. I don't think there is much that can be done about this at the moment, except maybe to raise a bug report to Asobo to get this fixed. John

Try searching for relevant key words... For the A32NX (Asobo and FBW - the latter is more functional....) try the MobiFlight HubHob site to see what presets are available (https://hubhop.mobiflight.com/). MobiFlight presets are directly assignable in the latest FSUIPC7 release, v7.2.16. The PMDG 737 for MSFS has still not been released, as far as I am aware... See Appendix 3 in the Advanced User Guide 'Handling VRInsight serial devices in FSUIPC' and the document Lua Plugins for VRInsight Devices.pdf if you want to use FSUIPC for this device. John

The current FSUIPC release should work fine with the latest MSFS release. Thus sounds like the UI is being positioned off-screen. Do you not see the FSUIPC7 icon in your task bar? If it is a positioning issue, delete the Window parameter for your FSUIPC7.ini [General] section - this will reset to the default window position and size. Does this mean that you can see the GUI when MSFS is not running? There really should be no difference in the FSUIPC7 main window position and menus displayed whether MSFS is running or not... Get what working? You don't supply much information.... Please give me a full description of your problem, and attach the relevant files, which would be your FSUIPC7.ini and your FSUIPC7.log with the relevant logging activated (Buttons + Keys and Events) showing your issue. John

I don't think so. I don't know about x-plane, but for MSFS FSUIPC7 is just reporting the simvar OVERSPEED WARNING in offset 0x036D. If this is not correct, you need to raise a big with Asobo. Also, not related to the E190, but this may help: https://forums.flightsimulator.com/t/overspeed-warning/206852/5 John

Ok, then maybe we should try and figure out what is wrong when using standard keys first. If we can get it working with those, then after switch to your devices keys. So, configure with standard keyboard input, and then show me the your ini and log files (with logging activated for buttons + keys and events), and we can see what is happening, and take it from there.

But I thought your button (conditional) assignments work working, and it was the key assignments that you were having issues with.... This is what is worrying me...if there are confusing "key reads" in the assignment panel, I would have thought they would also be confused in the assignments themselves...but logging should show this... Conditional and compound assignments work the same way on keys as they do on buttons. If they are working for you as expected on buttons but not on the keys, I suspect it is related to these spurious key reads you are getting from the device...

If you can't find any standard controls for a function that you would like to control. try searching for a MobiFlight preset for the function at https://hubhop.mobiflight.com/. If I look there, I can see the following MF presets: C_172_PEDESTRAL_LIGHT_INC C_172_PEDESTRAL_LIGHT_DEC C_172_PANAL_LIGHT_INC C_172_PANAL_LIGHT_DEC I can't see anything for the glareshield - maybe it comes under a different name? Check the MF preset list to see if available. In the latest version of FSUIPC7, v7.2.16, the MF presets are included and you can assign to them directly (no need for the MF WASM module to be installed). You need the FSUIPC WASM module installed and enabled to use the MF presets directly. John

Sorry, I don't understand...the trial license key file is available in the first post in this topic, nowhere else. What is the problem? Just download that and copy/move to your FSUIPC7 installation folder. John

Trial license has been updated. Just download this and copy/move to your FSUIPC7 installation folder. No need to re-run the installer - the trial license will not validate in the installer. John

Done. No need to request twice! John

Please show me your FSUIPC6.log and FSUIPC6.ini files - they will be located in your FSUIPC6 installation folder. John

First, before purchasing a license, please try the trial license to make sure that you want to use the registered facilities. There is one available in a sticky post at the top of this sub-forum, although I think this has now expired. Please post in that topic if you would like to try the trial license and I will generate a new one. If you have already tried the trial license and would like to purchase, you can buy a license from SimMarket here: https://secure.simmarket.com/john-dowson-fsuipc7-for-msfs.phtml Once you have purchased a license, re-run the installer and register your license at the end of the installation process. Please read the Installing and Registering FSUIPC7 document, included in the installer zip file, which will explain how to register and where everything is installed. John