John Dowson

I know what WidevieW is and does, I just have never used it and do not know anything about the configuration of this software, It is completely independent of FSUIPC and WideFS. What is the "package" you are referring to here? Do you mean the lua scripts, used by WideClient and FSUIPC? Then this sounds like a communication/network issue due to the W11 update, as you are using the same version of FSUIPC7. If the communication issue is with WideClient/WideServer, check those logs. Maybe the workgroup name has changed due to the update? Either way, if its a network error, then the WideClient / WideServer log files should report this. Of course. You don't need the separate WideServer any more, as its part of FSUIPC7. There is no change or difference when running either FSUIPC or WideClient on windows 10 or 11. Any differences encountered after such an upgrade must be due to the upgrade itself. And for which I need to see the files I have requested... John

This indicates that the axis has been registered as a digital on/off axis in your windows registry. To correct this, see the following FAQ entry: Note the FAQ entry is for saitek devices, for the devices this issue was original reported, but can happen to other devices. Just make sure that you use the correct VID and PID numbers/strings for your device. And (always) take a back-up of your registry before editing it. John

Thats strange...I will take a look when I get a chance... I think that it would overcomplicate things considerably to allow two parameters for controls. However, I could possibly allow for this in lua scripts using either ipc.control or possibly a new lua function to distinguish the two (e.g. ipc.control2). I will look into this also, when time permits. John

Not sure what I am supposed to do with that - looks like something to do with WidevieW. I have never used and don't know much about this software, so cannot help with that. I can only help with FSUIPC and WideFS. So you issue started when upgrading windows, not when upgrading FSUIPC7? Or did you upgrade both? Is WideClient connecting ok, or are you saying that you now gave a connectuin issue with WideClient? I am getting confused by this topic, and would like to see the files I requested (i.e. logs, inis and luas) to see what is happening.

But you have them calibrated in FSUIPC7. It was always possible to calibrate axes even when assigned elsewhere, but this functionality was disabled in 7.3.9 due to changes made by Asobo in the SDK. I updated to correct for this problem in 7.3.13. So it is working for you in 7.3.11 as the axes aren't being calibrated in FSUIPC7 in that version. To correct for this in the latest versiin, go into the axis assignment panel, go to the calibration tab, and then remove/reset the calibration for all the axes that you have assigned in MSFS. John

As I said, please read the documentation....

I don't understand why you would expect calculator code to except what is used in xml markup... Its certainly not a viable option, and I am not going to add a warning as I think that would be confusing. It accepts a calculator code string, and if you don't know what a calculator code string is, then you should check the MSFS/Asobo documentation to see what is allowed. I only document the additions to that MSFS allows, which is currently the use of $Param which when used will be substituted with the relevant parameter value, and the next release will also allow the @ character for the same purpose, as this is what the MF presets (for potentiometer input) use. Similarly, it is not up to me to document or explain RPN notation. John

If it is working to your liking, no other suggestions needed - apart from what I have said (i.e. try assigning directly to the rudder trim set axis). But if it is working ok, why not just stick to that, John

No idea - no one has reported this. I am not sure about in FS9 (that is now very old!), but looking at this in FSX & P3D (FSUIPC4-6), this offset holds the simvar SEA LEVEL PRESSURE, and is the barometric pressure at sea level and cannot be set (i.e. read-only), and it is not available in MSFS2020 / FSUIPC7. I suspect that this is the same in FSUIPC3, although that is no longer supported and I don't have the source files to check. Pete retired several years ago and will certainly not be willing to look into anything related to FS9 - I am pretty sure he doesn't even have this any more. I think you would be better off re-directing your question to avsim.com. Regards, John

Then FSUIPC7 will not be auto-started with MSFS, you will have to start it manually by double-clicking the FSUIPC7.exe in Windows Explorer, or create a shortcut to start it from your desktop. Yes you did, as you selected to create the desktop icon. The desktop icon shows the splash screen "preparing the flight cabin" and starts MSFS, not FSUIPC7. It is MSFS that starts FSUIPC7, but only if you select to install this component (auto-start). The "auto-start" component is to auto-start FSUIPC7 when MSFS is started (i.e. when MSFS is started, it is MSFS that starts FSUIPC7), so if you want that then you have to select the auto-start component when you install FSUIPC7. You seem confused about these things - I suggest that you read the provided documentation, starting with the Installation and Registration guide, which will tell you what the various components do. John

