Emulator Issues #2563
closedSuper Robot Taisen GC (J) Hangs At Battle Scene When Enemy Exploding, Or when using Specific Attack
0%
Description
What steps will reproduce the problem?
1.Start game, turn battle animation on
2.begin a battle which will ended in one of the participant being destroyed
3.watch the battle until one of the participant exploding from the dying
animation, it will always hang with the image stop moving and audio stuck
in a loop (it dosen't always happen though, only with specific units it
will happen, some attacks also has the same affect, so the hang will
happen during the attack animation)
What is the expected output? What do you see instead?
The battle should end normally after the animation completed and the game
should go back to the map screen.
What version of the product are you using? On what operating system?
I can't check them all, but I think any build at least from r5000 and up
were affected, most likely goes a lot deeper than that. I currently
running r5348 on a Win 7 64 os, 260gtx, core 2 duo e6320 machine, any help
will be appreciated.
Please provide any additional information below.
Updated by STLZ0001 over 14 years ago
Managed to trace it back to between r4748 which was working normally as far as I can
tell, to r4775 in which several warning window pops out, first line being: GFX FIFO:
(0x4), second window first line: Illegal command 04, then third: GFX FIFO:(0x42),
Illegal command 42, lastly: GFX FIFO:(0x41), Illegal command 41. Can't pinpoint the
exact revision to start having the problem yet, the latter's warning windows doesn't
appear on newer versions, but the hanging remains.
Updated by Anonymous over 14 years ago
I would try r4758 and r4759 first, to see if r4759 broke it.
Updated by Anonymous over 14 years ago
Issue 2289 has been merged into this issue.
Updated by STLZ0001 over 14 years ago
Thank you for the attention, no rush either, looking forward to a perfect emulator
this will eventually become due to all your hard work!
Updated by Anonymous over 14 years ago
- Status changed from New to Duplicate
Merging this into issue 2579, since it has more games listed that are affected :)