John Dowson

The latest and only supported version of FSUIPC4 is v4.977 - please update. What changed? If FSUIPC4 is sending a keystroke, you need to check the key assignments in FSX-SE to see what that keystroke is assigned to - maybe that has changed? I am not familiar with this control, but looking at the documentation for this it says: Used in conjunction with "selected" parameters to increase their value (e.g., radio frequency) So it looks like you need to use something else to select the parameter that you want to increase before using this control. John

As @Moderate Chophas indicated these lvars and presets are working, there must be something else going on. Check that you are using the latest version of FSUIPC7, which is v7.3.7 - if not update first. Also check the WASM module is enabled. If that is the case and it still isn't working, show me your FSUIPC7.log and FSUIPC7.ini files. preferably with Debug level logging activated on the WAPI, as well as Event and Button & Key logging activated. John

This shouldn't be an issue - there should be no problem mixing assignments between FSUIPC and MSFS or other software. But why don't you just try it - there is a trial license available in a post at the top of this sub-forum. It has currently expired, but I will generate a new one later today. John

No idea - hard to tell with so little information. Try activating logging for Buttons & Keys as well as Events, and check the preset is being sent when you press the button. You can also try executing the calculator code for the preset using the Add-ons->WASM->Execute Calculator Code... menu item to see if the preset is working. If it is, then there is something wrong somewhere - you can attach your log and ini files and I will take a look. If the calculator code for the preset isn't working, I can't help with that - try the MobiFlight discord server. John

Try reading the manuals...especially the section on the WASM in the Advanced User guide. Your FSUIPC7.log (and FSUIPC7.ini) file is in your FSUIPC7 installation folder. You should review the installation nd registration guide for an overview of what is installed and where. John

Ok - so that shows that the lvar L:SWS_ENGINE_Switch_Ignition_1 is being held in offset 0x66C6, and you have a button assigned to set the lvar value to 1 on press and 0 on release (as I suspected). Your macro file isn't being used. In fact, it can't be - as well as the contents being invalid, the filename contains more than 16 characters. From the Advanced User Guide, section on macro files: But if this is working, then its not an issue. Just delete that duff macro file. John

As I said: Remember to also set Debug level logging in the WAPI (instructions above). John

Hi Matt, In the latest version, the WASM should be enabled by default. This is usually due to timing, i.e. the information on lvars has not yet been received by FSUIPC. This occurs LvarScanDelay (a WASM ini parameter) seconds after the aircraft is loaded, and defaults to 5 seconds but should be increased (to 45-60 seconds) if using complex aircraft. No point doing this. Better to disconnect from MSFS and then re-connect. But, you really shouldn't need to do this. There is a possible problem that can occur if/when using multiple WAPI/WASM clients. This has been fixed in the latest beta release, so if your users are using multiple WASM clients then they should update to this version, available here: There really is no point re-installing FSUIPC7 for this issue. If this problem persists, then you should activate Debug level logging in the WAPI, by adding the following to the [WAPI] section of the FSUIPC7.ini file: LogLevel=Debug This should then show the data being received in the FSUIPC7.log file, and the WASM menu items should be enabled once this/these lines are logged: If the problem persists, show me the log file and I can take a look. You can also activate Debug level logging in the WASM (see the Advanced User guide) and attach both the FSUIPC7.log and FSUIPC_WASM.log files. John

👍😎

You need to opt-out of the beta program in steam (you must have opted-in, no?). To do this: You can opt out of the beta at any time by doing the following: • Open Steam • Open the Library tab • Right click on Microsoft Flight Simulator X: Steam Edition [g2610build] • Select Properties from the menu • Select the Beta tab at the top • From the drop down menu, select NONE - Opt out of all beta programs • FSX: Steam Edition will now update back to the LIVE version of the software • In the Steam Library, your game will be listed as Microsoft Flight Simulator X: Steam Edition No. FSUIPC4 was closed for new development many years ago. We provide a version that works with the beta, but with reduced functionality (e.g. no mouse macros). There will be no further updates. There is really no need to use this beta - this is the description: i.e. it was only released to allow more data to be collected for the development of MSFS2020. John

Your log only shows two offset control assignments on a button press and a release (same button), most probably setting the value of the lvar L:SWS_ENGINE_Switch_Ignition_1 (to 1 then 0), although I can't tell as I haven't seen your latest ini file: I see no use of that macro file. John

