John Dowson

Oh - and here is the documentation: FSUIPC7-Docs.zip Unzip that somewhere, usually it would go under your Windows Documents folder. I have removed the User Guide from that zip file as it made the file to large to attach - I will send that separately....

Ok, at least you have it now working. Attached in this WASM module - save this to your MSFS Community folder and extract the files (then delete the zip), and you will have access to the facilities provided by the WASM (access to lvars, hvars and calculator code). I have also attached the events.txt file - save this to your FSUIPC7 installation folder and this will give toy access to the MobiFlight presets. Cheers, John fsuipc-lvar-module.zip events.txt

Can you please show me/attach your InstallFSUIPC7.log file. Are you using a steam or MS Store version of MSFS? Do you know the location of your UserCfg.opt file?

Auto-connect and auto-start are two completely different things. You should have auto-connect set, but I would like you to try the auto-start, to see if MSFS can start FSUIPC when it is started. This will prevent you from having to manually start it from the command line. I thought that you can still not tun the installer at all, even via the command prompt, and that you can only start FSUIPC via the command prompt. As you see the Assignments menu, your key file is correct and you are running a registered version. All registered facilities will be available. I still think you will be better off trying to determine why the installer cannot run, and why you cannot start FSUIPC7 via windows Explorer. But I cannot help you any further with this. If you can confirm that the auto-start works, you can install the WASM, documentation, and other components manually. This should give you a full working FSUIPC installation which you can use, while you try and figure out the issue preventing the installer running.

But your initial post said 'FSUIPC allows imaginary buttons to be used,...' and also 'I started using imaginary joystick 17' so I assumed that you were talking about virtual buttons. And also note that only joysticks 0-15 are supported, not 17. Yes, that is for the InitialButton directive. Also page numbers are fixed. If you are seeing different page numbers on different PCs, then you are looking at different versions of the document. Yes - these are parameters for controls, and nothing to do with offsets. Just because the parameter to control a button flag is 3871, that does not mean that offset 3871 is available to control the same button flag. Do not confuse parameters with offsets. Of course, a parameter CAN be an offset address, but only if/when stated. No! You were interested in seeing the status of the button flag for joystick 13, button 0. 3328 just happens to be the parameter used when you want to toggle/set/clear the flag for this button. It has nothing to do with offsets. The state of button flags are generally not held in offsets. Well, if that was your issue you should have posted that earlier. Looks like at least that 2nd 'F+13' should be 'F-13', similar to the second working assignments, where you have also changed to use joystick 14 for some reason. But if its now working, no point in revisiting the assignments that are working. You should be able to see the difference between the two and figure out why it wasn't previously working...

Your lua scripts are not running. You need to have these running, normally started from an [Auto] section - add this to your FSUIPC7.ini: You only need to change the device number if you have multiple devices with the same Vendor and Product ids. As your product ids are unique, you do not need to change these, leave them as (or put them back to) 0. Note also that you have assignments to missing devices: This is usually caused by a GUID change for the device. To correct this, you should review all your assignments to these device letters (E and F) and either remove them or update the letter to the now correct device letter, id you can determine what that should be. John

What A320 are you using - Asobo, Fenix or FBW (dev/stable/experimental)? You are updating an lvar ( ipc.writeLvar) and then reading its value directly afterwards (ipc.readLvar). Due to the time it takes to update an lvar and the asynchronous nature of the request/communication (a request is sent to update the lvar, and later the updated lvar value is passed back to FSUIPC), you will be reading the original value of the lvar and not the new value, i.e. it will be the same as old_para. To prevent this, you can add a delay between the write and read (e.g. ipc.sleep(200)), or just assume that the update/write request has succeeded and just set 'new_param = ipcPARAM'. But isn't it the case that whatever value is set, the previous value must have been either 10 higher or 10 lower? So, if the current ipcPARAM value is 0, the previous knob position must have been 10, if the current ipcPARAM value is 10, the previous knob position must have been either 0 or 20, etc. So You only need to either increment or decrement to change the knob one position at a time.

