John Dowson

I had added these when they appeared in the documentation, but when I tried to use them I got unrecognised errors when trying to request them. These are the ones that were not recognised: //{KEY_AP_FLIGHT_LEVEL_CHANGE , "AP_FLIGHT_LEVEL_CHANGE"}, -- NAME_UNRECOGNIZED //{KEY_AP_FLIGHT_LEVEL_CHANGE_ON , "AP_FLIGHT_LEVEL_CHANGE_ON"}, -- NAME_UNRECOGNIZED //{KEY_AP_FLIGHT_LEVEL_CHANGE_OFF , "AP_FLIGHT_LEVEL_CHANGE_OFF"}, -- NAME_UNRECOGNIZED //{KEY_AP_ALTITUDE_SLOT_INDEX_SET , "AP_ALTITUDE_SLOT_INDEX_SET"}, -- NAME_UNRECOGNIZED //{KEY_AP_HEADING_SLOT_INDEX_SET , "AP_HEADING_SLOT_INDEX_SET"}, -- NAME_UNRECOGNIZED //{KEY_AP_VS_SLOT_INDEX_SET , "AP_VS_SLOT_INDEX_SET"}, -- NAME_UNRECOGNIZED //{KEY_AP_SPEED_SLOT_INDEX_SET , "AP_SPEED_SLOT_INDEX_SET"}, -- NAME_UNRECOGNIZED //{KEY_AP_RPM_SLOT_INDEX_SET , "AP_RPM_SLOT_INDEX_SET"}, -- NAME_UNRECOGNIZED However, I'm not sure what version I last tested these. I will take a look and if they are now available I will re-activate. There are a lot of new events in the last couple of SU updates. I still need to revise the documentation to see what else can be added. I am planning to do this in the next few days/weeks, once I have cleared the backlog of support requests (and updated my various systems to the latest MSFS/P3D releases....). John

And a Happy New Year to you as well! I will update later today...working through the backlog... John

Did you try a right-click and selecting Sava as... ? Other than that, I have no idea. Can you access from this: FSUIPC WASM Module 0.5.5d Thats the same link as in www.fsuipc.com, with the link source: http://www.fsuipc.com/download/FSUIPC-WASMv0.5.5d.zip Maybe your browsers don't like http? Try pasting that link directly in your browser. Or maybe its some sort of anti-virus software preventing the download?

Button 22 has one assignment: 15=P3,22,Cx03009400,x00000002 -{offset dword set, offset 9400}- which your log shows being pressed and the ssigned vontrol sent: Ok.

Then you must be running 5.2....I have just updated to 5.3HF1 and get this: I really can't see how it is reporting the incorrect version - this is taken from the Prepar3D.exe file properties. What does your P3d Help -> About menu option report? Is there an MSFS update? I'm still on 1.21.13.0 which I thought was the latest - just fired it up and no update available for me... John

No luck with what? What did you try? Yes, but before we do that can you let me know if you did have any saitek software or drivers installed or not. And if you did and removed them, I need to see your updated files.

Are you sure? Just took a look and it says 53 for me: 114047 Monitor IPC:3124 (U8) = 53 114047 Monitor IPC:3124 (U8) = 53 I still haven't updated to the latest 5.3 HF. I will do that today and recheck. Could you check again and if you still see 52 please show me your FSUIPC6.log file. The version in that offset should match the P3D version reported at the beginning (2nd line) of the log: Prepar3D.exe version = 5.3.12.28072 John

Are you sure? Which browser are you using? Just tried in Chrome and it downloaded as expected. Maybe a temporary glitch?

Your log shows both assignments on joystick3 button 23 being performed: That also shows your LandingLightsOn macro being executed. There are no assignments to your compound runwayturnoff macro, so I cannot check that. Therefore I cannot see any issues. Could you maybe explain again what your problem is, and provide an appropriate log and ini file if you want me to look into this further. John

Could you please attach a full log, not a continuation log. i.e. do NOT start a new log file. I need to see the complete file. If its too large, just zip it. Are you sure FSUIPC wasn't running when you edited the ini file? If so, you need to reload the assignments before they take affect. This shoudn't be a problem and is a common technique. This should also be fine - can you attach the macro file please. John

The 'Ignore Axis' button is used to disregard input from that axis for assignment purposes only. It has no affect when FSUIPC is not open. Please see the documentation provided. Then simply remove/delete any assignments in FSUIPC that you have to the yoke and throttle. i.e. rather than click 'Ignore axis', click the 'Clear' button, then 'Ok'. Otherwise, just manually remove any assignments manually from your ini file. You will need to have an axis section in your airbus profile, otherwise the general axes assignments will be inherited, but I think its ok for this to be empty (although I will check this....). Note that it is not possible to remove general button assignments for these devices. If you do not want any button assignments for these devices, all your button assignments for these devices must be done in profiles rather than be general, or they will be inherited in your Airbus profile. John

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