Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Join USB and Bluetooth to one mode for PS3 sixaxis controller #148

Open
beaumanvienna opened this issue Nov 19, 2014 · 3 comments
Open

Join USB and Bluetooth to one mode for PS3 sixaxis controller #148

beaumanvienna opened this issue Nov 19, 2014 · 3 comments

Comments

@beaumanvienna
Copy link
Contributor

I think we have this already to some extend. I noticed this accidentally today. Wouldn't that be a nice feature?

@mdeguzis
Copy link
Owner

mdeguzis commented Dec 1, 2014

How do you propose we do this? I suppose gp_autodetect could unload/load services based on what it detects on the system in lsusb or other active logging in the operating system. Since we have xboxdrv and sixad, there would have to be some sort of juggling of things, not to mention the controller mappings are different, for one. This is why it is still a seperate settings option in setup and otherwise.

Did you stumble upn something? Take not that if you did, be sure to check jstest-gtk before and after to confirm you are not actually using the hid_sony kernel module, and xboxdrv instead.

@beaumanvienna
Copy link
Contributor Author

[..] not to mention the controller mappings are different, [..]

That could be handled in xboxdrv or antimicro.

Currently we have four modes. Couldn't that be reduced to two modes? (PS3 BT and the rest?) There's no difference between the three xboxdrv-modes, or is there?

Can't we run xboxdrv and sixad at the same time? Like a trackpad and mouse as two different input sources for the mouse pointer.

When it comes to the amount of PS3/USB or XBox360 controllers that have to be stated in the setup, we should find an automatic solution.

I think alls that we have to do is to get the PS3/BT pairing done in the setup.

@mdeguzis
Copy link
Owner

mdeguzis commented Dec 2, 2014

Currently we have four modes. Couldn't that be reduced to two modes? (PS3 BT and the rest?) There's no difference between the three xboxdrv-modes, or is there?

The reasoning is to keep gamepads separate. I don't want to assume a pad will just work, and this also makes identifying the gamepads in the gamepads.shinc module and other areas more difficult and abstract. (lots of renames of folders/files from xbox360_usb_controller to xbox_compatible_controller?). Buttons on knock off controllers may assume different buttons, the device may not get identified right. But...I def. see your point. Some* gamepad configurations are the same, but some between wireless xboxdrv and xboxdrv over usb are not.

Can't we run xboxdrv and sixad at the same time? Like a trackpad and mouse as two different input sources for the mouse pointer.

I think so, but why? To mix controllers?

When it comes to the amount of PS3/USB or XBox360 controllers that have to be stated in the setup, we should find an automatic solution.

That is true. The defaults file for xboxdrv under /etc/defaults/xboxdrv sets up how many are enabled. It's just the method I have right now. I think in the past, if the improper number was stated, you wouldn't be able to enable all the controllers, or too many would show up in jstest-gtk, I think causing problems in games that have 2-4 player select screens. Not sure, it would need tested again (use a game like Mortal Kombat). Counting the number of controllers connected would need some rework. Sure, logs show connected devices, but pining down how many* devices is another thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants