John Dowson

Which version of FSUIPC are you using? The installer for FSUIPC5 must always be ran in admin mode, and the installer for FSUIPC6 requests admin level privileges. And if you are running P3D as admin, then as FSUIPC is an embedded dll, it also runs with admin privileges. It is normal for the P3D window to go black when you open FSUIPC. Sounds like the window may be being displayed outside of the screen coordinates. Try removing the parameter OptionsDialogOffset from your FSUIPC .ini file, in the [General] section.

Yes, I see the same. It seems that he requests from the WAPI to the WASM are working, but the data from the WASM isn't getting back to the client, so the client-side lvar/hvar lists are empty. I think this is because a lot of the functions from the WAPI.lib are missing from the dll, but I'm not sure how to correct this at the moment and don't have the time/resources to look into this, sorry. As I said, the project is now in github, so if anyone has any experience in wrapping a static lib in a dll wrapper, please take a look!

Ah, ok - thats good then, as you can just drop in the latest version and it will work without any changes. A few bugs fixed since 7.1.0a, but mainly in more advanced features. Yes, and lvar support is also coming soon. The WASM module (to enable lvar/hvar support) has already been released as a beta, and I'll be releasing yet another FSUIPC7 beta with lvar support in the next week or so. However, the initial lvar functionality will replicate previous lvar functionality in FSUIPC, so only accessible via macros or lua files.

Ok, well done - and thanks. Not sure which version of FSUIPC7 you are using, but there is also a beta version available (v7.1.0c) which has native support for up to 128 buttons, which will remove the need to use the Lua files for the Alpha & Bravo. See

Some issues with that version, please try the following: FSUIPC-WASMv0.4.7.zip

@d147 I have updated the interface rebuild the dll against he latest WAPI. Files attached below: FSUIPC_WAPI.hFSUIPC_WAPID.libFSUIPC_WAPID.dll I still don't think these are correct though, as the dll is only 96KB and the lib 8KB, whereas the WAPI lib is 6,473KB. I can push the DLL project to github if anyone wants to try and sort this out - I don't have time at the moment I'm afraid. John Later: I've just replaced the .lib/.dll so please download again. Project also available on github: https://github.com/jldowson/FSUIPC_WDLL As I have said previously, I don't think this is working at the moment.....

@andhogHere's the corrected version: FSUIPC-WASMv0.4.6.zip

If its a one button rotary, try the provided lua script, documented in the Lua Plug-ins document: If its a two-button type, then you can assign the different buttons to different increments (using the offset incr/decr controls). If its a phased rotary, then check the advanced user guide on how to handle. John

...power just back! Ok, will take a look. But tomorrow now..😴

Ah, yes - missed that. I will correct and let you know - tomorrow now though - power/electricity has just gone....

I don't think its an issue (at the moment) as only the CDAs needed (for the names) will be created, and its only an additional 8k CDA for the second values CDA, which won't get used by the client anyway. I'll look into allowing user restriction on the available lvars at a later date. Another quick and easy alternative for the time being would to add an extra ini parameter which can be set if you wanted to use more than 1022 variables, but I don't think its needed at the moment. Allocating an extra 8k, even if unused, shouldn't be too problematic these days.... Anyway, please try the version I attached. I can easily extend to allow for 1738 lvars (by allowing 12 lvar name CDAs which would accommodate 1752 lvars), or you can build yourself by changing the following in the WASM.h header file (if you are programming yourself, of course - if not, please ignore!): to Let me know if you want me to make a build for this...maybe this is something I can allow the user to set as an ini parameter, to basically tune to the needs of the user. However, this is obviously aircraft dependent, so I would need to allow tuning for profiles. Really, I need to concentrate on getting the basic functionality out and useable in FSUIPC7 before I consider such changes, but I don't mind over-tuning the parameters for the initial release, so it works for all/most add-ons, before I start adding the bells and whistles to tune.

Its up to you. You can still use the lua file in the beta version, with either the 128 button support enabled or disabled - from the Announcement page: You should try it, as its good to have people not using this feature (as well as people using this as well as the luas) to also test this beta. This will also be the official release at some point - hopefully pretty soon as I have had no further reports of any issues. John

Here - in the main support forum (I moved your post for you). The FSUIPC7 / MSFS sub-forum is specifically for FSUIPC7, all other support requests should go here. The 'User Contributions' forum is for contributions (advice, scripts, etc) from users, not support requests.

