John Dowson

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.

Good. Try adjusting the User Settings at the top of the lua script. Once adjusted, you will need to restart the lua script for the changes to take affect.

Yes what? Is your lua file in the same location as your FSUIPC6.ini file? Are you 100% sure that it has the extension .lua? If so, it WILL be picked-up by FSUIPC and added to the [LuaFiles] section of your FSUIPC6.ini file, which you still haven't shown me. All the information you need to get this working is readily available. If you want further help, please respond to my questions (all of them!) and provide the information I need, which at the moment is to see your FSUIPC6.ini file. Also show me your FSUIPC6.log file.

Please attach your FSUIPC6.ini. Is your lua file in the same location/folder as your FSUIPC6.ini file? Presumably you are using a registered version of FSUIPC6, no?

If FSUIPC6 was running when you dropped in the lua file, it will need to be restarted. If it isn't there, check your FSUIPC6.ini file - it should be listed under the [LuaFiles] section - is it there? If not, it either has the wrong extension (it MUST be .lua) it is in the wrong place. Please see the Advanced User Guide for details on how to auto-start luas if you are having difficulties.

Your FSUIPC6.ini file will be in your FSUIPC6 installation folder. If you don't know where that is, you can use the 'Open Folder' button from the FSUIPC6' logging tab.

See John

What do you mean?

Then I think you need to ask on Vatsim support. FSUIPC doesn't do anything with AI traffic nameplates.

The following MSFS controls/events are available in MSFS, but are not currently exposed via SimConnect and so cannot be assigned directly in FSUIPC7: Taxi Light On Taxi Lights Off Beacon Lights On Beacon Lights Off Nav Lights On Nav Lights Off I reported this to MSFS/Asobo quite a while ago but nothing has been done so far. I will chase this up. There are no default keyboard assignments to these controls, but alt + h is the default keyboard assignment to toggle the beacon lights. What you can do to control these lights, is assign a key or key combination to those events in MSFS, then assign buttons to those key presses in FSUIPC7. Alternatively, have you tried the Beacon Lights Set control, with a parameter for 1 for on and 0 for off? Or you could try with Toggle Beacon Lights, with an offset condition on offset ODOC for bit 1 (ie W0D0C&0002 for beacon lights on to turn off, W0D0C&0002=0 for beacon lights off to turn on). I am assuming that the light bits in offset 0D0C are showing the correct state of the lights. Those offset is also documented as ok for both reading and writing, so you should also be able to control the lights by updating that offset. Have you tried that? If you cannot get it working via one of those methods, let me know which aircraft you are using and I will take a look. There are some additional simvars (documented at the end of the Offset status spreadsheet) that are available but currently not used that I could look into adding if needed: LIGHT BEACON ON LIGHT BRAKE ON LIGHT CABIN ON LIGHT HEAD ON LIGHT LANDING ON LIGHT LOGO ON LIGHT NAV ON LIGHT ON STATES LIGHT PANEL ON LIGHT RECOGNITION ON LIGHT STATES LIGHT STROBE ON LIGHT TAXI ON LIGHT WING ON John

No. The aircraft tags/nameplates are an MSFS feature - check your MSFS General Options settings for Show Traffic Nameplates.

All licenses for FSUIPC are available from SimMarket. FSUIPC6 here: https://secure.simmarket.com/john-dowson-fsuipc6-for-p3dv4-5.phtml John

Your license id for FSUIPC4 only. For P3Dv5, you need a license for FSUIPC6. For MSFS2020, you need a license for FSUIPC7. Each version of FSUIPC requires its own license. WideFS7 is compatible with FSUIPC4, FSUIPC5 and FSUIPC6, so that should work with each product.# If you want to try FSUIPC7, ther is a trial license available here: John

Try running FSUIPC7 - if it won't run (unregistered), it may be a problem with your VC++ redistributables. If this is the case, you need to uninstall and re-install them - instructions are in the README.txt provided. If FSUIPC7 runs ok, you can try manually creating your FSUIPC7.key file, or use your previous one if still available. See here for details: John

👍

Note when using this script, the virtual buttons will not be seen in the button assignments panel. This is because the event.offset and event.button functions are not called when the buttons assignment panel is open. Therefore, to assign to the virtual buttons, you should first assign to the physical buttons and then edit your FSUIPC7.ini to manually change the assignments to the virtual buttons (including duplicating the physical button assignment to create two virtual button assignments and changing the control for the fast/slow movement). For an alternative solution that uses polling and so the virtual buttons can be seen on the assignments panel, together with examples on how to assign to the virtual buttons for the different functions of the selector knob, see John

