Emulator Issues #5382
closed
Zelda WInd Waker crash using LLE with almost every audio plugin setting
0%
Description
- Game Name and ID (as it appears in right click > properties: "GZ2P01",
"RSBE01", etc):
The Legend of Zelda: the Wind Waker - GZLE01
2) What is the expected output? What do you see instead?
I expect to be able to start the game with every audio plugin setting, instead using LLE + Xaudio2 (32000 and 48000 hz) and Dsound (only 32000) the game crashes at the first or second introduction "movie" with the message ERROR:COMPILING AT 0. LR=00000000 CTR=803226b4
3) Did the game ever work correctly (i.e. not have this problem) on an
earlier version of dolphin? Please specify the exact revision when the
problem began.
Not easy to tell...seems that r3.0-555 works fine while r3.0-583 is broken, but I still need some more time to find out the exact revision that caused this issue.
4) What steps will reproduce the problem?
- launch the game
- go through the first introduction, if it doesn't already crash start a new game, watch the second introduction and here you'll get the message ERROR:COMPILING AT 0. LR=00000000 CTR=803226b4
5) What version of dolphin are you using (32bit/64bit along with the
version as it appears in the title bar, etc)? Do not say 'latest version'
this changes multiple times a day.
On what operating system, drivers, and hardware? Be sure to list OS,
graphics driver information, and video card model if you are having
graphics problems, for example.
Dolphin r3.0.594 32-bit Revision: 8ff395406932 on Windows XP SP3, Ati hd4850 Catalyst 11.12, E8400, Sblaster Xfi
6) Please provide any additional information below.
HLE doesn't seem to be affected.
Usng LLE, DSound with 48000 hz is the only safe plugin setting (doesn't seem to be affected as well)...the problem is reproducible especially when using the AUDIO framelimiter, the AUTO frameliter seems to lessen a bit the probability of the error.
Updated by hatarumoroboshi about 12 years ago
Further testing showed that DSound 48000 is somewhat less affected (but still affected) and r 3.0-555 is not error free...
Updated by pauldacheez about 12 years ago
I'm not sure if this is related, but, on OS X using LLE Recompiler I'm getting "ERROR: Compiling at 0. LR=00000000 CTR=80324a7c" before the title screen appears, under "No audio output" (!) and OpenAL at 48k and 32k and under CoreAudio at 32k. LLE CoreAudio at 48k and all forms of HLE audio are fine. (Well, for the title screen, at least. I'm not gonna test any further into the game or with LLE Interpreter until I have the time.)
(OS X 10.7.3, Dolphin 3.0-600. System Profiler reports that this MacBook Air has "Intel High Definition Audio", while iFixit's teardown specifies that the audio controller is a Cirrus 4206BCNZ. Useless info, I know, but I felt like providing it.)
Also, I found another minor bug that I've just filed Issue 5383 for.
Updated by hatarumoroboshi almost 12 years ago
From my tests r3.0-484 Revision 5e2fd4520302 should be ok and r3.0-486 Revision 6202714efdf6 should be "broken", so in my opinion the latter seems to be responsible, because r3.0-485 (I cannot find it) is only a gameini update.
Could someone confirm that revision 6202714efdf6 can cause such an issue? And why HLE isn't affected?
Updated by hatarumoroboshi almost 12 years ago
Too early got an ERROR:COMPILING AT 0. LR=00000000 CTR=803226b4 in r3.0-484 after 5 times free...now back from the start.
Updated by hatarumoroboshi almost 12 years ago
Well this should be the definitve report: I couldn't experience any problems with r3.0-465 Revision 281d7531a3d9 so the first available revision that has the problem is r3.0-484 Revision 5e2fd4520302 (unfortunately I couldn't find any other revision between them)
Updated by skidau almost 12 years ago
Would you please test this issue with the Jit-Exceptions branch?
You can find builds here:
http://www.emucr.com/2012/04/dolphin-jit-exceptions-git-30-592.html
Updated by pauldacheez almost 12 years ago
Fixes my bug, on all backends and bitrates.
Updated by skidau almost 12 years ago
Would you be so kind to add a comment under r13b66df12535 to that effect so that it does not look like I am merging the branch for no reason?
Updated by pauldacheez almost 12 years ago
Huh. You can't just merge it and say that in the merge message, or as the first comment?
Oh well, I commented anyway.
Updated by skidau almost 12 years ago
- Status changed from New to Fixed
This issue was closed by revision 75fbbcae4003.