Emulator Issues #5067
closed
Rune Factory: Tides of Destiny - unable to pass cut scene where Odette shows big box in house
0%
Description
- Game Name and ID:
SO3EE9
2) What is the expected output? What do you see instead?
cut scene should continue to run, instead of that nothing happens, but game isn't hangs! animations still play and etc, just nothing happenes.
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.
there is no such problem in dolphin 3.0
4) What steps will reproduce the problem?
- start game
- play a few time
- you will notice when this happen
5) What version of dolphin are you using (32bit/64bit along with the
version as it appears in the title bar, etc)?
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.
that's all no matter since dolphin 3.0 does not have this problem.
version where this problem appeared is unknown.
and since dolphin went to GIT, i don't know the hell what version i using now. it has numbers 222, but i don't think they represents something.
6) Please provide any additional information below.
no additional info
- Attachments.
place where Odette stay forever: htt://segaempire.somee.com/files.hang.jpg
Updated by metafalica over 13 years ago
since can't edit my ticket... http://segaempire.somee.com/files/hang.jpg
Updated by hatarumoroboshi over 13 years ago
Ok, I found out that the last working revision is r3.0-71 - Revision c0dd84cf7d04
Using r3.0-73 - Revision 95517a974117 game gets stuck like in the foto (without error messages), so it may be somewhat related to issue 4906 (at least revisions affected seem to be the same).
In fact these issues are definitely due to r3.0-72 Revision 7812346c8973 (unfortunately unavailable for testing) or r3.0-73 Revision 95517a974117
Updated by metafalica over 13 years ago
nice bug hunt job! i hope this will help developers to fix this issue in new versions of dolphin
Updated by hatarumoroboshi over 13 years ago
Can someone test if this bug happens on a 64-bit O.S. as well?
Updated by metafalica over 13 years ago
sadly, i can't test, because don't have 64-bit O. S.
and looks like this ticket isn't that popular at all
Updated by arthas.menethill8 about 13 years ago
I also have this problem. I'm using x86.
Updated by moonlightofthenight about 13 years ago
i meet this problem too, i try to use from x86 version 3.0-367 to x86 version 3.0-413 but I still can't pass this cut scene near big box house ! Plese help me (My PC: laptop gateway core i5-430M, 512MB ATI Radeon HD 5470Mobility, RAM 4GB)
Updated by metafalica about 13 years ago
no one will help you here (even if developers has info about exactly from what doplhin version this problem appeared).
use dolphin 3.0 release. it works fine
Updated by hatarumoroboshi about 13 years ago
You mean 32-bit support will be dropped soon?
Updated by metafalica about 13 years ago
i mean that you found problematic version in second comment since when this bug started to happen, and developers do nothing about that. i don't know what could be easer then fix something that worked before, when you know what broke it.
it's like good old fatal frame 4 crash http://code.google.com/p/dolphin-emu/issues/list?can=1&q=fatal+frame&colspec=ID+Type+Status+Priority+Milestone+Owner+Summary&cells=tiles that exist for many years and peoples even showed code lines where it crashes, but no one fixes it.
Updated by skidau about 13 years ago
Please test out r70b6c4280f72. It might have fixed this issue.
Updated by hatarumoroboshi about 13 years ago
I kept the save-state right before the freeze, so as soon as I find the revision to download, I'm gonna report if this is fixed.
Updated by skidau about 13 years ago
Thank you, hatarumoro. Please note that using a save state will not positively identify that this issue is fixed because the bug itself might have been saved into the save state. Always retest issues like this from a in-game save.
Updated by delroth about 13 years ago
@hatarumoro: http://delroth.net/Dolphin-r70b6c4280f72.7z
Updated by hatarumoroboshi about 13 years ago
It worked for identifying r3.0-71 as safe, anyway I will start from beginning to be completely sure (in fact the freeze point is not really so far from it).
Updated by hatarumoroboshi about 13 years ago
Ok, tried from the very beginning, it works fine so this is fixed!