John Dowson

Do not install FSUIPC in a windows protected folder such as under ProgramData, Program Files or Documents. Installing FSUIPC in such folders invariably creates issues. I have just updated to SU9 (v1.25.7.0) so I don't think that this can be an issue - unless it was present in the beta and has now been fixed. Thanks for the info though - quite a few people are experiencing this issue, and it may help them... John

I don't think this can be an issue, but I am still on 21H2 22000.651. I am updating to the latest update (KB5012643) now and will check... Why do you think that? The FSUIPC7 and the WASM module are two distinct components. When you start FSUIPC7 manually does it connect to the WASM (e.g. can you list lvars)? If so, the WASM has started with MSFS, it is just that MSFS is no longer starting FSUIPC7 from the EXE.xml. I have no idea why this is now happening for a few people. All I can suggest is that you go back to the old method of starting FSUIPC7 directly from the MSFS.bat file. See the link I posted above on how to do this. John

First, you posted in the wrong sub-forum. Please take care to post in the correct forum. What aircraft are you using? If using the FBW A320, you need to use an lvar and spoof the offset to the lvar value, as we already discussed in this thread: If its not the A320, but some other aircraft that is not using the standard SDK simvar, then you will need to determine what is usedm get that into an offset and spoof the offset again. Is this any different from last time this was reported?

This post is old now - I have only just seen this as it was posted in the wrong sub-forum. Hvars are only visible to FSUIPC if made known via *.hvar files. Please see the Advanced User guide. John

Yes - select a different folder for installation. The Documents\Prepar3D v5 Add-ons\FSUIPC6 folder should only be used for the add-on.xml file and not as the installation folder. This can cause issues with Windows, especially in windows 11. So, re-run the installer and select a different installation location, not under any windows protected folders (such as Documents or Program Files). You can skip registration and copy/move across your FSUIPC6.key and FSUIPC6.ini files after installation, as wel as your *.lua diles and any *.mcro & *.dll files that you may use. If you still get the same problem, please show me your FSUIPC6.ini file. John

Your post/questions are slightly confused....Please be aware of the difference between hvars, presets and custom controls/events. hvar: is a simulator HTML variable. These can be made know to FSUIPC7 via *.havr files. Once made known to FSUIPC7, they can be used in macros and in lua scripts. They never appear in drop-down menus. They can also be activated by (or used in) calculator code, by standard controls or via custom controls. They do not need to be made known to FSUIPC7 (via *.hvar files) for such use. preset: a preset is just a name assigned to a calculator code string. These are made known to FSUIPC7 via the files events.txt and myevents.txt and all entries will be available for assignment, prefixed by 'Preset: ' in the controls drop-down menus (as in your picture). Custom events/controls: these are additional events/controls whose implementation is provided by an add-on (usually either an aircraft itself, or a WASM module such as the MobiFlight Event module). These are made known to FSUIPC7 via *.evt files, and will be available for assignments, prefixed by ':' in the controls drop-down menus (and therefore located at the top of these menus). Also note that these are only added once a connection is made to MSFS2020. Also, the total number of such events is controlled by the MaxNumberOfCustomEvents ini parameter, which has a default value of 1024. What have you inserted in the FSUIPC7.ini? You should not insert any files in the ini - the file sections (such as [EventFiles]) are managed by FSUIPC7 and should not be manually adjusted as this can cause issues. Hvars never appear in drop-downs - only presets and custom events. Are you referring to the following custom events: A32NX.FCU_HDG_PUSH A32NX.FCU_HDG_PULL ? If so, then these are located in the event file EventFiles\flybywire-aircraft-a320-neo.evt (under your FSUIPC7 installation folder). To use these, move that file up one folder level to the main FSUIPC7 installation folder. They will then be available for assignment (once FSUIPC7 is connected to MSFS) as ':A32NX. FCU HDG PUSH' and ':A32NX. FCU HDG PULL'. However, almost all events can be used as presets now. You can use the following presets: HDG_Pull#(>K:A32NX.FCU_HDG_PULL) HDG_Push#(>K:A32NX.FCU_HDG_PUSH) HDG_Push_Pull_Toggle#(A:AUTOPILOT HEADING SLOT INDEX, Number) 1 == if{ (>K:A32NX.FCU_HDG_PUSH) } els{ (>K:A32NX.FCU_HDG_PULL) } which will be listed as 'Preset: HDG PULL', 'Preset: HDG PUSH' and 'Preset: HDG PUSH PULL TOGGLE'. John