It is what it is - a programming API. You scale each RGB value to 16, not divide. This is because the wnd library was initially in WideClient only. It was later incorporated into FSUIPC. I would like users to at least consult the documentation before posting, and at least try for themselves. FSUIPC contains a lot of features, and I know there is a lot of documentation and it can be difficult to find and understand relevant sections, and the documentation can certainly do with an update/overhaul in many areas. Many support questions are covered by the documentation, but I always try and explain and point to the relevant section of the documentation. If the documentation is not clear, I will update it to try and make it more understandable, as I would like to try and reduce the time I am spending on support, so I can spend more time on improving the functionality and also improving the documentation.

I do not understand why you are trying the EXACT same thing as before, but for a different offset. Offset 4532 is in this area: You CAN NOT invent an offset for your own use (although you can use offsets marked as 'free for general use' for your own purposes). As I have already said, virtual joystick button states are held in offsets 0x3340: Please read and understand that. Also note that it only holds space for 9 joysticks, 32 buttons each. You cannot use (imaginary) joystick 17, that is not supported. Not sure what this means ('280,10''?), but if you want to have different functions in a button depending on the state if another button, use compound button controls - see the Advanced User guide for details. John

Yes you can, but not using that offset- see offset 0x29F0 which provides a facility to set/clear/toggle virtual button flags. The flags themselves are stored from offset 0x3340. By writing to offset 0x3328, you will be writing to this: You should always consult the FSUIPC Offset Status document before reading/writing to offsets. John

And the installer still doesn't work after this change (and a reboot)? Do you still have to run it twice before it starts? Can FSYUPC7 be auto-started with MSFS? Can you try setting this up - you will have to manually create and entry in the MSFS EXE.xml file - instructions can be found here: It will be running as a background process when in the task bar. Me too.... Did you manage to create your key file and get access to the registered/licensed facilities? If so, and FSUIPC7 is auto-started ok by MSFS, we can manually istall the WASM and Docuementation, as well as any other components you may want (SDK, WebSocketServer, Event files, etc). John

Anything that relies on text (or menu) display using the SimConnect_Text function will not be functioning correctly, including lua plugins and offset controls. From the README.txt: Yes, as its says in the README.txt, and as I indicated in my previous comment: As it says in the documentation: So 0xF00 would be red, 0x0F00 would be green, and 0x00F would be blue, and combine different quantities of each colour for other colours. What is WideConnect? Do you mean WideClient? As I said, there is no reason to use WideClient on a server PC UNLESS you want to use the button-screen facilities. Just use FSUIPC to run your lua scripts. No - and I don't understand why you would want to do this, and why you are using WideClient. Why don't you just use the wnd facilites in lua script on the server? You should be able to exchange the wnd window reference between scripts running on the sane server (process), but not between WideClient-controlled lua scripts and FSUIPC-controlled lua scripts. You can use ipc.get/ipc.set to exchange data between client/server lua scripts. but with restrictions, and should be used sparingly. Handles, such as wnd handles, can be passed but they will not be useable as a handle created on a client will have no meanung on the server, and vica-versa. I would just use the logging facilities for this, either via ipc.log or using FSUIPC's (offset) logging facilities. And you can also keep the logging console open so that you can see what is being logged in real-time. John

Then why post in this topic? All licenses are purchased from SimMarket. Your license/key details will be in your SimMarket purchase email, and also available in your SimMarket account. John

I do have some ideas to replicate the SimConnect_Text function in the WASM (using jsp) and switch to using this. There is a lot of new APIs I need to understand before I can do this, and need quite a bit of time to study and play around with this. Maybe I will have chance one day, when I get less support questions. It is VERY difficult to get any development done as I am spending 90% of my time on support at the moment..... John

No, and they never will be - they have been deprecated by Asobo. You need to use the Wnd library to display text. None of this will work (reliably) as the SimConnect_Text function is broken. Use the Wnd library for the time being. You can run WideClient on the server, but no point if just for text display purposes as these are broken. The only possible reason that you would want to tun WideClient in the server would be to use the button page facilities. No - no point.

Already done. Did you check this both in the Local Security Policy and in the Registry, as shown in that link I provided? If not, please do so, as there is obviously something wrong somewhere... This makes no sense - why should it work the first time and not the second? What do you see when you run it the first time? What happens when you double-click the FSUIPC7.exe in Windows Explorer? Have you checked that FSUIPC7 is not sitting in your system tray (NOT the task bar)? You should not see the FSUIPC7 main window until you open it from the task bar (or use Alt+F). Then you haven't created the FSUIPC7.key file in the correct format or with the correct file name, Please try again - and don't forget the first line MUST be '[User]'. The WASM also needs to be installed. No point in doing this until you can actually run FSUIPC7 correctly, and also it would be better to get the installer working rather than installing manually. Do you see the UAC permissions box when installing other utilities (that need admin rights to install)? Does your windows account have admin privileges? If you go to your Account info, does it say you are an Administrator? If not, you cannot elevate to admin privileges.

Why did you post your key details? Posting key details in a public forum invalidates your license, as anyone can then use these. NEVER post your key details or share them with anyone. If you do this again I will invalidate your license.

Maybe UAC has been disabled on your PC? See the following article on how to enable: https://www.tenforums.com/tutorials/112488-enable-disable-user-account-control-uac-windows.html

Ok, then this is the problem, i.e. there are issues with your UAC configuration. Can you take a look at the security tab of the installer (in the properties window). This is what mine looks like: It is probably already running. When you run FSUIPC7, a splash screen is displayed, and then it is iconised to your system tray. You can open it from there, or use the (default) hot-key combination of Alt+F to open/close the FSUIPC7 main window.

You only need a FSUIPC7 key if you want to use the registered facilities (e.g. assignments). If you are just using FSUIPC7 to support 3rd party programs, you probably don't need a key. FSUIPC7 runs without registration, but you will not have access to the additional features provided by registration. If you want to try these features, a trial key is available - you need to request this by posting in the following topic: WideFS is a separate product, and is only used if you want to run FSUIPC 3rd party apps on a separate client PC (i.e. on another PC in your home network that is not running MSFS). You can also run FSUIPC7 on a client PC, so this can be used instead of WideFS/WideClient for most use cases. If you decide that you want to purchase a license for FSUIPC7 (and/or WideFS), these are available from SimMarket. John

👍

Can you make sure that you are not running the installer from a windows protected folder. Also please try running the installer from a command prompt window - are any errors reported when doing this? Can you also try running FSUIPC7 to see if it can run correctly. Create a folder (e.g. C:\FSUIPC7) and download the latest FSUIPC7.exe from Then just try running it to see if it runs. If so, exit and manually create a FSUIPC7.key file in the same folder - details on the format of this file can be found in the Installing and Registering FSUIPC7.pdf document (which is included in the installer zip file). Then run FSUIPC7 again and see if you have access to the registered facilities (e.g. assignments). If that works ok, I can provide you with the additional files you need (WASM and Documentation).

I have updated to 23H2 now and the installer is working as expected here (although I am now having some strange issues with my displays...). Ok, so it is the installer framework that is causing this - FSUIPC6 and FSUIPC7 use the same framework, but not FSUIPC5. If this is a new PC, you will need to install the latest combined (2015, 2017, 2019 & 2022) VC++ redistributables, available from https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#visual-studio-2015-2017-2019-and-2022. Install both x64 and x86 versions. Can you please install these and try again.

Yes, and you (most probably) loaded a different variant, so it did not match that full aircraft name in your profile, so the profile wasn't loaded and therefore you didn't have your assignments. You have no general axis assignments, and only 3 general button assignments, so you would have had no (or hardly any) assignments when you load any variant that wasn't the one in your profile. That is how profiles work....

Change this: to this: You also have various profile for the PMDG 737: You really don't need so many profiles for the same aircraft, different variants. and any new variant you try will need another profile to be created, or to be added to an existing one. You just need one profile: or possibly two if you have different assignments for the 700 variant vs 800, but usually not necessary. Choose one profile (not necessarily the 'PMDG 737 FSUIPC7' one - you should choose the one which is most complete), and try using that for all variants. Of course, you can use separate profiles if you so wish, but no need if it is just a livery change. Your profile aircraft name should be a substring of the actual aircraft name that catches all variants of the aircraft you want to use with that profile. Please see the User guide on how to use profiles. John