Jump to content
The simFlight Network Forums

morrispe

new Members
  • Posts

    4
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Canada

morrispe's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

1

Reputation

  1. Thanks so much for posting these. The two LUA files with separate 3340 = ALPHA, 3344 = BRAVO offsets are what I needed. Both controllers are working properly now with FSUIPC7 and I'm able to assign functions to all of the switches in MSFS2020 🙂
  2. I've merged the button code section of the HidDemo LUA into the previously downloaded HidButtons32-39 LUA file and came up with the attached HidButtonsBravoQuad LUA file. when calling both LUA files (for the Alpha and Bravo) from the FSUIPC7.ini FSUIPC7 is now detecting events from all switches on both controllers. The button event detection lag issue I was seeing previously on the Bravo is also gone. The only remaining issue is that the above 32 high switches on both devices are seen as Joy# 65 by FSUIPC7. Just need to figure out how to get FSUIPC7 to see each controller as a separate Joy# and I'll be able to assign all the desired MSFS2020 functions to the Bravo switches. Making progress. HidButtonsBravoQuad.lua
  3. I tried increasing it to "Device = 1" in the Bravo lua file but it doesn't seem to work unless I have it set to zero. With both lua's using Device = 0 and their respective product ID's I'm getting Joy# 65 for both. I tested loading the HidDemo.lua as is and inserting Vendor = 0x294B, Product = 0x1901 and that does work for all the buttons on the Bravo however for some reason its showing a 4 - 5 second lag when registering switch inputs. I might try extracting just the button sections as I don't require the axis to see if I can resolve the event registration lag issue. Thanks for the responses. P.
  4. Hello, I was able to use the HidButtons32-39.lua provided in one of the threads to map the buttons above 32 on my Honeycomb Alpha. In doing so I've been able to assign all of the rotatory magneto switch positions using FSUIPC7 in MSFS2020 I have now received my Honeycomb Bravo throttle quadrant and I'm attempting to do the same for it. Hidscanner shows the Alpha as: Vendor = 0x294B Product = 0x1900 and the Bravo as: Vendor = 0x294B Product = 0x1901 I created a second lua file named HidButtonsBravo.lua using the 0x1901 product ID and the FSUIPC7.ini has entries to load both lua files. When running MSFS2020 and FSUIPC7 the low switches on the Alpha show as Joystick A and the Bravo shows as Joystick D which can also be seen in the FSUICP7.ini Joystick names section. The issue I'm having is that when I trigger switches above 32 (or 0-31) FSUIPC7 is seeing them as Joy# 65 for BOTH the Alpha and the Bravo controllers and they are therefore in conflict with each other and manipulating the same functional assignment within the MSFS2020 simulator. How can I assign the Bravo to another separate Joystick like Joy# 66 for the higher than 32 switches? I haven't been able to figure this part out? In addition I believe the Bravo also has a total of 48 switches and the 32-39 lua file I'm using doesn't seem to detect any Joy# 65 Button inputs when I trigger the higher switches on the Bravo. Can I modify this lua to accommodate up to 48 switch inputs? I'm a complete lua noob so some assistance would be appreciated. Thanks
×
×
  • 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.