Dreamcast mvc2 crashing at stage 2
-
@tackett1980 You can try flycast, but honestly, get a pi4 and use redream for ~full speed dreamcast emulation.
-
@tackett1980 said in Dreamcast mvc2 crashing at stage 2:
The game does not crash with flycast, though the game functions much worse
In comparing the cpu/gpu specs between a pi3 and pi4, it seems that you should easily be able to overclock the pi3 to get to the same values (1500/500 MHz cpu/gpu) as the pi4 has without any overclocking.. and I can confirm that with no overclocking, the pi4 can run mvc2 in flycast pretty well. It's not as good as redream, but it's playable.
Can you run..
top -i -b -n 10 > topout.txt..and post the resulting topout.txt? That will take about 30 seconds to run.
Also..
vmstat -n 1 > vmstat.txtRun both of those while you're observing the slowness when playing the game in flycast.
I'm just wondering if your troubles are related to swapping, as opposed to insufficient cpu/gpu resources.
-
Also, regarding the links you posted.. it just seems like there was a defect in reicast that was fixed back in July.
However, I just tested this and I can confirm the same behavior with reicast at stage 2. So I would say this is not yet fixed. I'll try fiddling with the reicast settings a bit to see if that changes things. I assume the fix from July is in the current build provided by retropie.. that's something else to check on.
-
Just noting that I couldn't make the bad behavior go away in reicast by changing the settings. However, I also noticed that redream crashes with the game as well, but not until I reach level 3.. so it just takes longer with redream.
Maybe flycast will last longer.. might test that tomorrow. But it certainly looks like this game is tough for the emulators, and these issues should be reported.
Again, I have decent performance in flycast, so I'd be interested in your top & vmstat output.
-
I forgot..there is a ~10fps speed increase if you use the naomi version of mvc2 with flycast on a pi4. I haven't tested this on a pi3b+. I highly recommend you get a pi4, though. This hobby doesn't break the bank.
-
I will take a look at this and post results tommorrow.
I’d love to have a pi4, but there is no retropie install for it at the moment.
Edit:
My pi3, (not3b+) is overclocked to 1.5ghz.
And for fear of sounding really stupid...umm, how exactly step by step do I accomplish what you are asking me to do?
For a person trying to do this I’m totally computer illiterate. I’m kind of out of my element here.
-
@tackett1980 Sure, I can give you exact steps. Do you have another computer besides the pi? If so, let me know what kind it is (Windows/Mac/etc.). The instructions will be different depending.
Edit: also wanted to mention that I couldn't get it to crash using redream with a CDI version of the game. But it still consistently crashes every time using reicast. Flycast has frozen on me a couple times, but it hasn't crashed yet like the others.
-
Using an ancient PC.
-
@rejesterd said in Dreamcast mvc2 crashing at stage 2:
In comparing the cpu/gpu specs between a pi3 and pi4, it seems that you should easily be able to overclock the pi3 to get to the same values (1500/500 MHz cpu/gpu) as the pi4 has without any overclocking
This is incorrect. There may be 1% of pi3s that can boot at 1500mhz and also be stable, the ARM Cortex-A53 on the pi3 is already "overclocked" from the factory and has very little headroom for CPU overclocking. Remember also that the pi4 is a completely different CPU (ARM Cortex-A72). Even if you underclocked the pi 4 to 1200mhz to match the pi 3 it would still be considerably faster than the pi3. The GPU on the pi 4 is a Videocore VI while the pi 3 is a videocore IV, the performance difference is immense, again even if you set them both to the same clock speed. You'll never be able to make the pi 3 match a pi 4's performance by overclocking.
-
So after all my fiddling and observations so far, I really think this crashing issue is related to saving data to the VMU file. When you reach a new level in the game, it seems the emulator tries to write to the vmu and is unsuccessful.
For instance, if I launch the game with flycast, select a memory card slot, then go and delete the vmu files under ~/RetroPie/BIOS/dc/, the game will crash right after I select my characters and am about to play stage 1. Of course that's expected to happen for any game using a vmu, but the timing of the crash (and where in the game it happens) is very similar to the case where I don't mess with the vmus and simply reach stage 2 or 3 (depending on which emulator is being used).
I still need to collect more data before reporting it, but that my take on it so far.
-
My pi3 has an older version of reicast and I was able to make it to the 2nd stage without crashing. You might be able to take my reicast binary and swap it out on your pi.
https://mega.nz/#!9ZBBjSCZ!DEetDT-HYLEdByt5o2xYcv5uW3kb8HiiuO7yApzgX6U
Place it in:
/opt/retropie/emulators/reicast/bin/I would recommend backing up your reicast binary first before replacing.
-
@quicksilver Good to know.. when I was reviewing the specs last night, my tired eyes couldn't tell the difference between Roman numerals VI and IV lol.
@tackett1980 I think we can forget the tests I mentioned, as I seriously doubt you are swapping. Plus, I don't think the results from those tests would guide you to a configuration that avoids this particular crash.
-
@quicksilver btw I did test with your binary, but it won't launch the game. In the runcommand log, I get..
Parameters: Executing: /opt/retropie/emulators/reicast/bin/reicast.sh alsa "/home/pi/RetroPie/roms/dreamcast/Marvel vs. Capcom 2.chd" 640 480 Virtual cfg config:homedir=/home/pi Virtual cfg x11:fullscreen=1 Virtual cfg x11:width=640 Virtual cfg x11:height=480 Virtual cfg audio:backend=alsa Virtual cfg audio:disable=0 Virtual cfg config:image=/home/pi/RetroPie/roms/dreamcast/Marvel vs. Capcom 2.chd Config dir is: /home/pi/.reicast/ Data dir is: /home/pi/.reicast/ Personality: 00C00000 Updated personality: 00800000 found libbcm_host rpi2: bcm_init ARM VFP-Run Fast (NFP) enabled ! Linux paging: 4096 00001000 00000FFF MAP 00800000 w/ 25165824 MAP 20000000 w/ 25165824 MAP 04000000 w/ 16777216 -
@rejesterd what version of raspbian is your pi 3 on? Or you using an old image?
-
@quicksilver I'm on a pi4.. very recent image from about a month ago.
-
@rejesterd do you have any more info about the crash? I've not heard of a crash from this game in ages, but would love to see the stdout after it crashes if you can snag it. To note, I pushed a fix a few nights ago that addresses a silly shader compilation error (literally, a typo) that'd been hanging around for a few weeks and effected some games with fog.
-
@rejesterd said in Dreamcast mvc2 crashing at stage 2:
@quicksilver I'm on a pi4.. very recent image from about a month ago.
Then a binary compiled for the 3b model won't work, since it uses the legacy video drivers.
-
I’m on the way home from work I can try to get the information you need if someone can walk me through how to obtain it.
-
@tackett1980 he's referring to the crashing behavior on redream not reicast.
-
Well, I gotta quit for the time being (I'm so sick of this game now lol), but here is what I've learned.
It consistently crashes in reicast every time when you reach the second stage (and in rare instances, it will crash even before then). The runcommand.log shows:
Parameters: Executing: /opt/retropie/emulators/reicast/bin/reicast.sh alsa "/home/pi/RetroPie/roms/dreamcast/Marvel vs. Capcom 2.chd" 640 480 ALSA: underrun occurred ALSA: underrun occurred /opt/retropie/emulators/reicast/bin/reicast.sh: line 35: 7380 Trace/breakpoint trap "$rootdir/emulators/reicast/bin/reicast" "${params[@]}"Note that if I run the game in reicast with sound disabled, the underrun messages go away, but the crash still occurs and the last line in the log is the same. So I don't think it's related to audio. I added these details to issue #1684.
In redream, the crash is not as consistent as you advance through stages (I made it to stage 3 many times and the game never crashed). However, I am able to get redream to crash pretty consistently right away if I just rapidly press B to select my characters and the game mode (turbo or normal). Doing that rapidly causes a crash before match 1 begins. So I reported that to inolen as issue #967. Hopefully he can fix it for redream. Not sure how much attention it will get from the reicast folks, as it's an old issue.. seems like they thought it was fixed back in July, but apparently not (or this is just a new crash profile).
Cheers.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.