ffingers

Yeah happy to. I did reinstall beta 1 so its working now, but happy to throw another install on to troubleshoot the issue. Also just so you know, I used a generic USB controller as well thinking maybe it was the GP-Wiz or vJoy but it happened with a generic controller as well. It was not willing to recognize any USB controller. I'll throw on a fresh version of beta 3 and check if the same thing happens and I'll let you know.

Wanted to let you know of an issue I identifed with beta 3. I recently did a whole new LB build moving to a new computer. As a result I had to redo all the controls etc. (this will matter in a second). I had done all the mapping using a gamepad and a virtual joystick (vjoy) all was fine. Realized I need to go back in and tweak the order of the controllers and whatnot. When I went into change things, LB and BB refused to recognize any controller input when remapping. I thought I had done something when moving controllers around, but everything worked in all the emulators, in windows, etc. Just LB and BB refused to register inputs for remapping and most input just for navigation (if any mappinges still existed). I racked my brain trying multiple different things. I tried an old install in a different directory and the controllers worked as intended. I figured it was a bad install, something got corrupted. I did a reinstall of beta 3 over the top of the existing LB and it still didn't work. I tried a rollback to beta 1 and all of sudden, all controllers and inputs were recognized. All this to say, there is something definitely wonky with beta 3 and USB game controllers and mapping. For reference I'm running Windows 11 and the game controllers were a GP-Wiz from GroovyGamer and also a virtual stick using vJoy.

Are you by chance running steam at all? I have a controller that works absolutely fine, HOWEVER, if Steam is running (due to launching a game via BB or just running at startup) - it completely messes up the controller in BB. It does what you say, it skips up and down and it's not even consistent. I'm not sure if the Steam app adds a level of sensitivity or what. To be honest, I identified the problem awhile ago but have not done any troubleshooting within Steam to see if it has a setting or something that is causing it. All I have done is verified that it was Steam causing my controller to go wonky in BB. Tony

So I have a weird issue and am curious if I'm the only one having it or if it's a known limitation or I'm doing something wrong. Haha. Here's the situation: - I am running a GP-wiz controller board for my 'cade - it has somewhere around 40-ish inputs - I use vJoy to simulate a "second" gamepad so that I can use the "one" controller as two controllers in Steam This all works absolutely fine. The configuration in MAME and RetroArch also work completely fine. The issue shows up that in setting the big box and launchbox mappings...it will not recognize any buttons past 16 for my GP-Wiz. I have opened the controller properties in Windows and sure enough, I press the button and it show's it's being pressed. It just might be button say 29. I was able to track down that it Big Box will recognize all the buttons UP to #16, after that, it does acknowledge them being pressed. My question is this, is that an internal constraint within Big Box because all the emulators are able to see all the buttons, it's only BB/LB that won't see all the buttons. Is it a configuration issue where I need to tell BB/LB it has more buttons? I'm completely stumped. I can work around this but requires me to do some wonky things for my navigation, Any thoughts anyone on what I can do or if they have seen this before? Thanks Tony