John Dowson

No, macros are not limited to mouse macros. That should work - if it isn't, then please attach the relevant files -the macro file, your .ini file, and your .log file, with Button + Event logging activated. Note that to have multiple assignments in a single button, you can also overload your assignments by editing the ini file. So, for example, to have 'landing lights off' on your controller with id3 on button 23 (for example), you could have: John

Yes, I have the same yoke. There still seems to be an issue though - your TWCS Throttle and T.16000M Joystick both have the same joystick Id. You don't seem to have any assignments to either of those devices at the moment but you would have issues if trying to assign to those devices. To correct this, first try changing your [JoyNames] section in your FSUIPC4.ini from: to Do this when FSX/FSUIPC4 are not running, then start FSX and see if both of those devices are recognised as separate devices. If not, show me your update .log, .ini and .JoyScan.csv files. John

Did you install the FSX service packs - SP1 (or SP1A) and SP2? Yiu need to have at least SP1/SP1A installed.

Did you install any saitek drivers or software? Your X-56 throttle and stick have the same PID, which is usually caused by installing saitek software and/or drivers. If so, can you disconnect your devices, uninstall any saitek drivers or software, reboot then reconnect and let windows install the default windows drivers. Then show me your updated FSUIPC7.log, .ini and .JoyScan.csv files. If they are still showing with the same PID after that, we will need to clean your registry.

