Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
09394 Crash/Freeze Critical (emulation) Always 5 days ago 2 days ago
Tester vidpro1 View Status Public Platform MAME (Official Binary)
Assigned To Resolution Open OS Windows (x64)
Status [?] Confirmed Driver
Version 0.286 Fixed in Version Build x64
Fixed in Git Commit Github Pull Request #
Summary Regresssion 09394: fvipers, fvipersb, schamp, sfight: Coprocessor error on bootup
Description Fighter Vipers Sega Model 2 will not get past the bootup screen. Coprocessor Error.
Steps To Reproduce
Additional Information
Github Commit
Flags Regression
Regression Version 0.286
Affected Sets / Systems fvipers, fvipersb, schamp, sfight
Attached Files
png file icon 0001.png (3,576 bytes) 5 days ago Uploaded by vidpro1
vidpro1
Relationships
There are no relationship linked to this issue.
Notes
6
User avatar
No.24171
Osso
Moderator
5 days ago
It's marked as MACHINE_NOT_WORKING; this isn't a valid report according to rule 10 of MAMETesters.
User avatar
No.24172
Robbbert
Moderator
4 days ago
This is a regression. It works with -nodrc
User avatar
No.24174
Osso
Moderator
4 days ago
Some discussion about this between gm-matthew and Vas che can be found here: https://github.com/mamedev/mame/commit/9c1eb3d13371a108eaa11fe0c31396bc321a33a5#commitcomment-177502323
User avatar
No.24175
Robbbert
Moderator
4 days ago
Just noticed there's a post at bannister from Vas about it too, so he's already aware of it. But here is the proper place for this kind of problem to be stored, so we'll leave it open until Vas is satisfied that it works at least as well as it was before.
User avatar
No.24176
georgc3
Tester
4 days ago
This issue also affects Sonic Championship. All Sonic Championship variants (and their clones), as well as Fighting Vipers and their clones, are affected by the same Model 2 coprocessor error message. The rest of the Sega Model 2 games I tested run and work fine.
User avatar
No.24193
yoshi200213
Tester
2 days ago
hello
the regression happened in the commit 9c1eb3d
https://github.com/mamedev/mame/commit/9c1eb3d13371a108eaa11fe0c31396bc321a33a5