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

[Bug] Cemu crashes in every Skylanders game with a connected portal of power #1058

Closed
Miaush opened this issue Jan 7, 2024 · 2 comments
Closed

Comments

@Miaush
Copy link

Miaush commented Jan 7, 2024

I wanted to play Skylanders again after some time and Cemu updates.
For me the bug happened on Cemu 2.0-61, the latest version right now, and according to a reddit post I've found is „fixable“ by downgrading to 2.0-47, in which version the games don't crash after selecting a language or even before that.

Steps to reproduce:

  1. Connect Portal of Power and install the drivers in device manager (USB Input Device)
    1.5. Try to launch a game without the portal connected to see if it crashes. It should not crash but rather show the message to connect a portal.
  2. Launch the game. It will now crash if you are using one of the newer Cemu versions (every version since 2.0-47 probably)

This crash has nothing to do with the crash happening when using Superchargers/Imaginators + the Updates with an Online Account. (just disable online mode to fix it)

Until now I couldn't really find anything useful in the logs, but it probably has something to do with changes to the way USB devices are handled by cemu.

The only fix for me was to downgrade the Cemu version to 2.0-47.

I have tested all of the 6 games with the newest Cemu version, and the bug is present in every game and at the exact same point. Either after selecting a language for the games that support multiple languages, or directly on launch.

@TheRealWario
Copy link

Its a known issue. Indeed, this is caused by a PR that attempted to change the usb support to be usable with zadig drivers, like dolphin has. Unfortunately, as you seem to have noticed, it broke the functionality entirely. It needs someone to look into it, but it may be a while.

@Squall-Leonhart
Copy link
Contributor

You can close this, the issue as stated is known and the fix is included in a changeset in the PR already.

@Miaush Miaush closed this as completed Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants