Emulator Issues #409
closed
Tatsunoko vs. Capcom dolphin must now close issue ..non playable
0%
Description
What steps will reproduce the problem?
1.selecting arcade mode
2.selecting vs, survival, or time attack mode
3.demo battles with 4 characters will make dolphin freeze
What is the expected output? What do you see instead?
Dolphin turns black then freezes. I see pretty much nothing after that
excpet starting over the emu.
What version of the product are you using? On what operating system?
Using dolphin version 1556
Please provide any additional information below.
I noticed a fps increase in the game ...GREAT JOB...Also
the min-games work fine by the way.
Updated by apricotcrow about 16 years ago
I have been able to see a few 4 character battles, and it has crashed for 3 character
battles. So I'm not sure that is a factor. I have a very low chance of even getting
to the demo battle though, mostly it just crashes :/
Specs: Win XP 32bit, E8400(3ghz dual core), 2gb ram, 9800GT
Updated by cadiblack about 16 years ago
i always can view the 3 character battles , thats very ODD
and just 4 hours ago i watch 2 back to back 3 character battles
then it froze on the 4 character battle. i tryed to record it but my fraps was
the demo version at the time. I will try to make a video again.
Updated by apricotcrow about 16 years ago
Actually, my experiences were based on the rev that was out when tatsunoko was
released(I even took some screens of 2v2 matches in action)... I tested some with a
newer rev now(1557) and had the same experience you have pretty much... 4 never
loads, 3 pretty much always (but often it just presents one side and then just stop
there... animations still play and you can press button to return to main menu, but
there is no actual fight). Weird.
Updated by cadiblack about 16 years ago
i found a real wii game debugger that might help in figuring out the problem
i hope this helps u guys
http://wii.qj.net/Debug-your-games-WiiRD-GeckoOS-first-public-release/pg/49/aid/121450
Updated by hyperiris almost 16 years ago
due to some trace work, I can figure out these:
Last game DI activity Log, some UnknownCALLs
DVDLowClearCoverInterrupt
: /dev/di - Command(0x00000086) BufferIn(0x133e2560, 0x20) BufferOut(0x00000000, 0x0)
DVDLowRead
: /dev/di - Command(0x00000071) BufferIn(0x133e2580, 0x20) BufferOut(0x00000000,
0x4f7e0)
: DVDLowRead: snd\se\se_csl.whd (0x4f7d2) - (DVDAddr: 0x0, Size: 0x64f53c60)
UnknownCALL
: /dev/di - Command(0x000000e0) BufferIn(0x133e25a0, 0x20) BufferOut(0x003d0620,
0x20)
DVDLowClearCoverInterrupt
: /dev/di - Command(0x00000086) BufferIn(0x133e2540, 0x20) BufferOut(0x00000000, 0x0)
DVDLowRead
: /dev/di - Command(0x00000071) BufferIn(0x133e2560, 0x20) BufferOut(0x00000000,
0x4f7e0)
: DVDLowRead: snd\se\se_csl.whd (0x4f7d2) - (DVDAddr: 0x0, Size: 0x64f53c60)
UnknownCALL
: /dev/di - Command(0x000000e0) BufferIn(0x133e2580, 0x20) BufferOut(0x003d0620,
0x20)
UnknownCALL2
: /dev/di - Command(0x00000095) BufferIn(0x133e25a0, 0x20) BufferOut(0x003d0720,
0x20)
DVDLowStopMotor
: /dev/di - Command(0x000000e3) BufferIn(0x133e2540, 0x20) BufferOut(0x003d0620,
0x20)
Updated by hyperiris almost 16 years ago
- Status changed from New to Questionable
Updated by hyperiris almost 16 years ago
we ca see, in DVDLowRead, BufferOut address is 0x00000000, so it was failed.
I guess the UnknownCALL may be try do some kind of "clear error state",
and UnknownCALL2 may be try to reset the laser len pos, then game call
DVDLowStopMotor to stop Drive and halt.
Updated by hrydgard almost 16 years ago
- Status changed from Questionable to Work started
Um, this ain't a "questionable" bug. Setting status to Started.
Updated by Ismael.A.Bartleboom almost 16 years ago
NOW TATSUNOKO VS CAPCOM PLAYABLE SVN VERSION 2656-57