Emulator Issues #3536
closed
Donkey Kong Returns doesn't boot on newer revisions due to FIFO bug
0%
Description
What's the problem?
Donkey Kong Returns doesn't boot on newer revisions
Dolphin version with the problem (as it appears in the title bar, Ex.: "R
4779" or "R 6403M"): any revision above r5696
(optional) Dolphin version that does not have the problem:
Any revision below that, off course. But don't go way back too much :P
Operating system and version: Win 7
32-bit or 64-bit: x64
Game ID (as it appears in game properties, Ex.: "GZ2P01" or "RSBE01"): SF8E01
Please provide any additional information below.
Well, it seems that FIFO changes made in r5699 killed the game, same as Super Monkey Ball Banana Blitz, Super Monkey Ball Step & Roll and Pokemon XD.
Skidau stated that info. I'm only sure about DKR 'cos I don't own the other games.
There is an issue with sound in cinematics also. Maybe using the newer revisions with the new Xaudio2 backend should solve it. But we have to wait for the FIFO fix first.
Well, That's it. Thanks again for the great emu. ^^
Updated by frango0010 about 14 years ago
Have you tried raising the Watermark Tightness on the game properties?
Updated by frango0010 about 14 years ago
Have you tried raising the Watermark Tightness on the game properties?
Updated by razi3l13 about 14 years ago
i have the same problem.tried to raise Watermark Tightness and there isn't any change
Updated by rodiabloalmeida about 14 years ago
Changing watermark tightness doesn't help. Already tried that before reporting the issue. I should've mentioned that in the details. :P
Updated by dev.mohammed about 14 years ago
i can not play the game on an OLD revision also because i have Nvidia GT 240 and there was a known issue with this card and it have been Solved in revision 6252 so we need to play this game on a new revision.
Please developer help us to fix the Problem ( if i was a C++ Developer i would really help but Unfortunately i'm a VB.Net Developer :) ) and ofcourse thank you guys for this great Emu.
Updated by
Updated by skidau almost 14 years ago
- Status changed from New to Fixed
This issue was closed by revision r6461.
Updated by rodiabloalmeida almost 14 years ago
Thanks very much, skid. I didn't expected the fix coming so soon. :)