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

[Regression] Real DJ Hero turntable's inputs no longer recognized if an emulated turntable is enabled #13504

Closed
shockdude opened this issue Mar 6, 2023 · 2 comments · Fixed by #13578

Comments

@shockdude
Copy link
Contributor

Quick summary

A real DJ Hero turntable was previously able to work at the same time as an emulated turntable, for local multiplayer in DJ Hero 2.
As of v0.0.26-14609-7648171f (#13268), if an emulated turntable is used, a real turntable no longer responds to input.

Details

  • Configure a real DJ Hero turntable by installing the WinUSB driver with Zadig
  • Enable an emulated turntable, in Config > I/O
  • Boot DJ Hero 2
  • Emulated turntable responds ingame, real turntable no longer responds.

Build with regression

v0.0.26-14609-7648171f

Attach two log files

RPCS3-real&emulatedtable-14606.log.gz - both real & emulated table respond ingame
RPCS3-real&emulatedtable-14609.log.gz - only emulated table responds ingame, real table's inputs are ignored.

Attach capture files for visual issues

No response

System configuration

Windows 10 22H2
Intel i7-4720HQ
Nvidia GTX860M, Driver 528.02

Other details

Another user confirmed that using 2 real turntables still works fine on v0.0.26-14609.
Their logs are attached:
RPCS3-2realtables-14606.log.gz
RPCS3-2realtables-14609.log.gz

@shockdude
Copy link
Contributor Author

Forgot to note: using only a real turntable in single player works fine. Likewise, using only an emulated turntable in single-player works fine.
The problem is using both a real turntable & an emulated turntable (game no longer responds to real turntable's inputs)

@RipleyTom
Copy link
Contributor

RipleyTom commented Mar 24, 2023

Pretty sure it's a side effect of #11192.

With non-blocking on normal usb it's processing all the events for the fake usb instantly which means it always has something processing. The game probably loops handling all the events for fake device constantly because it queues a request instantly after getting a reply which means it always has something to do with that device and the processing never switches to the real device(in the game logic I mean).

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

Successfully merging a pull request may close this issue.

3 participants