- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
06908 | Speed | Minor | Always | Mar 11, 2018, 21:46 | Mar 25, 2018, 07:10 |
Tester | mmarino4 | View Status | Public | Platform | MAME (Official Binary) |
Assigned To | tedgreen | Resolution | Fixed | OS | Windows Vista/7/8 (64-bit) |
Status [?] | Resolved | Driver | |||
Version | 0.195 | Fixed in Version | 0.196 | Build | 64-bit |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 06908: bbhcotw, bbh2sp: Game runs slow on certain levels despite being 100% in MAME (snow?) | ||||
Description | On certain levels, the games will run very slow despite MAME reporting 100% speed with F11. This happens in Canada which has a snow effect. Tried an older version (0.180) and this did not happen. Could no reproduce in bbhsc or bbhsca. | ||||
Steps To Reproduce | Start a game and press F11 to show the game speed. Go to Canada and play through some of the levels. No need to shoot, just observe the speed of the animals running in relation to the speed MAME is reporting. | ||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | bbhcotw, bbh2sp | ||||
Attached Files
|
bbhcotw.mp4 (3,066,597 bytes) Mar 15, 2018, 00:28 Uploaded by mmarino4 Comparison of speed in MAME 0.195 and 0.180, directly captured from MAME | ||||
Relationships
There are no relationship linked to this issue. |
Notes
4
No.14841
mmarino4 Tester
Mar 15, 2018, 00:29
|
Video added from Call of the Wild running in 0.195 and 0.180. Recorded directly from MAME. |
---|---|
No.14849
tedgreen Developer
Mar 17, 2018, 23:20
|
I have pushed a commit which should fix this: https://github.com/mamedev/mame/commit/d9be150c6fa86eb6a0cfa1cb2160c3347ece203a Please confirm it fixes the issue. |
No.14854
mmarino4 Tester
Mar 18, 2018, 19:12
|
Yes it does. This can be marked as resolved. |
No.14855
tedgreen Developer
Mar 18, 2018, 19:24
|
Thanks for putting this issue up. I had made an earlier commit which made the voodoo video timing correct which exasperated the incorrect cpu frequency setting. |