| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 03825 | Crash/Freeze | Critical (emulation) | Always | May 2, 2010, 06:03 | May 3, 2010, 02:03 |
| Tester | Q.T.Quazar | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | Resolution | Open | OS | Windows Vista/7 (32-bit) | |
| Status [?] | Confirmed | Driver | |||
| Version | 0.137u3 | Fixed in Version | Build | Normal | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 03825: drivfrcp: Reset problem in the middle of the game | ||||
| Description |
game begins with 80 seconds race time. upon getting an Extension 3 time bonus (the best? possible time extension bonus, as opposed to 1 and 2) timer goes back up to 80 seconds and play continues as normal. towards end of this second 80 seconds, game auto-resets. bug has been reproduced by many players, many times, at MARP. top 3 recordings at: http://replay.marpirc.net/r/drivfrcp all display this behaviour |
||||
| Steps To Reproduce | must get time extension 3, then simply drive until bug occurs. | ||||
| Additional Information |
.inp file attached, playback in WolfMAME.137 (shell GUI using MAMEcore .exe). apologies for no savestate but the poor design of this game makes getting a time extension 3 exceptionally difficult. bug does not seem to occur on galaxian hardware conversions (have completed an entire race with Time Extension 3 on drivfrcb) interesting to note that drivfrcp plays much worse than drivfrcb or drivfrcg -- problems with car placement and control are quite noticeable, and speed cap is much faster. other interesting note, and this may come up as a separate bug: cars during 'night time' segment of the Galaxian conversion versions erroneously appear above the track on the horizon. do not know if this was original machine behaviour, since these were hardware conversions. this does not occur on drivfrcp. finally, curious that on all 3 sets, cars come up *behind* you at start of race as you accelerate, and will inevitably hit you before you can move out of the way (unless you have played before and know they will be coming, hence moving to the side). hard to believe that this was original behaviour, as it would be an incredible design flaw. how many games run you over before you've even started racing? suspect incorrect behaviour here. both these side notes will be reported as separate lower priority bugs if someone can check and confirm vs. original hardware. |
||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | drivfrcp | ||||
|
Attached Files
|
 qcn_drivfrcp_16600_wolf137.zip (69,911 bytes) May 2, 2010, 06:03 | ||||
 No.06037
Q.T.Quazar Tester
May 3, 2010, 02:03
|
can now confirm completed races on Time Extension 3 in drivfrcb and drivfrcg with no reset; therefore this bug seems to be limited to drivfrcp only. |
|---|