John Dowson

Sorry, I'm probably posting too many messages and confusing you... If you have done anything yet, first try this: - unplug your devices - backup your registry - run the .reg file again - remove the drivers for your X55 using the windows device manager - reboot - connect your devices. Let windows install the default drivers - start P3D/FSUIPC, load an aircraft, then shut down - show me your 3 files, the .ini, .log and .JoyScan.csv files If you still don't get the devices recognised as individual devices after doing this, then you can try manually setting/changing the joystick using a program called JoyIds. See John

Maybe also try removing the installed drivers for the X55 after you have removed the registry entries (and before you plug in your controllers), and let windows re-install them again when you re-connect. I would do this before manually removing anything else with the same vendor and product ids.

I suspect that there may be other registry entires that need removing.... You could try running the.reg file again with devices unplugged (again, backup first), then reboot. Start regedit, backup again, and then search for 0738 (the VendorID for the X55). All entries you encounter that look related to your devices (i.e. if they also have a Product ID of 2215 or A215) should be removed. Then reboot again, connect you devices, start P3D/FSUIPC and see what is recognised. Show me you .log, .ini and .joyscan.csv files after doing this. Maybe show me your current JoyScan.csv file first before doing this though....

I don't understand why the registry cleaning seemed to do nothing this time. And I don't understand why it is again getting two GUIDs for your stick but none for your throttle. Could you show me your FSUIPC5.JoyScan.csv file please.

I don't know why it has done this again....are you unplugging your devices? Try cleaning the registry again. Once done, and you have ran P3D/FSUIPC once to update your ini, close P3D and then change this line in your FSUIPC5.ini: AutoAssignLetters=No to AutoAssignLetters=Yes And the run P3D/FSUIPC again. Close down P3D/FSUIPC and show me your updated FSUIPC5.ini and FSUIPC5.log files (the devices may need switching after doing this). I don't know why it has done this again. Are you sure you don't have the saitek/logitech drivers installed, or are running any saitek control software?

Sure. No, you can leave it running - it shouldn't take up too many resources. However, if you don't want to use it, you can also opt to not install it during the installation process. If you occasionally want to use it with FSUIPC7, you can just move it out of your Community folder (i.e. move it up one folder level) before you start MSFS, and when you want to use it just move it back, again before you start MSFS.

Because when you installed FSUIPC7 you selected the option to auto-start with MSFS. When this is selected, it creates or updates the MSFS EXE.xml file so that MSFS auto-starts FSUIPC7 at the appropriate time. If you don't want this to happen., re-install FSUIPC7 and deselect the auto-start component. After doing this, if you want to still have the ability to start FSUIPC7 with MSFS from the desktop MSFS link that is created, you can edit the MSFS.bat file, located in your FSUIPC7 installation folder, and located the following lines (although your path to the FSUIPC7.exe may be different): Then remove the two double colons which comment out the timeout and start lines, thus: If you do this, you can then use the MSFS desktop link to start MSFS and FSUIPC7, or the standard MSFS desktop link or start menu option to start MSFS without FSUIPC7. John

Yes - or you can remove them using the assignments UI panel, if they are single assignments to buttons.

Please see the README.txt file provided in the downloaded zip file. You need to uninstall and re-install your VC++ redistributables.

And it looks like you can also control the Pedal DISC with the lvar AB_FCTL_Tiller_Toggle - see https://forum.aerosoft.com/index.php?/topic/148027-mapping-pedal-disc-to-button/ Maybe the easiest root to take - just set up a macro for that lvar (see the Advanced User Guide for details).

There is also a lua script for the A320 pedal disconnect button in this post:https://forum.aerosoft.com/index.php?/topic/94496-rudder-pedal-disc-button/ However, that post is quite old now and the lua is no longer available. It may be worth asking on the aerosoft forums.

I don't think there is a standard control for this. Before trying lua, try setting up a mouse macro instead. See the Advanced User guide for details.

Ok. You can try but it may not be necessary, I've just checked in the windows Game Controllers to see what it says for my X55 throttle and stick, and I have something similar but the other way around - I see the test page for the throttle but not the stick, and the calibrate button is grayed out. However, as both my stick and throttle work as expected, this doesn't seem to be an issue. I think this is maybe just how the x55 works. The difference in our systems is that for me the stick has id 0 and the throttle 1, and yours is the other way around. I don't think this is an issue. Just try Pete and my suggestions in FSUIPC. Ok, no problem. Let us know how you get on. John

Did you try going to the settings page and calibrating?

