Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
00962 Gameplay Minor Have not tried Feb 7, 2008, 18:09 Jul 28, 2019, 23:47
Tester -Misc Reporters- View Status Public Platform
Assigned To Resolution Fixed OS
Status [?] Resolved Driver
Version 0.53 Fixed in Version Build
Fixed in Git Commit Github Pull Request #
Summary 00962: rampart: Sound FX / Sound Items come at the wrong times occasionally.
Description Rampart still seems to have cosmetic issues, even now that the slapstic emulation is complete.

Sound FX / Sound Items come at the wrong times occasionally, such as having the announcer yell "Cease Fire" while you are building your castle, or hearing cannon sounds go off during the build round. Playback on the trackball version (original romset 'rampart') will often cut out and go blue screen, which leads me to believe that either sound or control is still not properly emulated in the game (trackball movement is pathetically slow in the game, much slower than the arcade).I'm unsure if the last thing I noticed is a bug or not: ships disappear sometimes after the 'Destruction' round, which may be a bug, but more importantly, if that ship was beached before disappearing, it can still drop off armies the next round, even though it isn't there. Did this happen on the original machine as well?
Steps To Reproduce
Additional Information Posted by Q.T.Quazar / BSR
Github Commit
Flags
Regression Version
Affected Sets / Systems rampart
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
2
User avatar
No.16693
Kale
Developer
Jul 26, 2019, 22:38
Does this still applies? Seems fixed to me.
User avatar
No.16700
MetalGod
Senior Tester
Jul 28, 2019, 16:06
edited on: Jul 28, 2019, 18:13
Tested on mame 0.211 and mame 0.78. I can confirm that all of the mentioned issues are fixed.
Focusing on the sound issue of the title, it seems it was fixed long ago, maybe in mame 0.60
According to mameinfo:
"-12nd June 2002: smf fixed the sounds in Rampart".
This fix could belong to mame 0.60, but I cannot test it because I don't have such an old mame romset (the oldest I have is 0.78).