What happens when you run the uninstaller? If it produces an UninstallFSUIPC6.log file, then please show/attach that. Have you tried re-installing FSUIPC6? Download and run the latest installer - this will first try and uninstall FSUIPC6 (using the uninstaller). Do that and show me the installation log if there are any issues. Also not that FSUIPC6 is an embedded dll with P3Dv4/5, so you need P3D running. So after installing, run P3D and see if FSUIPC is running. John

Ok - so it was auto-starting...when it starts you should see the FSUIPC7 splash screen and then it is iconised to your system tray. Alt+F is the (default) hot-key which opens the FSUIPC7 main window - you can also do this from the system tray icon by double-clicking or using the left-click context menu. Please see the provided documentation (which will be installed under your Windows Documents folder) - as well as the README.txt which is only available in the downloaded zip file. John

@Chad P Did you resolve your issue? Just took a look at the FBW A320 (dev version) and assigning 'Direct to FSUIPC Calibration' to LeftBrake and RightBrake (and calibrating) seems to work as expected. I also tried with the experimental version, and the same assignments also work in that version. John

You should have received an email with your registration details, and they are also available under "Your Orders" and "Purchase History" of your SimMarket account. I will also PM then to you now... John

What do you mean by this? Did you follow the instructions in the README.txt for this issue? If not, please do that. And see this post (and onwards) as this issue has already been reported: So, check your EXE.xml. If that is correct and FSUIPC7 isn't starting, then you will have to revert to the old way of starting FSUIPC7, which is via the MSFS.bat file. Instructions on how to do this are given in that topic (above). John

If you click 'Yes' to run the software, does FSX run ok with FSUIPC also running or does it crash? Does the window display again the next time you run FSX? I can't really add more to what has already been said on this issue - please see the following: John

Flight saving/loading seems rather flakey - sometimes it seems to work, other times not, and I have also experienced some CTDs when trying to load a flight. I will check further next week - some of the flt files I am trying to load are probably created by older versions of the SDK, which may no longer be valid. However, as FSUIPC just calls the MSFS SDK functions to load & save flights, there isn't much I can do about this, except report any issues to Asobo. I think this may also depend on your MSFS settings. For example, I'm not sure how live weather (and AI) affect flight loading. John

What do you mean? Copy/paste your key details - all 3 parts (Name, address, key) - from your SimMarket purchase email or account. If you still have issues, let me know your order number (do NOT post your key details) and I will check them here. Almost every time this is reported, it is due to user error... John

I have only just seen this as you posted in the wrong sub-forum. I have moved your post to the correct place. Why do you have 3 different key codes? Please see your SimMarket account for your FSUIPC4 registration details. No success installing or in registering? If you have problems with installing, please show me your installation log file. For registration issues, check you are using the correct details for name, address and key (all 3 fields) as in your SimMarket account. If using a new PC, also check that you have the required VC++ redistributables installed - download and install the latest combined package from Microsoft if in doubt. John

Ah. Sorry, missed this. I don't know where you got them from, but they certainly don't look correct. With MSFS2020, many settings are aircraft specific, don't blindly copy settings for other aircraft and Flight Simulator software.... John

