John Dowson

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.

👍

Thanks for reporting back and glad you got it working. One thing - be careful of the offset(s) that you are using. 0x6748 is in the range 0x6700 - 6D5F which is documented as Reserved. 0x6700 - 67FF is reserved for Jean-Michael Biston's Airbus gauges. You should be ok if you don't use those, but it is generally better to choose an offset that is in an area that is documented as 'Free for general use'. Regards, John

I cannot help with this - either try asking on the Asobo SimWorks Studios forum or ask on the MobiFlight discord forum about those KODIAK_100_IGNITION_SWITCH_* presets. John

You should familiarise yourself with that resource as it is the source of the presets in the events.txt file, and can contain additional information on how to use a preset (e.g. some presets require an update to an MSFS aircraft xml config file to work properly). You can also download the latest preset file as new presets are being added, as well as existing ones updated, all the time. Why? You need to register (which you should) to use those features. 'Add Preset' allows you to add your own preset to share with others in the Community (check not already available before doing this!), and the Export button allows you to export the events.txt file, which you can use to replace the one in your FSUIPC7 installation folder. Ok, that makes sense and shows that the lvars are working. You are using the presets KODIAK_100_IGNITION_SWITCH_ON (and _OFF, _TOGGLE). Your log shows that these are being triggered: If you look at the code for those presets, they use the TURBINE_IGNITION_SWITCH_SET1 event, not the lvar. The description of these presets also says 'Intended for latching switch.'. If presets don't work, then you need to ask about this on the MobiFlight Discord server - they manage the community-driven effort for these presets. But, if you know that the lvars work, as you have tested them, why don't you just use the presets that use the lvars (Starter Switch Off/Lo/Hi) instead? Or add the lvars to offsets and assign to the appropriate offset control instead, as you do with the C310? Note that you are using an old version of FSUIPC7, v7.3.6. Please update to the latest version, v7.3.7. Only the latest version is supported. There is also a beta version available in the Announcements forum - v7.3.8b. I will release this in the coming days (hopefully, pending info I am waiting to receive from PMDG). John

The WASM functionality is not available until you have an aircraft loaded and ready-to-fly, i.e. they are not available when in the MSFS main menu. You may also need to Enable the WASM functionality, but in the latest version this should be enabled by default. John

Is fs_com.exe also in your FSUIPC7 installation folder? If so, then maybe that is an FSUIPC c# client that requires that dll. Otherwise, I cannot see why that is needed. No. *.hvar files are only needed to make hvars known to FSUIPC. You can still use hvars (via calculator code or presets) without using such files. But these days presets are far easier to use as they are directly available for assignment. You should not need to download that file - it comes and is installed by the FSUIPC7 installer (although there is no problem downloading and using the latest one from MobiFlight). That preset is an example of a simple one that activates a hvar. Not quite... Your A320.hvar file should) just contain a list of hvars. To activate them via calculator code, you need to use the correct syntax, as the example you gave shows, i.e. (>H:<name>). But the FBW A320 has been around a while now and most (if not all) hvars should be available for use via presets, so there really shouldn't be a need to create your own, but you can of course do this if you want to. Some folks like to copy the presets for the aircraft that they use from the events.txt file to a myevemts.txt file and then delete the events.txt file. This will reduce the presets available to the aircraft that you fly, reducing the number of presets available in the drop-downs and making them easier to find. John

Then you are not searching/looking correctly: How are you doing this? This indicates that changing the lvar has the desired affect. But if thats the case, I don't know what your issue is as you have also said that this is not working, so I'm confused now... Of course not! $Param can only be used in preset definitions, when the value will be substituted with the parameter you enter when you assign. If using calculator code directly, you need to put in the value. So, try 0 (>L:SWS_ENGINE_Switch_Starter_ThreeState_1) or 1 (>L:SWS_ENGINE_Switch_Starter_ThreeState_1) or 2 (>L:SWS_ENGINE_Switch_Starter_ThreeState_1) But there is no need if you have already confirmed that changing the lvar has the desired affect. If you need further assistance, please attach a relevant FSUIPC7.log file (i.e. with Event logging and Button & Key logging activated, and also Debug level logging activated for the WAPI, and showing your issue) together with your latest FSUIPC7.ini file. Also, maybe try reading the section on the WASM module and how to use presets, in the Advanced User guide. John

