Jump to content
The simFlight Network Forums


  • Posts

  • Joined

  • Last visited

Posts posted by paulinyyz

  1. No, I can't see them in the way you would press the switch and have it respond with the corresponding number in FSUIPC. What you can do in the Controls section of MSFS is select the Bravo throttle and select the known button position. I know that the first toggle/rocker switch is 34 and 35 so I can assign pitot heat on/off but what happens is the switch on the panel is stuck either up or down, so the button are connected somewhere. It is as if in FSUIPC you could overwrite the joystick button numbers and enter what you liked.

    The levers each have a detente at the bottom which when moved past the detente becomes a button press, what I just discovered is when moving the lever which when moved through the detente becomes button #33, FSUIPC7 with the new .exe identifies it as #132. But when one of the seven toggles is pressed, nothing.

  2. Hi John,

    I think I am just flogging a dead horse here, the new .dll for FSUIPC6 works with the Alpha but still nothing with the Bravo so I can only assume that the seven switches are defective. I know they are doing something because in MSFS when I assign one of them to a switch function, the switch can no longer be moved with the mouse, it is jammed or jiggles rapidly, just not doing the right thing.

    I have tried to contact Honeycomb but have not had a reply yet and not sure if I will even receive one.


  3. I tried the HidDemo.lua after editing the vendor and product id's and removing the other two scripts but no luck. It was odd because when I pressed one of the <32 switches or buttons, FSUIPC would ID the joystick as F which is correct for the Bravo but as I flipped between position, #64 would flash up, still nothing from any of the seven rocker switches.

    In FS 2020 controls I tried to assigned one of the seven to a pitot heat switch by manually selecting the switch positions but as before it either froze the toggle on the panel in place or it vibrated, so the rockers are doing something, just not the right thing.

    Maybe I will try vjoy and the other bits that go along with it and see what happens.

    For what it's worth I ave attached the FSUIPC log and the HidScanner log.


    FSUIPC7.log HidScanner.log

  4. I can see all the numbers <32 in both FSUIPC and the Windows game controller, it's only the rocker/toggle switches which don't appear. In MSFS the picture of the device has the first of the toggles switches starting at 34 up to 47, 33 doesn't seem to feature anywhere.

    Power management for the port is disabled and changing ports didn't help.

    I will try some of what you suggested under "Useful additional programs".


  5. Hello,

    The Bravo comes with the toggle keys assigned to functions as landing light, beacon, pitot heat etc. If you move the switch, the corresponding assignment does not happen, i.e the pitot heat switch will not move but it seems like this is because the "always on" state is the reason. If I remove one of either the on or off positions, the corresponding switch on the panel will move one way but will not go back the other way. So they have an effect but not really working because they are stuck in one position or another.

    To recap, the Alpha LUA script will work and is seen by FSUIPC at joystick #64 but the Bravo script is not recognised, I think it should be seen as #65.

    I have attached the log file, it's a new day so I am now allowed more quota.



  6. Hello,

    I have both the Honeycomb Alpha and Bravo and wanted to address the switch assignments greater than 32 for both devices. I found and followed this topic, "A step by step for FSUIPC7, Honeycomb Alpha Yoke, and MSFS2020" and now have the switches (rotary start switch) working for the Alpha (joystick #64) but not having the same luck with the Bravo, still no response when pressing any of the seven rocker switches.

    I did see this reference, "The other lines which you might want to change are: Device = 0  -- Multiple devices of the same name need increasing Device numbers."  and wondered if this was necessary but there was no mention of what to change it to, 1 or maybe 01, tried both but didn't seem to make a difference and after searching every LUA related PDF in the Documents folder I still could not find anything.

    I have attached my INI file and the latest FSUIPC7 log.


    It appears that I can't attach both file because together they greater than what I am allowed to here is the LUA entries in the INI.

    1=lua hidAlphaButtons
    2=lua hidBravoButtons



  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.