Log file looks ok and just shows its working in the DHC2. I thought your issue was with the T-28, but you dom'y seem to be providing any of the requested logs for this, or reporting on the other controls I have asked you to try. Btw. you should consider using aircraft substrings for your profile sections rather than the full aircraft name, with livery. Then you won't have to continually have to add your aircraft to a profile if not previously used. For example, you could change: to You also have "DHC2 Beaver N1117F Straight Floats" in your "Single Engine Amphib" profile (as well as your "MilViz DHC2" profile) which you probably want to remove. However, if you do use different profiles for different variants (which seems strange to me!), then you may need to use the full aircraft name, but using substrings is far easier. See the documentation for details in profile substring matching. John

You can only have one parameter to events with FSUIPC. The events with 2 parameters were recently introduced (in the simconnect SDK) and I have not looked into making these available with FSUIPC yet - and am not sure if I will do this at the moment. This may be possible using calculator code - although I am also not sure on how to set two parameters for an event with calc. code either. However, the MF preset for the pedestal lights in the C172 classic uses the following calculator code: @ 655.35 / 0 max 100 min (>K:LIGHT_POTENTIOMETER_6_SET) So this takes an axis value parameter, converts that to a percentage (between 0 and 100) and then uses the LIGHT_POTENTIOMETER_6_SET event. So you could try just using that control instead, i.e. ipc.control(66910, x) where x is the percentage. The glareshield is similar - that uses LIGHT_POTENTIOMETER_5_SET which is ipc.control(66909, x). John

Of course - that just means that its a 64-bit application, not a 32-bit one (x86). This is not related to the frameworks you are using. The .Net framework is usually used with C# (or maybe VB). I think it can ve used with C++ but I don't know anything about this. You should decide if you want to use .Net or not, and if so which other .Net framework you want to use for the GUI. Otherwise, just start with the Win32 API without ,Net. Yes - the ability to read and write to lvars using simconnect was recently added to the SDK, and works in the same way as you would read and write/update a simvar. But I have not used simconnect for lvars yet, as I implemented the WASM to be able to do this before this was made possible via SimConnect. Sorry, but this is not the place for simconnect programming or support, or basic windows GUI programming. There are many other resources available for this. I only have time to support the products I provide. John

There was a similar request for support for a MIDI output device called Loopedeck: Someone developed an application so that this can be used with FSUIPC. Maybe that can be adapted for the X-Touch mini? I have no plans to add direct support for such devices in FSUIPC. I don't know much about midi-output devices, and how they interact with the low-level windows HID interface, which is what FSUIPC uses for controllers. John

You have to decide which UI framework you want to use. You seem to have chosen WinForms, which is a .Net framework. I have never used .Net or any of its associated frameworks, so cannot really help you. Try google or StackOverflow to get you started on windows GUI programming, and try and get a basic (non-functional) GUI running first. You can then add the WAPI once you have an understanding of the GUI framework you are using, and then a simconnect connection if you also want to use that. The WASMClient just uses the old/original Win32 API with no additional framework layers, as does FSUIPC. John

The UninstallFSUIPC7.log file should tell you which version was uninstalled when you install a later version. Are these lua files running on the clients or server PC? I would like to see the FSUIPC7.log and FSUIPC7.ini files for when this is working and also when not working in the latest version, as well as the lua files. For now, jut set logging for Events and, if the lua plugins are running on the server also logging for Lua Plugins, otherwise set logging for IPC Writes. If the luas are running on the client PC, I will need to see the WideClient.log and WideClient.ini files. I don't think there is any lua plugin logging on WideClient - I may need to add some offset logging to WideClient, but I will need to see the files first to see what, if any, additional logging is required.

MSFS probably crashed before it even started FSUIPC7. That just shows that FSUIPC7 exited as MSFS was no longer available, i.e. had crashed. I can't really help with MSFS CTD issues - try the Asobo forums. You could try removing everything from your Community folder to see if MSFS starts ok then, and then add the Community folders back one-by-one to see if any of them are causing this issue. I have had similar issues with MSFS on several occasions, but each time they seem to resolve themself as I am investigating... Sorry I can't be of more help. John

