- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
03781 | Misc. | Trivial | Always | Mar 13, 2010, 02:06 | Mar 13, 2010, 15:24 |
Tester | NekoEd | View Status | Public | Platform | SDLMAME |
Assigned To | Resolution | Open | OS | Linux | |
Status [?] | Confirmed | Driver | |||
Version | 0.137 | Fixed in Version | Build | Normal | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 03781: trivialp: [possible] In-game EPROM tests take a ridiculous amount of time | ||||
Description | The EPROM checksum tests in set trivialp take an incredibly long time to complete, well longer than the approximate times listed on the test screens. Compare to scrabble, where the tests complete in reasonable amounts of time rather close to the approximations given. To complete the tests in trivialp in a reasonable, but still rather long amount of time, unthrottling the game is necessary. | ||||
Steps To Reproduce | Open the back door ( "9" by default ), then wait until the game displays "BACK DOOR OPEN". From there, hit the "TEST/DEMO" key ( "=" by default ) and you'll hear a sound then go to the test menu. The ROM tests are in the second half of the menus, accessed on this set by touching "MORE TESTS" at the bottom of the list. | ||||
Additional Information | I have not tested any of the other sets in the driver, feel free to do so if I don't get around to it. | ||||
Github Commit | |||||
Flags | Possible | ||||
Regression Version | |||||
Affected Sets / Systems | trivialp | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
4
No.05866
Tafoid Administrator
Mar 13, 2010, 02:26
|
Again, like your other bug, specific steps to reproduce would be helpful. |
---|---|
No.05869
NekoEd Senior Tester
Mar 13, 2010, 11:56
edited on: Mar 13, 2010, 11:57 |
Done. Added to main report. |
No.05870
Haze Senior Tester
Mar 13, 2010, 14:36
|
I have my doubts that this is a bug. If anything ROM/RAM tests are usually *faster* under emulation due to missing watistates / ram access time emulation. I imagine they just have a very inefficient routine to do the tests, and have inaccurate values displayed on the screen. Test Screens are often an unreliable source of information. It *could* be a bug, but given other games on the hardware work as expected I'd be surprised. |
No.05872
Tafoid Administrator
Mar 13, 2010, 15:24
|
Got a chance to try this - starting fresh and doing the test directly it does it in almost exactly 2 minutes (compared to realtime clock). There might be something out of whack or not being processed correctly - doubling the time? The DUART emulation (according to the source), is still in progress. I'll confirm, but set as possible pending some investigation and some input from driver author would be helpful too. |