The ini file you attached shows no assignments what so ever....have you ever made any assignments in FSUIPC? Your log file again shows continual scanning of your USB devices. This is usually a sign of a bad connection, an under-powered hub, or a faulty usb port/hub. Try changing/switching usb ports/hubs for your devices, and check all your connections and cables. And check the power settings in the windows device manager - you really need to turn off power management for all your USB hubs. You also need to check this now and again, as this setting can revert on Windows updates. Ans, as I said, you are using an old version of FSUIPC4 - only the latest version is supported, so please update to 4.977 before responding further. Also, please change this in your ini, in the [JoyNames] section if your FSUIPC4.ini: AutoAssignLetters=No to this AutoAssignLetters=Yes Not an issue at the moment, but this can/will prevent problems with assignments (that you don't yet have!) if your joy ids change. There are also very mixed messages on your devices between your ini and log files, which is usually a sign of dodgy registry entries. Can you also show me your FSUIPC4.JoyScan.csv file please. Did you try this? It does look like a faulty device, hub or cable is giving these problems.... Please revise my comments and let me know how it goes. This is my last response this year, I will be back covering support from the 3rd Jan. I wish you and your family best wishes for the New Year, John

Hi Hal, thanks for your kind words. I'm happy that its now all working for you. With best wishes to you and your family for a very Happy New Year, John

Your throttle has the same joystick id as your rudder pedals for some reason. Can you please attach your FSUIPC7.ini and FSUIPC7.JoyScan.csv files. We can possibly resolve this by changing your ini file to get the Joy Ids updated, but if that doesn't work me may need to correct/edit your registry. John

Please try the attached FSUIPC4.ini on your new computer: FSUIPC4.ini Best wishes to you and your family for a happy and prosperous New Year. John

Yes - the offset is in BCD format, so you need to look at the hex representation, as it says in the offset status documentation:

First, can you please attach files and not paste their contents. If they are too large, you can zip them. I need to see the complete FSUIPC4.ini. Also, the latest version of FSUIPC is 4.977 - can you please update. Other than that, your log shows that your devices are continually reconnecting. Are you using a (powered?) hub? Make sure that there is enough power for your devices. Maybe try switching them to different usb ports/hubs. And check that you have usb2 devices plugged into usb2 slots. Maybe also try with just one device connected, then add each device back until you notice the problem again. Also, you should change this in your FSUIPC4.ini: AutoAssignLetters=No to AutoAssignLetters=Yes This will assign letters to your devices and prevent issues if/when your Joy ids change. John

Check that you have power management disabled on your USB hubs.

They are in your FSUIPC installation folder. For FSX, that will be under a folder called Modules, in your FSX-SE folder.

Hi Max, I have no experience with motorized TQs- as suggested, maybe ask over on https://www.cockpitbuilders.com/ John

Hi Zsolt, This is the issue. If MSFS doesn't recognise the input as keyboard unput, it won't be forwarded to 3rd party clients. Does MSFS maybe recognise it as another (assignable) device? You can also try to see if FSUIPC recognises your device as a HID type device without running the encoder_keys.exe software. If it is recognised directly (i.e. as a joystick type device), you may be able to assign the MCDU buttons directly to the custom controls. Otherwise you could try using lua. If you want to try this, first verify that the MCDU buttons can be recognised - you can do this using the HiDScanner software, available from here: John

I cannot help with this - you need to look at the FlightPM TQ manuals, or contact them for support for your hardware. I only support FSUIPC, not 3rd party hardware.... No idea. Many people use motorized throttles with FSUIPC, but as I don't have this device I cannot really advise. You may get more response on either the manufacturers forum or over on cockpitbuilders.com. John

Btw, Is FSUIPC4 installed and running ok? If not, I also need to see your installation log.

Can you please show me your FSUIPC .ini and .log files.

Opening FSUIPC6 will make the P3D window go black. Do you not see the FSUIPC6 main window? If not, it is possible that it is being displayed outside if your screen coordinates. If this is the case, delete the ini parameter OptionsDialogOffset from the [General] section of your FSUIPC6.ini file. Not sure what you mean by this...Alt +F4 is the P3D default hot key to exit P3D, which is why you see that pop-up. I think Alt + F is the default hot key to open FSUIPC^, but this is defined by the InvokeFSUIPCOptionsKey ini parameter. There are no issues or conflicts between FSUIPC6 and FSUIPC7. Yes, this will be the issue. Look at (and remove) the ini parameter OptionsDialogOffset and maybe also ConsoleWindow (which stores the windows coordinates of the FSUIPC console window). John

You keep saying this and I keep giving the same response: you will not see your bindings when you look at your log. But you do not see your bindings in the log, as I keep on saying. Your bindings (i.e. assignments) are stored in your FSUIPC7.ini file. You can see the affect of the bindings in the log, if and when you have the appropriate logging options set. Please understand the difference between your FSUIPC7.ini file, which holds all of your settings, and the FSUIPC7.log file, which is a log of the current/latest session. You can assign view controls in MSFS if you prefer. Alternatively, you can assign your POV to the keyboard assignments to control the view. Ok. If you have any issues, activate appropriate logging (which for axes assignments would be Axes control logging) and show me both your FSUIPC7.ini and FSUIPC7.log files, the latter showing you moving your assigned axis through its full range. John

This is true - FSUIPC7 does not detect key presses when it dies not have the focus. It can only detect key presses - when FSUIPC7 has the focus - by receiving the key press as an Input event via SimConnect The issue seems to be that MSFS is not detecting these "key presses" and so not forwarding them to interested 3rd party clients, such as FSUIPC7. Have you tried with an actual keyboard - you should see that it works when using a keyboard and MSFS (or FSUIPC7) has the focus. So this software does the encoding and then forwards to the current windows application that has the focus? Can MSFS see the input from this device as key strokes? If it can, it should forward them to FSUIPC7 via SimConnect. However, if MSFS does not see these as key strokes then they will not be forwarded to 3rd party apps.

Neither your device's GUIDs or Joy Ids should change when using a new hub, so you should be fine. If using JoyLetters and your Joy Ids change, that shouldn't be an issue as the joy letters facility is designed to cope with this. If your GUIDs change then you may need to manually edit your ini. You can do this yourself or post here and we can take a look if that happens. Best wishes for a the New Year. John

For FSUIPC6 and later, I am using the format major.minor.patch with the lower 2 digits of the version number being combined to be the patch number. So v6.1.7 is seen as 0x61070000, v6.2.1 would be 0x62010000m and v6.2.10 would be 0x62100000, etc.

I doubt it, but maybe check on windows 10 if possible. Looking at your assignments, many are using multiple modifiers, e,g, 112=123,15,32907,0 -{alt+lctl+lshift+F12: Press=:MobiFlight.A320_Neo_CDU_1_BTN_R }- I am wondering of this may be the issue... Could you please activate logging in FSUIPC for Buttons and Keypresses as well as for Events, and then generate another FSUIPC7.log file where you load your aircraft and then, when MSFS has the focus, press some of your assigned key combinations - try the following: 6 - should trigger a MobiFlight.A320_Neo_CDU_1_BTN_L3 event lshift+P - should trigger a MobiFlight.A320_Neo_CDU_1_BTN_L1 event alt+lctl+lshift+H - should also trigger a MobiFlight.A320_Neo_CDU_1_BTN_L1 event Then exit and show me the FSUIPC7.log file. Thanks, John

P3D and FSX have a tendency to assign your controllers automatically when they are detected as new controllers. This is why, if assigning in FSUIPC, we recommend to disable controllers completely in the FS (P3D / FSX / FSX-SE). John

Ok - so that is using overloaded assignments to custom controls with an offset condition on the position of the 3 wat switch, as I suggested.... Thanks for reporting back. John