No - you have controllers enabled in P3D - from you log file: You have removed the assignments, not disabled controllers. This may be ok, but the problem is that P3D will occasionaly re-recognise your controller and then re-assign if controllers aren't disabled. Due to this, we recommend disabling controllers completely in P3D if assigning in FSUIPC. Its ok if you want to do it this way, but just be aware the P3D can re-assign your throttle on occasion, and so if you start experiencing strange axis movements, then re-check your P3D assignments. John

Was just replying when Pete has replied.... As well as what Pete says, , you should also remove the slopes. You can add these later, if needed, once the throttle is calibrated correctly. You can do this either in the UI, or by removing the SlopeThrottle1/2 ini parameters from your [JoystickCalibration] section (and then reload the file by using the 'Reload all assignments' button from the axes assignment panel. Also make sure that the throttle axis is set-up and calibrated ok in the windows calibration before anything else. And as well as what Pete has said about using the AXIS_THROTTLE controls with NRZ checked, you should also try assigning 'Direct to FSUIPC Calibration' rather than 'Send to FS as normal axis' if calibrating in FSUIPC. This generally works better for most aircraft, but if the a/c implements its own throttle calibration system (which can happen in more complex add-on aircraft), then you should use 'Send to FS as normal axis' as there can be timing issues with different values (calibrated and uncalibrated) going to the sim causing jittering on the axis. John

But you have no throttle or indeed any axes assignments in FSUIPC. If you have disabled controllers and assigned and calibrated your throttle axis in FSUIPC, I need to see your updated FSUIPC5.ini file to advise, and also your FSUIPC5.log file. There is no point in me watching your videos. I need to see your assignments before anything else. Then show me your files!

They are logged to the FSUIPC6.log file, also located in your FSUIPC6 installation folder. That won't affect logging of lvars from a control. There is a lua script that also logs lvars that you can use (see the example lua scripts provided), but I think its easier to use the control if not familiar with lua. John

Maybe also try using the full hive name instead of the abbreviatuib, so use HKEY_LOCAL_MACHINE instead of HKLM, and HKEY_CURRENT_USER for HKCU...

How are you changing the increment/decrement delta value? This is the assignment line for decrement: The delta value is what I have highlighted (0100 hex = 256 decimal). The descriptive text is a comment - you cannot change the value there. Really you should change in the assignments dialog, but you can also change the value in the ini if you like. However, it is confusing that you say the trim wheel action is too slow, but you want to reduce the delta from 256 to 128 which would make it twice as slow!! To speed it up, you need to increase the delta. If using a buttons for trim, you can also try lua scripts which can distinguish between a short button ptess (for a small inc/dec) and a long button press (for a larger and repeated in/dec). There is a generic triple-use lua script for buttons that you can use (will obviously need modifying!) here: There is also the example Rotaries.lua that you can use, which is for single button rotaries (in each direction) which is the same as using two buttons, so you can adapt that for your needs. I recently adapted this for the Honeycomb Bravo, but you could also do something similar to use the buttons on your alpha in a similar way: Yet another trick folks use is to duplicate (or triple.quadruple) there assignments, so it sends the same control 2, 3 or 4 times. This works ok for fast movement, and maybe ok for trim, but I woukd onkly do that if using double or truple use in the button, so a long press would result in duplicate large delta controls being sent, but a single press would result in just one smaller inc/dec being sent. I am using the Bravo for trim. and here are my ini entries (FYI): In those assignments, my two physical buttons for in/dec have been converted to 4 vurtual buttons, one for slow in, one for fast in, one for slow dec, and one for fast dec, and then my fast assignments have been duplicated (i.e. being sent on press and release in my case). Hope that helps and isn't too confusing.... John

Are you using the stock A320 or the FBW mod? If the former, you should try the latter... What do you mean by 'won't work'? Do you mean they don't work in the UI? If so, you cannot control them - try the FBW mod. Or are you saying that the controls you are using dont work? If so, which ones? Have you tried logging the events to see which controls are logged (if any)? If no controls are logged, try listing the lvars or look at available hvars. For the FBW mod, I think the following lvar is available: XMLVAR_Momentary_PUSH_OVHD_APU_MASTERSW_Pressed with value 1 for on and 0 for off. Not sure about the stock A320 - take a look for yourself if using that. Have you tried the Beacon Lights Set with a parameter of 1 for on an 0 for off? For more info on beacon lights, see I have answered this question so many times now....please search the FSUIPC or Asobo forums for this. Basically you need to look into using the *_SLOT_INDEX_SET controls. You can start here: or maybe here: https://forums.flightsimulator.com/t/simulator-events-for-switching-between-managed-and-selected-mode-in-the-a320/323838 https://forums.flightsimulator.com/t/airbus-neo-is-there-a-binding-to-switch-between-managed-and-selected-modes/244977/4 The A320 is not an easy aircraft to control and you may get more help from other A320 flyers if you include that in the title of your post - I have added it for you. Here are also some lua scripts that have been provided by another user - I am attaching them as an example of the sort of thing you need to do to control things properly in the A320. You can try using them if you like, but you would need to edit/adjust for your controllers. John FCU_Hdg.lua FCU_Speed.lua FCU_VS.lua FCU_Alt.lua

The script you attached is not the same as I pasted. It is missing the first line which is needed. Please try with that added. John

First, if you have installed any Saitek/Logitec drivers or software, you must remove/uninstall those. As your stick is recognised as two devices, this makes me suspect that you either have the saitek drivers installed or some saitek/logitek software. This is how FSUIPC5 sees your devices: 187 Product= Saitek Pro Flight X-55 Rhino Stick 187 Manufacturer= Madcatz 187 Serial Number= G0001739 187 Vendor=0738, Product=2215 (Version 0.87) 328 GUIDs returned for product: VID_0738&PID_2215: 328 GUID= {F866EB80-CAB4-11EA-8004-444553540000} 328 Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U0,V0,X65535,Y65535,Z0 328 GUID= {F866EB80-CAB4-11EA-8003-444553540000} 328 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 328 Product= Saitek Pro Flight X-55 Rhino Throttle 328 Manufacturer= Madcatz 328 Serial Number= PP000503 328 Vendor=0738, Product=A215 (Version 0.119) Note the 2 GUIDs for the stick, but none for the throttle. I also gave the X55, and this is my equivalent log extract: 390 Product= Saitek Pro Flight X-55 Rhino Throttle 390 Manufacturer= Madcatz 390 Serial Number= G0001630 390 Vendor=0738, Product=A215 (Version 0.119) 406 GUIDs returned for product: VID_0738&PID_A215: 406 GUID= {8B238AC0-45DE-11EA-800C-444553540000} 406 Details: Btns=35, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X1023,Y1023,Z255 406 Product= Saitek Pro Flight X-55 Rhino Stick 422 Manufacturer= Madcatz 422 Serial Number= G0003298 422 Vendor=0738, Product=2215 (Version 0.87) 422 GUIDs returned for product: VID_0738&PID_2215: 422 GUID= {8B23B1D0-45DE-11EA-800E-444553540000} 422 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0 i.e. each has its own GUID, and the product id of the stick and throttle are different. So, please remove any drivers or software that you have installed for the X55. Then disconnect your devices and reboot. Save the following text as a .reg file (e.g. removeX55.reg): Take a backup of your registry (using regedit), then double click the .reg file created (with the above content) to run it. This should remove those entries. Then re-connect your devices and start P3D/FSUIPC5. Load an aircraft and see if both your controllers are recognised. If not, show me your updated FSUIPC5.log and FSUIPC5.ini files, as well as your FSUIPC5.JoyScan.csv file. John

Your files show that you have registry issues, with duplicated joystick ids, resulting in both your stick and throttle being assigned the same id: 343 WARNING: Joystick ID 0 is duplicated in Registry 343 WARNING: Joystick ID 1 is duplicated in Registry 343 Device acquired for use: 343 Joystick ID = 0 (Registry okay) 343 0=Saitek Pro Flight X-55 Rhino Stick 343 0.GUID={F866EB80-CAB4-11EA-8004-444553540000} 343 Device acquired for use: 343 Joystick ID = 0 (Registry okay) 343 0=Saitek Pro Flight X-55 Rhino Throttle 343 0.GUID={F866EB80-CAB4-11EA-8004-444553540000} Have you installed any saitek drivers or software? If so, best to remove those. But you have very few assignments anyway. In fact, the only assignment you have in FSUIPC is for one button for Gear Down: 1=P0,6,C66080,0 -{GEAR_DOWN}- You have no other buttons or axes assigned. You have controllers turned on in P3D, so all your other assignments (including axes assignments) must be there. If you want to assign in FSUIPC, you will need to clean your registry. To do this, disconnect your devices and then remove all registry entries for Vendor id 0738 and product id 2215. Take a backup of your registry before you do this. Then re-connect your devices and try again. You should also turn controllers off in P3D if assigning in FSUIPC. If you need help removing the registry entries, let me know.

Please show me your FSUIPC log and ini files.