| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 01037 | Gameplay | Minor | Have not tried | Feb 8, 2008, 14:41 | Feb 6, 2012, 19:59 |
| Tester | Nomax | View Status | Public | Platform | |
| Assigned To | Resolution | Open | OS | ||
| Status [?] | Confirmed | Driver | |||
| Version | 0.78u3 | Fixed in Version | Build | ||
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 01037: mmpanic: There are issues with the game clock. | ||||
| Description |
The driver automatically grabs the correct time from MAME, but year is set to 1904 instead of 2004 (see snapshot 1). It's not a bug in the original game because as you can see on the second snapshot, the game is "year 2000" compliant. When you push the "clock set" button (3) on the clock setting service screen (see 2nd snapshot), the game freezes. All you can do then is reset or quit the game. So it's impossible to set the clock since the changes aren't saved. Suggestion: It's not really a bug as it shouldn't freeze, but you shouldn't be able to save the clock either. We aren't going to update your system clock.. Actually, this could be better. In all of the other systems the clock is seeded from the system clock and then updated in memory. This one simply reads the current time from the system clock on every read with localtime(), for example. |
||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | mmpanic | ||||
|
Attached Files
|
 mmpanic078u3ora_shot1.png (2,483 bytes) Feb 14, 2008, 17:53 | ||||
| mmpanic078u3ora_shot2.png (2,295 bytes) Feb 14, 2008, 17:53 | |||||