Latest version is v7.3.3. Please update. What aircraft are you using? MSFS aircraft, especially add-ons and more complex aircraft, do not use standard controls and you need to look into other methods of control, such as lvars, hvars, calculator code and presets (which also use calculator code). A could resource to check is the MobiFlight HubHop page: https://hubhop.mobiflight.com/#/list. Your assignments don't make sense. An axis needs to be assigned first to an axis control using the left hand side of the axis assignment panel. The right hand side of the axis assignment will only trigger a control when the axis moves in or out of the range specified. Inc/dec controls are for use on buttons (or a rotary control that fires one or two buttons in each direction) and shouldn't really be used for axis assignments. At the moment you can't assign an axis directly to the heading axis controls Heading Bug Set or AP Panel Heading Set. I could allow this (I will check this), but for now If you wand to use an axis to set the heading, you would need to send the axis value to an offset (most probably 0x07CC or 0x07CE). You (probably) would need to calibrate the axis value to the range accepted/used by the offset as well, using the facility Additional parameters to scale input axis values (see p41 of Advanced User guide). I suggest you take a look at the documentation (user guide and advanced user guide) and maybe also search for similar posts in this forum. If you require further assistance, please state the aircraft (including any mod) that you are using. Also, please attach your FSUIPC7.ini file so that I can see your assignments, rather than pictures. John

It shouldn't be painful...if you just download and run the installer and accept the defaults, it should update without issues and only takes a minute.... John

This has been corrected in the latest version, v7.3.3. Please update. John

Usually if you accept to trust and run the dll it should load automatically and subsequent runs. However, if it doesn't for some reason, please see the following FAQ entry: John

There is a hvar file for the B747 included under the HvarFiles folder if your FSUIPC7 installation folder. This was generated quite some time ago now so it may not contain all available hvars, but you could use that as a starting poinr and add any that you use that are currently missing. Yes. There is currently a MobiFlight request to provide access to all sych variables - you should vote for this: https://forums.flightsimulator.com/t/enhanced-api-to-access-all-aircraft-state-and-trigger-all-cockpit-functions/454608 You can use offset 0x3110 to send any control, including custom controls and presets. Add-on control 1070 (Key Press and Release), 1071 (Key Press/Hold) and 1072 (Key Release) can be used to send keypresses using this offset. You can also set lvars, activate hvars and call presets using offset 0x7C50. Offset 0x3200 can also be used to send key presses. Also, check the MoviFlight preset lust for the B747 if you haven't done this already (https://hubhop.mobiflight.com/#/list). John

Yes, this is now quite usual with MSFS aircraft, especially airliners and the FBW A320... The logging shows that it is using the standard Axis Left/Right Brake Set control, so that should be working... However, the parameter logged for that control doesn't vary much - just 12840 and 12839, and both always the same, which us unusual - very difficult to apply the same pressure to each, even via the UI... I'll take a look later (or more probably tomorrow now), but in the stable or dev version of the FBW A320. I am not going to switch to the experimental - and I suggest you always try with the stable or dev if having problems with the experimental. One thing you could also try is to do the same test, but using your toe brakes. Use each one individually through its full range, and see what parameter is logged as you do this. You can report what you see (no need to attach the log) if it looks strange, and maybe also attach your FSUIPC7.ini so I can see your configuration. John

Which aircraft are you using? If its a default one or an add-on that I have then I can check here for you. Otherwise, you can try logging axis controls, operate the toe brakes in the UI and see if anything is logged in the FSUIPC7 console window - if you open the console window you can see what is logged as you activate the toe brakes in real-time. John

If you add the lvars to offsets, you could use the Offset monitoring facility to log the lvar changes (to the console or MSFS title bar). As the simconnect text display facility seems to be permanently broken, I am considering changing this to allow logging to be displayed in a wnd window. I could also look into adding specific lvar logging - I will add this to my list of new features to look into. You can use hvars via executing calculator code or via presets (which are also executed as calculator code), but such hvars are not known to FSUIPC7. The only way to make them known, and so have them listed, is via the *.hvar files. But there is no need to do this, except if you want to be able to list them or use them via macros or the lua ipc hvar functions. John

I will look into adding a 'Force Main Window to Top' option to see if this helps, as you can do with the logging console window. John