Ho Bob, First, you posted in the User Contributions sub-forum, where it explicitly states (in simple English!) NOT for Support Requests. Please take care to post in the correct forum for support (here or the FSUIPC7 sub-forum). The document you are looking for is the FSUIPC Offset Status document: 0480 8 Aileron trim axis input, 64-bit floating point (double), read-only ?-Intl N/A 0488 8 Rudder trim axis input, 64-bit floating point (double), read-only ?-Intl N/A 0490 8 Aileron trim axis required value, 64-bit floating point (double). If 2^0 is set in the byte at 04A0, then, when written, this value is copied to the FS trim (2EB0) instead of the value in 0480 N/A ?-Intl 0498 8 Rudder trim axis required value, 64-bit floating point (double). If 2^1 is set in the byte at 04A0, then, when written, this value is copied to the FS trim (2EC0) instead of the value in 0488 N/A ?-Intl Cheers, John

Hi Hal, please try the following: FSUIPC4.ini

Hi @andhog I have a new version ready for release that has support for up to 2048 lvars , although it is only currently configured to support 1168. However, as I don't have any aircraft with so many lvars (although I guess I could create lots...!), would you be able to test this for me before I release? Also, is support for 1168 enough - do you know how many lvars the CRJ has? The latest version is currently configured for 2 lvar values CDAs (2048 values) but only 1168 lvars (8*(8k/56)) but I can easily increase this now if/when needed. FSUIPC-WASMv0.4.6.zip

The dll is currently nor working, and I don't really have time to look into it. However, the API is available if someone else wants to try to create a dll from the static lib project. Thats ok - you can also just use: fsuipcw_init(NULL, 0, NULL); The parameter to this function is now an int, but you can still use the enum I guess (if supported by your language). Thats the default so you can skip this if you like. As @jaxx mentioned above, these functions need to be updated: But, I'm surprised you have as much working as you do! I can update those functions (maybe later this week), and maybe also provide write functions that accept the lvar name rather than the id for you. Please remind me if you haven't heard from me on this by Friday. John

Where are the options for this?

"High Performance" power management is different from USB power management, but as long as "Allow the computer to turn off this device to save power is unchecked" then this won't be the issue. Does your hub supply enough power to the connected devices? Also check if its USB 2 or 3 and matches the USB protocol of your devices - sometimes USB2 devices can be problematic on USB3 for some reason. Maybe also try your rudder on a separate USB hub if possible.

No, not that I'm aware of. Maybe, but not that I know of., sorry. If its just the case of using a different parameter for different aircraft, you could either use profiles, or you could maybe set the parameter to the correct value in your lua based upon something you know (or have access to), such as the aircraft name/title.

I am sorry but FSUIPC3 and WideFS6 are no longer supported (and are both way before my time I'm afraid!). Did you check that both computers are in the same workgroup? I can only suggest that you go through the user manuals which contain the information on how to set-up and trouble-shoot WideServer/Client connection issues. You posted in the specific forum for FSUIPC7 / MSFS. I have moved your post to the correct forum.

I think the first think you should do is upgrade to the latest version, v6.0.13. When you run the installer, it will first uninstall your current installation. When it comes to selecting an installation folder, don't except the default but change to a folder outside of your Documents folder, somewhere like 'C:\FSUIPC6 ' or 'C:\P3Dv5 Add-ons\FSUIPC6'. After you've done that, start P3D and see of FSUIPC is installed and available from the add-ons menu. If not, show me your new installation log. It looks like OneDrive is confusing the installation - better to install outside of your Documents folder, especially when using OneDrive.

I am not sure if mouse macros will ever be possible with MSFS - still needs to be looked into at some point. However, MSFS has HTML variables (hvars), which will also be accessible at some point via FSUIPC7. They are currently available for testing with the WASM module + test client. Note, however, that you (or someone!) will have to find.discover what hvars are available for a particular aircraft, and make them available to FSUIPC7 via a hvar file. Currently I have only determined the hvars that can be used for the A320,

Do you mean that when you select the 'Axes...' menu option from either the icon context-menu or the FSUIPC main window 'Assignments' drop-down menu, then FSUIPC 'disappears'? And what do you mean by 'disappear' - has it crashed or is it still running? Is the task bar icon still visible, or the system tray icon? Is it still running, i.e. can you see it and kill it in the tasks activities and kill it from there (if present)? And the same thing happens with 'button' assignments? What about 'keys'? Can you also show me your FSUIPC7.ini and .log files please.

It is located in the installation folder, i.e. the folder you selected (or accepted) when you installed, and the same location as the FSUIPC6.dll. If you don't know where that is, you can use the 'Open Folder' button located in the logging panel. Note also that the ini file is created the first time FSUIPC is ran, if no ini file currently exists. In that case, its sounds like FSUIPC6 was not installed correctly. Did the installation process complete ok to the registration dialog window? Show me your InstallFSUIPC6.log file, also located in your installation folder (and also the folder where you ran the installer).