In GitLab by @secretseal on Feb 7, 2020, 06:36
## Summary
<!--- Provide a general summary of the issue in the Title above -->
Controllers using Brook PS2-->PS3/4 adapter are not found as an input by BT4/5 and cannot bind any buttons within config.exe
## Expected behavior
<!--- Tell us what should happen -->
When using the adapter, BT would recognize its inputs.
## Current behavior
<!--- Tell us what happens instead of the expected behavior -->
BT does not recognize inputs from controllers using the Brook adapter.
## Steps to reproduce
<!--- Provide a detailed step by step description how to reproduce this issue -->
1. Buy a Brook PS2-->PS3/4 Adapter
2. Connect a controller to the adapter
3. Connect the controller + adapter to your computer via USB
4. Open Bemanitools 4 or 5
5. Attempt to bind a button
## Possible solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
Unsure but BT may be filtering out/not looking for
## Context (Environment)
### Bemanitools version(s) affected
* <!--- Add one or multiple versions as a bullet list -->
* 4 (assumed all)
* 5 (assumed all)
### Game(s) and version(s) affected
* <!--- Add one or multiple game versions as a bullet list -->
* Pop'n Music (using KOC minicon)
* IIDX (using KOC, version unknown) (from another user in Discord, who also has the issue)
### Log output
See attachment.
<!--- Provide log output as attachment. Make sure to censor sensitive data like PCBIDs or device names if necessary -->
No log as the issue exists in the config exe.
### Configuration files
See attachment.
<!--- Provide any configuration files that you used, e.g. iidxhook-XX.conf. Make sure to censor sensitive data like
PCBIDs -->
No attachments
### OS version
<!--- Provide the version of Windows you used with whatever update/build identifier -->
W10
### Hardware specs
* Controller: KOC V2 Pop'n Minicon, IIDX KOC (version unknown)
PS3/4 controllers aren't properly exposed to dinput iirc.
Does it work if you install something like ds4windows?
In GitLab by @xyen on Feb 7, 2020, 20:53
PS3/4 controllers aren't properly exposed to dinput iirc.
Does it work if you install something like ds4windows?
Just tried -- DS4Windows does not recognize the Brooks adapter as a DS4, so it doesn't seem to have an impact.
In GitLab by @secretseal on Feb 8, 2020, 20:06
Just tried -- DS4Windows does not recognize the Brooks adapter as a DS4, so it doesn't seem to have an impact.
Otherwise, pull requests would be appreciated if this is something you'd like to integrate directly into BT.
In GitLab by @xyen on Feb 8, 2020, 22:17
Does the controller show up in anything else?
Otherwise try this maybe:
https://github.com/ViGEm/FireShock
Otherwise, pull requests would be appreciated if this is something you'd like to integrate directly into BT.
That also didn't seem to work -- I don't think the driver itself is the issue, as the windows gamepad tool is finding it just fine, and Spicetools as well is able to pick it up without incident.
I just tried mapping in a few emulators as well (ePSXe and no$psx) and they were both able to map the controller just fine, so it does seem that this is something isolated to btools
In GitLab by @secretseal on Feb 8, 2020, 22:28
That also didn't seem to work -- I don't think the driver itself is the issue, as the windows gamepad tool is finding it just fine, and Spicetools as well is able to pick it up without incident.
I just tried mapping in a few emulators as well (ePSXe and no$psx) and they were both able to map the controller just fine, so it does seem that this is something isolated to btools
Checked a few other places and Dolphin seems to report it as Dinput, similar to my Yuancon:
In GitLab by @secretseal on Feb 9, 2020, 19:04
Checked a few other places and Dolphin seems to report it as Dinput, similar to my Yuancon: 
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In GitLab by @secretseal on Feb 7, 2020, 06:36
Summary
Controllers using Brook PS2-->PS3/4 adapter are not found as an input by BT4/5 and cannot bind any buttons within config.exe
Expected behavior
When using the adapter, BT would recognize its inputs.
Current behavior
BT does not recognize inputs from controllers using the Brook adapter.
Steps to reproduce
Possible solution
Unsure but BT may be filtering out/not looking for
Context (Environment)
Bemanitools version(s) affected
Game(s) and version(s) affected
Log output
See attachment.
No log as the issue exists in the config exe.
Configuration files
See attachment.
No attachments
OS version
W10
Hardware specs
In GitLab by @xyen on Feb 7, 2020, 20:53
PS3/4 controllers aren't properly exposed to dinput iirc.
Does it work if you install something like ds4windows?
In GitLab by @secretseal on Feb 8, 2020, 20:06
Just tried -- DS4Windows does not recognize the Brooks adapter as a DS4, so it doesn't seem to have an impact.
In GitLab by @xyen on Feb 8, 2020, 22:17
Does the controller show up in anything else?
Otherwise try this maybe:
https://github.com/ViGEm/FireShock
Otherwise, pull requests would be appreciated if this is something you'd like to integrate directly into BT.
In GitLab by @secretseal on Feb 8, 2020, 22:28
That also didn't seem to work -- I don't think the driver itself is the issue, as the windows gamepad tool is finding it just fine, and Spicetools as well is able to pick it up without incident.
I just tried mapping in a few emulators as well (ePSXe and no$psx) and they were both able to map the controller just fine, so it does seem that this is something isolated to btools
In GitLab by @xyen on Feb 9, 2020, 12:47
Do any of the things it works in say if the device is picked up as dinput or xinput?
In GitLab by @secretseal on Feb 9, 2020, 19:04
Checked a few other places and Dolphin seems to report it as Dinput, similar to my Yuancon:
In GitLab by @mjt112 on Dec 3, 2021, 05:00
Anyone ever able to get this working?