I don't need to see your aircraft.cfg file. Your ini file shows that you have no assignments at all in FSUIPC. You have the FBW event file loaded, but are not using any events. These days there is no need to use the FBW custom events, as it is easier to use either lvars/hvars directly, or calculator code using the provided presets. Why? That is only needed if you are developing your own C# WAPI client. Presume this was added by FSUIPC, no? You should not manually edit this section. I have no idea what fs_com.exe is or does. Is that where your assignments are? If so, then you need support for this software for your issues. I can only help if you are assigning in FSUIPC, which your ini shows that you are not.... I suggest that you try using/assigning-to the provided presets for the FBW A320. Use the MF HubHob site (link in my previous message) to search for the preset you need for the function that you want to implement, and then assign to that. I don't recommend using the FBW event file these days - and if you do it probably needs updatung as I created this quite a while ago now and it is probably not complete (I will not be updating this file as it is basically redundant now). John

What do you mean by this? What are your assignments for this? Have you tried logging to see what is happening? Have you tried using the available presets for the FBW A320 (see https://hubhop.mobiflight.com/presets/)? For further issues, I would need to see your FSUIPC7.ini so that I can see your assignments, and a log file generated with Event logging activated, as well as logging for Buttons & Keys, and preferably with Debug level logging activated in the WAPI. Your log indicates that your hvar file is loaded ok, so that is not an issue. John

Looking at the MF HubHop site, I see 3 presets available for the Kodiak 100 starter switch: Starter Switch Off, Starter Switch Lo, Starter Switch Hi. These use the same lvar that your preset is using - L:SWS_ENGINE_Switch_Starter_ThreeState_1. There are a few other things you can check: - when you change the lvar value, does that stick (i.e. if you red/log the value afterwards, does it have thee value that you have set)? - when you change the state of the starter switch un the UI, does the lvar value change? Are any other events logged? - try setting the lvar using the WASM->Addons-<Execute Calculator Code menu option to set/change the lvar value. If that works, then there is a problem in your assignments. However, remember FSUIPC only provides the mechanism for you to assign such calculator code to controllers and have it sent to the FS for action. If the calculator code/preset doesn't work, I cannot really help with this. especially i do not own the aircraft. I cannot possible know how all functions work for all aircraft... If FSUIPC7 is functioning correctly, i.e. the code you assigned is being sent to the FS/aircraft (which logging would tell you), and the calculator code (or whatever you are using) is not working, then the best place to ask about this is either on the Kodiak discord server (https://discord.com/invite/Ns7GkWW) or on the MobiFlight Discord server. In this post over on avsim, one user indicated he could get most things working using lvars/calculator code except for the ignition switch, while another user indicates that he got everything working with the help of MobiFlight: https://www.avsim.com/forums/topic/614394-sws-kodiak-100-control-problems John

The MSFS PMDG 737 is quite different to the P3D version, especially in terms of control. You will have to review and redo all/most of your assignments as well as offsets that you may use. If you are also using the specific FSUIPC offset area for the PMDG 737 then many if these offsets have also changed, and the offset area is not available in the current FSUIPC7 release, although it is available in the latest FSUIPC7 beta which you can download from here: The custom controls have also changed, and now use the Rotor Brake control. Information available here: There are also many presets available for the PMDG 737 which may be easier to use than the custom/Rotor Brake controls/events. Note that in the latest beta, presets are available for assignment by checking the 'Select for preset' checkbox. You can view/search for available presets using the MobiFlight HubHop site (https://hubhop.mobiflight.com/presets/). John

Check that you have controllers disabled in P3D - if you don't, P3D has a tendency to automatically assign your controllers. If controllers are disabled, it may be due to aircraft - some complex aircraft don't play well with FSUIPC calibration due to priority levels of the events. If this is the case, assign using 'Send to FS as normal axis' rather than 'direct to FSUIPC Calibration' and don't calibrate (i.e. remove/delete the current calibration settings). With the latest version if ProSim, it may be better to assign directly in ProSim rather than in FSUIPC. BTW, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. I have moved your post to the main support forum. John