You are using the latest FSX-SE beta. I am surprised that FSUIPC4 is working at all! Please see that post I previously referenced as you are using the latest beta. Mouse macros will not work in this version. If you want to use Mouse macros, you should opt-out of the beta and revert to the pre-beta release (62615)))). John

I am very surprised that that macro is working...from the documentation: Also, TURBINE_IGNITION_SWITCH_SET1 is an event (k-type variable) and not an lvar Not 100% sure what that macro is actually doing due to these problems, but I suspect that, if anything, it will set the lvar L:SWS_ENGINE_Switch_Ignition_1 to 1 and then 0 (logging would tell). John

I'm pretty sure I've tested the auto-save with that aircraft before (but a while ago now) and I think it was working for me, more or less. Not sure though, so I will check again next week. There are plenty of SDK updates planned by Asobo for the SU10/SU11 releases so hopefully this will be fixed in a future update. John

The FSUIPC auto-save function relies on functions provided by the SDK to save and load flights. If it isn't functioning correctly, there isn't much I can do. What aircraft are you using? If you let me know (and I have that aircraft), I can take a look, but I don't think I can do anything. Looking at the SDK documentation for the save flight function, it is still documented as NOTE: The current status of this function is NO ERROR, NO RESPONSE, which indicates that this function is still not fully working. This should be fixed by Asobo in a future release. John

It is labeled MSFS as this is an additional feature that displays a splash screen while MSFS is starting. It has been like this for a long time (over a year!). Please read the Installation and Registration guide which explains what is installed and where. What do you mean by this? Is FSUIPC7 running - do you see the FSUIPC7 splash screen when it is started? If so, it should be sitting in your system tray from where you can open the main window. You can also open the main window using the (default) hot key combination Alt+F. Also the WASM should be enabled by default in the latest version. John

As I said, please show me your FSUIPC4 Install.log file. There is no other version, but (as I also said), you need FSX with at least SP1 installed. Mouse macros will also not be available if using the latest FSX beta, build 63003 - see John

No - the installer will request admin privileges when you run it which you need to accept. John

That is very strange...I don't understand how that button can't be present... Can you please download the latest FSUIPC4 installer again and re-install and check again. If not there, please show me your installation log file. Note that, as the manual states, you need at least SP1 installed for the macro creation facilities to be available - check that you have that installed. John

That EXE.xml looks fine. If I replace my EXE.xml with yours, I can also run the installer without issues, so I'm afraid that I do not know what your issue is. You can either add the FSUIPC7 <Launch.Addon> section to your existing EXE.xml file, or copy the <Launch.Addon> sections from your existing one to the new one that the installer creates. It should be straightforward, and that post in the FAQ I referenced in my previous comment should help you if you have issues. John

Ok. Do you have an MSFS EXE.xml file? this will be located in one of the following locations: Steam installations: %APPDATA%\Microsoft Flight Simulator\EXE.xml MS Store installations: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\EXE.xml If so, please show me/attach that file. You can also rename that file (e.g. EXE.xml.old) and re-run the installer with the auto-start component selected and see if that works. If there is another application that needs to be auto-started, you can add that back in afterwards. I would like to see this file as it seems to be causing the installer to crash, and if I can determine this I can update the installer to handle this situation. Please see this FAQ entry in the FSUIPC7 auto-start component: John

That is your FSUIPC7 log file - I need to see the installer log file - InstallFSUIPC7.log, if one was created... Ok, then the installer crashed and you will not have an installation log file. If you have an older InstallFSUIPC7.log file in your FSUIPC7 installation folder, then please show me that. There seems to be an issue installing one (or more) of the components. Try re-installing again, but without the auto-start component. If that succeeds, show me your installation log together with your current MSFS EXE.xml file. If that fails, try installing without the WASM module (but with auto-start) to see if that succeeds, and if so show me your installation log. If both those fail, try installing without any documentation. You need to determine which component is crashing the installer. Also, if you are running any anti-virus software, try disabling that while installing, and/or check the antivirus logs to see if that is preventing the installation. Some antivirus software can (incorrectly) prevent FSUIPC from being installed. John

Can you explain what happened? Was an InstallFSUIPC7.log file created? If so, please show it to me. Also, make sure they you unzipped the installer before running and did not run it from withing the zip file itself. John

Look again - I cannot see how there cannot be a Create Mouse Macro button in both the Key Presses tab (top right) and in the Buttons + Switches tab (bottom left).. Like like this is missing from the screenshot of the Buttons + Switches tab in the User guide though... John P.S. I will delete your similar post in the FAQ section.

👍