SteveB69 Posted November 5, 2019 Share Posted November 5, 2019 Hi, I've paid up for the one year and am having an issue with my 2 x zero delay encoders. Both work fine in everything but in LB / BB which fails to identify which zero delay encoder it is coming through so regardless if I map Button 1 on zero delay encoder 1 it becomes Button 1 but if I map something else using Button 1 on zero delay encoder 2 it is labelled Button 1, no different identification so both buttons, whilst mapped to different controls do the same thing. Have googled & searched this but can't find any solutions? Quote Link to comment Share on other sites More sharing options...
DOS76 Posted November 5, 2019 Share Posted November 5, 2019 I think that is due to it being seen as a D-input device I have the same encoders and I only use one to control LB/BB. I don't know if you will have any options beyond that. Quote Link to comment Share on other sites More sharing options...
Retro808 Posted November 5, 2019 Share Posted November 5, 2019 Same boat here. On a couple cabinets I have similar encoders. No real work around right now. Thankfully those two cabinets I only use Mame so I make sure Mame is mapped as I want. Mame does see them as Joy1 and Joy2 so things inside Mame work fine. I am not sure if this is something @Jason Carr ever really looked into. So I will tag him just in case. Especially since he expanded the controller mapping options. Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted November 5, 2019 Share Posted November 5, 2019 Am I understanding correctly that you have a controller board that basically acts like two separate game controllers? Assuming that is correct, I think the only way we would be able to manage something like that is to add controller-specific bindings to each option. That's possible, but it would be a fairly significant new feature to add. Quote Link to comment Share on other sites More sharing options...
Retro808 Posted November 5, 2019 Share Posted November 5, 2019 Not sure if this is exactly the same as for the original poster. I have two of these style encoders. Each is a unique usb plugged into the pc. Windows sees them both only as "USB Generic Joystick". No numeric separation. In Mame they are seen as Joy1 and Joy2 so you can easily map player 1 and player 2 with no conflict. Launchbox however sees them as the same joystick. So for example the button I use for P1 start button, LB sees it only as "Button 12". If I hit the start button on the P2 side LB sees it as well as only "Button 12". Quote Link to comment Share on other sites More sharing options...
SteveB69 Posted November 6, 2019 Author Share Posted November 6, 2019 Oh good, well at least I know it's not my setup. Jason Carr, no not one controller board but 2 seperate boards, each plugged into it's own USB port. Windows see's both as USB Generic Joystick and in Mame / emulators they identify as Joy 1 or Joy 2, but in launchbox there's no numeric identification. Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted November 7, 2019 Share Posted November 7, 2019 I see. It's still the same issue. LaunchBox and Big Box don't currently make any distinction between inputs from different controllers, and we'd have to make significant changes to the interface and the backend to support that. Is there a reason why the controllers need to act as game controllers and not keyboard-based devices? Quote Link to comment Share on other sites More sharing options...
DOS76 Posted November 7, 2019 Share Posted November 7, 2019 its not that they act like game controllers its that they are game controllers each controller has its own encoder board and they take up two USB ports on your PC. Quote Link to comment Share on other sites More sharing options...
Rincewind Posted November 7, 2019 Share Posted November 7, 2019 I have them too and I'm pretty sure Retroarch sees them as joy1 and joy2 also Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted November 7, 2019 Share Posted November 7, 2019 LaunchBox sees them as separate controllers as well, of course. Always has. But there's no way to map controllers differently between them currently in LaunchBox. Which, I suppose, in most cases is fine, because it just means that player 2 will have the same controls as player 1. But if you want it to work differently, that's not currently supported. Quote Link to comment Share on other sites More sharing options...
SteveB69 Posted November 9, 2019 Author Share Posted November 9, 2019 On 11/7/2019 at 9:45 PM, Jason Carr said: LaunchBox sees them as separate controllers as well, of course. Always has. But there's no way to map controllers differently between them currently in LaunchBox. Which, I suppose, in most cases is fine, because it just means that player 2 will have the same controls as player 1. But if you want it to work differently, that's not currently supported. Jason it doesn't affect gaming as the controllers are set up via the emulator running them, what it affects are the controls for LB/BB ie I have 2 buttons on my cab that are mapped to Volume Up & Volume Down. The way I have done my wiring is that both my volume buttons are connected to Button 8 & obviously I can't use button 8 for both Vol up & down. So it would have been nice to have Page Up & Page Down mapped to my 2 player buttons but I can't because these buttons are already mapped to player one controls. Shame & strange considering every emulator out there & windows picks these up as seperate encoders. Quote Link to comment Share on other sites More sharing options...
DOS76 Posted November 9, 2019 Share Posted November 9, 2019 LB sees them as separate too the issue is that LB only takes commands from one controller so if you had one Zero Delay and one XBox controller you still couldn't map them separately they would still do the same thing. In other words you can't map separate functions to different controllers 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.