Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
03175 Crash/Freeze Critical (emulation) Always May 13, 2009, 01:03 Aug 6, 2009, 15:57
Tester Tafoid View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Fixed OS Windows 2000
Status [?] Resolved Driver
Version 0.131u1 Fixed in Version 0.133u2 Build Normal
Fixed in Git Commit Github Pull Request #
Summary 03175: cham24: Game doesn't start correctly
Description All you see is a gray screen and the normal menu which is presented with the selectable games is not shown. Even if this is a game_not_working, it's a clear and major regression.
Steps To Reproduce
Additional Information
Github Commit
Flags
Regression Version 0.130u4
Affected Sets / Systems cham24
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
1
User avatar
No.04429
etabeta
Developer
Jun 1, 2009, 16:37
edited on: Jun 1, 2009, 17:51
This is the same issue affecting MESS emulation of nes/famicom.

Among other things, the old PPU code required a VROM region to be set or not at init, depending on the mapper of the game. The new code passes the region tag in the device interface, hence such a choice cannot happen anymore (because MAME device interface cannot be dynamically chosen at init). But this is only part of the MESS regression and I don't think justifies the cham24.c problem.

Long story short, the old code was not really suited the device implementation and probably a rewrite is needed.

Also, a few pc10 games are probably affected as well