Falcon BMS Forum
    • Register
    • Login
    • Search
    • Categories
    • Unread
    • Recent
    • Unsolved
    • Popular
    • Website
    • Wiki
    • Discord

    [SOLVED] v4.36 - can't detect keys > 32

    Winwing
    6
    11
    287
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • V
      viffviff99 last edited by viffviff99

      Newbie with a new install here. I read the latest version of bms supports 128 keys, but I’ve got 4.36.1 and it does not detect any keypress with a number above 32 when trying to assign keys. I’m using the normal launcher and Winwing Orion 2 joystick and thottle. Any key press below button number 32 is fine. The Alt Launcher can see the keys above number 32, but I have read there are problems with using Alt Launcher and Winwing. Do I have to use 4x32 mode with 4.36 still? Many thanks

      1 Reply Last reply Reply Quote 0
      • MaxWaldorf
        MaxWaldorf last edited by

        check BMS manual as you need to activate the 128 support via a parameter set…

        Benchmarksims Developer - Falcon Lounge Founder

        V 1 Reply Last reply Reply Quote 0
        • V
          viffviff99 @MaxWaldorf last edited by

          @MaxWaldorf Thank you! I will look tomorrow

          V 1 Reply Last reply Reply Quote 0
          • V
            viffviff99 @viffviff99 last edited by

            @viffviff99

            Read the manual (Tech Manual section 10 page 10-164 from memory). it says to change the default to 128 using
            " a new config option, g_nButtonsPerDevice, which defaults to 32 for backwards compatibility reasons, but users can now set this to a larger value if they want to support more buttons per device".
            But: “The config line is not present in the default file”.
            I’ve not edited a config file before (and makes me a little nervous). Do I simply insert that line with “=128” at the end? Or is there a simple guide to how to safely edit the config file?

            Badger L 2 Replies Last reply Reply Quote 0
            • Badger
              Badger @viffviff99 last edited by

              @viffviff99 you can add the line with any text editor, like notepad, I’d suggest you add it in the x:Falcon BMS 4.36\User\Config\Falcon BMS User.cfg file.

              V 1 Reply Last reply Reply Quote 1
              • L
                lew0984 @viffviff99 last edited by

                @viffviff99 said in v4.36 - can't detect any key above 32:

                @viffviff99

                Read the manual (Tech Manual section 10 page 10-164 from memory). it says to change the default to 128 using
                " a new config option, g_nButtonsPerDevice, which defaults to 32 for backwards compatibility reasons, but users can now set this to a larger value if they want to support more buttons per device".
                But: “The config line is not present in the default file”.
                I’ve not edited a config file before (and makes me a little nervous). Do I simply insert that line with “=128” at the end? Or is there a simple guide to how to safely edit the config file?

                My knowledge of .config etc is zero, but following the directions in the user manual to add to the user config I’ve been able to implement a heap of stuff, including the 128 option. It’s testament to the guys writing the manuals, especially if I can make it work!

                1 Reply Last reply Reply Quote 0
                • V
                  viffviff99 @Badger last edited by viffviff99

                  @Badger Many thanks for the advice, that’s very useful. Will give it a go.

                  SOLVED: Use syntax: “set g_nButtonsPerDevice 128” - works a treat!

                  Boy there is a lot to learn… Probably about as much to learn as the real thing!

                  K 1 Reply Last reply Reply Quote 1
                  • K
                    Kumquat @viffviff99 last edited by

                    @viffviff99 I’m new at this and have a Orion with the F16 handle. So I just add that line to “C:\Falcon BMS 4.36\User\Config\Falcon BMS User.cfg”? Right now it looks like this:

                    ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
                    // User can place here his or her specific configurations lines that will superseed the main ones located in the Falcon BMS.cfg file //
                    ///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

                    set g_nButtonsPerDevice 128

                    airtex2019 1 Reply Last reply Reply Quote 0
                    • airtex2019
                      airtex2019 @Kumquat last edited by

                      @Kumquat yep … if you have more than 2 devices with buttons, be aware you may also need to raise your pinky-shift offset (the default shift-range is 256).

                      set g_nButtonsPerDevice 128
                      set g_nHotasPinkyShiftMagnitude 1280 // room for 10 devices
                      

                      BUT changing that will hork existing key file layouts … eg. all the stock key files are coded with shift-range starting at 256. so you’ll have to update the shifted-button assignments manually, or with Alt Launcher

                      K 1 Reply Last reply Reply Quote 0
                      • K
                        Kumquat @airtex2019 last edited by

                        @airtex2019 Ahh ok! Well right now I only have the throttle and a VKB stick. But plan on getting the Cougar MFDs and a Simgears ICP. So should I go ahead and make it 1280 now?

                        Interestingly, after I edited my “falcon BMS user.cfg” file, I opened the main “falcon bms.cfg” and noticed that this line was already in there:

                        set g_nButtonsPerDevice 128 // SETUP OVERRIDE

                        So I guess I didn’t have to add it after all?

                        airtex2019 1 Reply Last reply Reply Quote 0
                        • airtex2019
                          airtex2019 @Kumquat last edited by

                          @Kumquat it is true the latest Alt Launcher sets it to 128 now … I think you’re seeing the result of that

                          I don’t know, if Alt Launcher has any special ability to track which button-assignments map to which device, and adjust accordingly (incl. pinky-shift magnitude) if/when you plug in new devices.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post

                          53
                          Online

                          10.6k
                          Users

                          21.0k
                          Topics

                          348.8k
                          Posts

                          Benchmark Sims - All rights reserved ©