No, only the latest version is ever provided and supported. What about the versions between 7.3.11 and 7.3.19? e.g. was it working in 7.3.12? Knowing the first version in which this stopped working would help narrow down the problem. Can you please provided more details on the actual issue - how are the external lights controlled? And please also attach a FSUIPC7.ini file and a FSUIPC7.log file generated with appropriate logging enabled (i.e. Buttons & Keys and Events). Please also review either the changes.txt file or the History document, which detail the changes between each version, to see if you can identify any possible changes that could cause this issue. If this proves difficult to track down, I may provide some early versions for you to test to try and track down the issue, but I don't like providing an earlier version because something has broken - it must be fixed in the latest version and the patch/update released in the next version. John

The 737 panel brightness presets use the PMDG SDK custom controls via the Rotor Brake control - and there are several of these. Can you let me know the exact names of the presets you are using please? You can use the right hand side in the axis assignment panel to send the inc/dec presets when you enter axis ranges, with up to 10 ranges, so you could set 5 ranges for inc, and 5 for dec, with the control/preset being sent on repeat in the outer ranges. That may work ok - so please try that first. It may also be possible to set this up as a proper axis by assigning the dial to an FSUIPC offset, and then having a lua script monitor that offset and send a custom control (instead of a Rotor Brake mouse control), but I am not 100% sure on this. If you let me know what presets you are currently using for the panel brightness inc/dec, I will see what offsets this changes, get the max/min values and see if I can create a lua script that then calibrates the axis offset value to this range and sends the custom control to change it. I won't have time to look into this for at least a couple of days though... John

Ok, thanks for the update. Please also note that you should consult the documentation for such issues before posting, if you didn't already, as 99.9% of registration issues are covered in the installation and registration guide. John

That does sound strange! Do you know what offsets the ATC map is using - possibly 0x0560 (Plane Latitude) and 0x0568 (Plane Longitude) or 0x6010 (GPS Position Lat) and 0x6018 (GPS Position Lon)? Whichever offsets it is using, try logging those offset using FSUIPC7's offset logging feature, and see how they change both with and without Spad.Next runnning. If Spad.Next is changing those for some reason, you will have to ask Spad.Next support about this - I don't think there is anything i can do if something else is changing the sim variables used... John

No - that section is automatically generated by FSUIPC, and should not be touched unless assigning your own "joyletters" What type of device is this X-Touch Mini controller? FSUIPC should recognise all HID joystick type devices. If its a HID / USB device but no a joystick type device. you will have to use lua. There is a demo script provided called HidDemo.lua which you can adapt and try. If its an XINPUT type device (as opposed to DirectInput) then you need to download and install a conversion utility called XInput Plus, available from https://www.play-old-pc-games.com/compatibility-tools/xinput-plus-tutorial/. With XINPUT devices, FSUIPC will only detect button presses when it has the focus.

You seem to be using the .Net framework. I have no experience with this and cannot help you with .Net. Also, if using .Net, you should use the dll instead of the lib. or Paul Henty;s client dll for .Net which includes a wrapper for the WAPI - see

You just add the header files to your project, and include the WASMIF.h file in the source files where you want to use the WAPI, and specify the WAPI include folder (as well as maybe the SimConnect one, if you are planning to use that) under the C/C++ Additional Incude Directories. Also add the FSUIPC_WAPI.lib to your project. Then you need to set the VC++ Directories -> Library Directories to add locations for both the WAPI and SimConnect libraries, and then add the following libraries to the Linker -> Input -> Additional Dependencies: FSUIPC_WAPI.lib;SimConnect.lib;Ws2_32.lib;Shlwapi.lib (and debug versions for the debug configuration. Take a look how the build for the WASMClient is set-up and try and follow that. I haven't got time to clone/download and look at your project, or to help with building standard apps, but if you can explain what your problem actually is maybe I can point you in the right direction:

As I said, the next available id is just allocated on lvar creation. so an lvar could have a different id in a subsequent run of MSFS, but it will not change in the same session, even if you switch aircraft and back again. This is actually a bit of a pain as it means that lvars are never cleared and so the number of available lvars is always increasing, even though many are of no use as they are for previous aircraft loaded. John