@Dreamflight767 Did you manage to configure your Bravo AP? I have just configured mine, for MSFS, but it should be the same for P3D. This is how I did it. First, you need the following lua file: Rotaries.lua Save that file to your FSUIPC6 installation folder. This will give the two rotaries on the Bravo fast/slow support. To use this, you need to have it auto-ran. To do this, add it to your [Auto] section of your FSUIPC6.ini, or create if not there, e.g. [Auto] 1=Lua Rotaries This will convert the rotaries physical buttons to virtual buttons. With this, you don't want to see the physical button presses registered in the assignments UI. To prevent this, add the following line to your [Buttons] section of your FSUIPC7.ini file: IgnoreThese=B.12, B.13, B.21, B.22 NB. My Bravo is assigned the letter B. If yours is different, change the letter to the one you are using. Next, you need to add the assignments. You can use the following i.e. copy and paste to your [Buttons] section. When you have done this, you will need to adjust the index numbers (i.e. first number on each line) to make sure that they are all unique (and better consecutive). Also, you again need to change the B in the (+B,??) bit to the letter you are using. 58=CP(+B,18)64,0,C65879,0 -{HEADING_BUG_INC}- 59=CU(+B,18)64,0,C65879,0 -{HEADING_BUG_INC}- 60=CP(+B,18)64,1,C1025,0 -{heading bug inc fast}- 61=CP(+B,18)64,2,C65880,0 -{HEADING_BUG_DEC}- 62=CU(+B,18)64,2,C65880,0 -{HEADING_BUG_DEC}- 63=CP(+B,18)64,3,C1024,0 -{heading bug dec fast}- 64=CP(+B,16)64,0,C65897,0 -{AP_SPD_VAR_DEC}- 65=CU(+B,16)64,0,C65897,0 -{AP_SPD_VAR_DEC}- 66=CP(+B,16)64,1,C1020,0 -{ap spd var dec fast}- 67=CP(+B,16)64,2,C65896,0 -{AP_SPD_VAR_INC}- 68=CU(+B,16)64,2,C65896,0 -{AP_SPD_VAR_INC}- 69=CP(+B,16)64,3,C1021,0 -{ap spd var inc fast}- 70=CP(+B,17)64,0,C65662,0 -{VOR1_OBI_DEC}- 71=CU(+B,17)64,0,C65662,0 -{VOR1_OBI_DEC}- 72=CP(+B,17)64,1,C1026,0 -{vor1 obi dec fast}- 73=CP(+B,17)64,2,C65663,0 -{VOR1_OBI_INC}- 74=CU(+B,17)64,2,C65663,0 -{VOR1_OBI_INC}- 75=CP(+B,17)64,3,C1027,0 -{vor1 obi inc fast}- 76=CP(+B,19)64,0,C65895,0 -{AP_VS_VAR_DEC}- 77=CU(+B,19)64,0,C65895,0 -{AP_VS_VAR_DEC}- 78=CP(+B,19)64,1,C1022,0 -{ap vs var dec fast}- 79=CP(+B,19)64,2,C65894,0 -{AP_VS_VAR_INC}- 80=CU(+B,19)64,2,C65894,0 -{AP_VS_VAR_INC}- 81=CP(+B,19)64,3,C1023,0 -{ap vs var inc fast}- 82=CP(+B,20)64,0,C65893,0 -{AP_ALT_VAR_DEC}- 83=CU(+B,20)64,0,C65893,0 -{AP_ALT_VAR_DEC}- 84=CP(+B,20)64,1,C1016,0 -{ap alt var dec fast}- 85=CP(+B,20)64,2,C65892,0 -{AP_ALT_VAR_INC}- 86=CU(+B,20)64,2,C65892,0 -{AP_ALT_VAR_INC}- 87=CP(+B,20)64,3,C1017,0 -{ap alt var inc fast}- For the trim wheel, you can also use these: 52=P64,6,Cx32000BC0,x3FFF0018 -{offset sword increment, offset 0BC0 (Incr=24, Limit=16383)}- 53=P64,7,Cx32000BC0,x3FFF0032 -{offset sword increment, offset 0BC0 (Incr=50, Limit=16383)}- 54=P64,4,Cx42000BC0,xC0010018 -{offset sword decrement, offset 0BC0 (Decr=24, Limit=-16383)}- 55=P64,5,Cx42000BC0,xC0010032 -{offset sword decrement, offset 0BC0 (Decr=50, Limit=-16383)}- 56=U64,7,Cx32000BC0,x3FFF0032 -{offset sword increment, offset 0BC0 (Incr=50, Limit=16383)}- 57=U64,5,Cx42000BC0,xC0010032 -{offset sword decrement, offset 0BC0 (Decr=50, Limit=-16383)}- Hope that helps. John

As well as what Blake has said, before you fo that, check that the gear control offset at 0BE8 is showing the correct value (again, by logging). If it is, you can do as Blake says, with the dowsides of this approach. If offset 0BE8 is not showing the correct gear position, you are out of luck.

You don't need to make any changes any more as Blake has already updated the scripts so this is not necessary (and that is also why the line numbers have changed). Check that offset 060C is populated correctly for the aircraft that you are using, i.e. shows 1 (for retractable). You can do this using the offset logging facilities (as UB).