- --
Viewing Issue Advanced Details
| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 02001 | Interface | Minor | Always | Jul 11, 2008, 19:49 | Jul 12, 2008, 13:46 |
| Tester | john_iv | View Status | Public | Platform | MAMEUI |
| Assigned To | Resolution | No change required | OS | Windows XP/Vista 64-bit | |
| Status [?] | Closed | Driver | |||
| Version | 0.126 | Fixed in Version | Build | 64-bit | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 02001: sfiii: Spurious information presented after -str benchmark run on command-line w/ sfiii. | ||||
| Description |
After running a benchmark pass on sfiii there are additional texts showing on the command line beyond the expected percentages: testhacks 000166b4 063cdff4 cram_gfxflash_bank_LSB_w LSB32 00000000 Sound [84] 230000 Sound [84] 230000 Sound [84] 230000 Average speed: 376.47% (89 seconds) |
||||
| Steps To Reproduce |
Run 'mame64 -str 90 -nothrottle -nosound -video none' After run see this or similar: testhacks 000166b4 063cdff4 cram_gfxflash_bank_LSB_w LSB32 00000000 Sound [84] 230000 Sound [84] 230000 Sound [84] 230000 Average speed: 376.47% (89 seconds) |
||||
| Additional Information | Just kind of annoying to have to work around it when copying and pasting bench results from a full .txt file from 20 other behaving games. :-) | ||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | sfiii | ||||
|
Attached Files
|
|||||
Relationships
| There are no relationship linked to this issue. |
Notes
3
|
No.01578
Tafoid Administrator
Jul 11, 2008, 23:06
|
I think this fall under the blanket of debug files and other messages - like those mentioned in 01779. If that's the case, it's not really a bug. Another Dev care to comment? |
|---|---|
|
No.01579
Haze Senior Tester
Jul 11, 2008, 23:18
|
well some of them serve as a reminder that the decryption really needs to be done in the cpu core, so that it behaves correctly (non-encrypting) on dma operations etc.... at the moment the behavior depends on the code address, very kludgy. |
|
No.01580
Tafoid Administrator
Jul 12, 2008, 13:45
|
Unless I'm told otherwise - I'll assume all text messages / debug files are acceptable and are not required to be stripped out of release builds. Resolving |