John Dowson

I don't know what the Honeycomb software does - best to just try it. Note that if you want to configure the Bravo using FSUIPC, there is a beta version available (of FSUIPC6 and FSUIPC7) that has native support for up to 128 buttons - the Bravo has several above the 32 button limit which won't be recognised natively by other versions of FSUIPC without using a lua script. It is available from here:

That cannot happen! Do you have controllers activated in P3D? If so, they can be automatically re-assigned, so best to disable controllers completely in P3D if assigning in FSUIPC. If you already have controllers disabled, please show me your FSUIPC ini file together with a log file.

The macro entries you see in the assignment drop-downs are there as they have been found in .mcro files in your FSUIPC installation folder. If they are not there, the files must have ben removed (or you have reached the limit if the number of macro files processed). Are the macro files still there? Also, please show me your FSUIPC6.ini.

You shouldn't move before uninstalling as then the location of your files does not match the registry location. If you want to change location, you should uninstall first, then move any remaining files/folders before re-installing. Ok, but you can change this to your preferred location, no? This does not match with what I'm seeing. So the default location is still wrong in the updated version I posted? Strange, I'll look into it when I get a chance, but its very minor. Because thats under you Documents folder. Its not a document, its an application.

No, it won't - FSUIPC does (next-to) nothing out-of-the-box! You have to configure your controllers/devices using the Assignments panels, to assign your axes (elevator, aileron, throttle, rudder, etc) and buttons, as well as any keys. Please see the provided documentation - for new Users, you should at least read the Installation and Registration manual, and also take a look at the User Guide and Advanced User Guide, to familiarize yourself with the various tools provided. Also, if using any devices with more than 32 buttons, you probably want to either the latest FSUIPC7 beta v7.1.0b, which has native support for up to 128 buttons. For this, please see You just need to configure your assignments, nothing else. John

D'accord - bonne chance!

Note also for trimming, there are a couple of lua scripts that may be of interest: and this one recently added:

No problem. Before you try the new version, please first uninstall and try with the current release but this time actually choose an installation folder to see if that works. Then, uninstall again and try the updated installer. The default installation location (for a clean install) should now be different (& hopefully correct) in this new version. However, it is still recommended to change this to a folder outside of your documents/add-on.xml folder.

Could you download and try this installer (please uninstall your current installation before running) and let me know what folder the installation defaults to: Install_FSUIPC6a.exe

Yes, here: This is because you have accepted the default location for the install. Admittedly, it should not default to this location, but you should change this anyway as this is your installation folder. Better to choose something like C:\FSUIPC6 or C:\P3Dv5 Add-ons\FSUIPC6 (although you can always select C:\Users\snorr\OneDrive\Dokumenter\FSUIPC6 of you wish, although not recommended). So, please re-install again, and this time actually select an installation folder rather than accepting the default. As the installation manual says: As I said, I will look into changing the default installation location.

Ok, but I also need to see your install log. Would be better if it was one from a clean install, so could you uninstall your current version by running the provided uninstaller (or using the windows apps control panel), then re-install FSUIPC (in the same folder). Then show me your new install log file. Doing it this way will perform a clean install (rather than taking the locations from the previous install).

ok, no problem. Cheers, John

May be as @jaxx indicated. It is certainly nothing FSUIPC7 does on its own....Can you show me you FSUIPC7.ini and .log files please.

It doesn't use hard-coded paths, it uses your registry to determine the location. Could your registry entries be incorrect? Could you show me your installation log file please. Sorry, that will never happen! I do not use .Net, and neither VisualBasic... Please show me your install log, and also check your registry for the HKCU entry for "SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders" Personal.

First, you posted in the FAQ sub-forum, where it explicitly states 'NOT for Support Requests'. I have moved your post for you this time, but please take care to post in the correct forum for support. I'm sorry - what does this mean? What 'listings'? Disappear from where? Can you please explain a bit more, and also attach your FSUIPC log and ini files (you don't even say which FS or version of FSUIPC you are using!).

No, this won't cause any issues. Your issue sounds like power management is enabled on your hubs, and windows is putting your devices to sleep. Check and disable power management on all your USB hubs/devices.

If you haven't purchased and/or aren't using WideFS, you can ignore that field during registration - its optional and only to be used if you have purchased a WideFS7 license.

Ah, ok. Glad its now working at least. Its really quite a simple change and shouldn't have caused so many issues, and I don't really understand why it did...

Was this test with your original or updated macro? Either way, it is now showing an error: And why is this now a right single click? And the rectangle ID (X40000087) is different from what was previously used (X4000018d) so it again looks like something else has changed....Have you changed the macro file again? I need to see your files each time they have changed otherwise I have no idea what is going on.... Also, I can see that you have various 757s assigned to the profile: A couple of things here... First, you are better off using substring matches, so you can re-write that as: But another issue is that the mouse macro rectangle IDs may change for different aircraft. They are generally the same if its just a different livery, but they may change between the 757-251 and 757-200. You need to check this and if the rectangles IDs are different, you need to create separate profiles.

This doesn't tell me anything. At a minimum, I need to see your FSUIPC7.ini and FSUIPC7.log files. Have you tried logging anything (e.g. Buttons & Switches + Events to start with) to see what is happening?

Many/most of the G1000 events are not working in MSFS. To control the G1000 with FSUIPC7, you need to install the MobiFlight WASM module and add the MF G1000 events to FSUIPC7 using event files. There are several posts in this forum that show you how to do this. FSUIPC provides access to the controls/events provided by the MSFS SDK / SimConnect. The MSFS documentation for this states: If any events aren't working, you can report to Asobo. [And note also that some events may work in some aircraft but not in others.]

For this issue, please see How did you configure this for each set-up? Does your rotary have 1 or 2 buttons in each direction? Or is ir a two-phase type rotary? If its the 2 button type, you can implement large/small increments/decrements on the different butons. If it has a single button in each direction, you could look into using the example rotaries.lua script - from the Lua Plug-Ins document: What do you mean by 'In FSX the radios stack run normaly, but with MSFS the radios not on'? You configure your radios in MSFS in the same (or similar) way as you do in FSX, although some of the controls/events may have changed. Have you tried turning the avionics on - there are several controls for this - from the controls list document: 66293 TOGGLE_AVIONICS_MASTER 66701 AVIONICS_MASTER_SET 67176 AVIONICS_MASTER_1_ON 67177 AVIONICS_MASTER_1_OFF 67178 AVIONICS_MASTER_2_ON 67179 AVIONICS_MASTER_2_OFF 68070 AVIONICS_MASTER_1_SET 68071 AVIONICS_MASTER_2_SET

I really don't understand this.... Are you saying that changing a macro used in one aircraft affects the way a different macro works in another aircraft? That really isn't possible.... And are you also saying that everything was working except for the issue you mentioned (button staying pushed-in) but with that minor change to one macro on one macro file, this stops all your macros working in that file and also other macros in different files used by different aircraft?

Please show me your updated ini and new log files. I need to see these after each change.

There was a bug in the WASM now corrected, Please try the following WASM module: fsuipc-lvar-module.zip (Also now released as 0.4.5)