Today's developement versions beyond 5.0-3090

[labworkz98125]

To start this post, I would like to thank all members who had a hand in development of this fantastic emulator.

My post is about development versions beyond 5.0-3090.
-
For sum reason all the development versions I've tried before and including 5.0-3090 work fine. It's today's next versions that crash as soon as a Wii or GameCube game is selected to open.

Is there any thoughts on the reason for the crash. The older development versions work just fine in opening the Wii and GameCube games. The emulator immediately goes to the dolphin not working and then closing error message.

Thank you for inquiry.

[envisaged0ne]

Sure enough, it's happening on my end too. I'll play around with some settings to see if I can find something obvious causing it. But I can't launch a gamecube or wii game without the emulator crashing

EDIT: Well nothing to obvious is causing it. I tried different graphic backends, enabled & disabled every graphic option. Disabled cheats & Dual Core, etc. Pretty much adjusted every setting I could think of, but the emulator still crashes. Might be an internal bug that has to be fixed by the devs

[Korados]

I can confirm this, too! Since 5.0-3092, Dolphin crashes every time I try to start up a game, no matter if Gamecube or Wii.
And switching the setting also doesn't work. Sorry to be so bold, but I guess the devs messed something up.

[Mister Nobody]

Can confirm this as well, current version 5.0-3108 crashing as soon as I try to start a game. Was using 5.0-3052 previously and had no issues but can't say what build started the crashing bug.

[Mister Nobody]

Suggest the title of this post be changed to 'crashing issues with latest builds' as the current title doesn't bring enough awareness/attention for people who might be looking for the same reports...

[JosJuice]

This is a problem with the x64 JIT, and a fix is in progress.

[JosJuice]

Should be fixed by 5.0-3110.

[degasus]

Sorry, I've just tested this patch on linux. Dolphin was broken on Windows for everyone :/

It was an obvious bug, too ....

[labworkz98125]

I want to thank the development team for the swift reply and fix. The problem starts at versions 5.0-3092 and ends at version 5.0-3108. The problem is fixed at version 5.0-3110.