| カテゴリ | 重要度 | ステータス | 解決状況 | 登録日時 | 最終更新 |
|---|---|---|---|---|---|
 ゲームプレイ | 重要 (ゲーム) | 解決済み | 修正済み | 2018-10-18 08:46 | 2020-12-15 21:07 |
| テスター | rodneylives | 担当者 | galibert | ソース | rampart.cpp |
| バージョン | 0.200 | 発生バージョン | 0.123u5 | 修正バージョン | 0.227 |
| 修正コミット | プルリク | ||||
| フラグ | |||||
| セット | rampart, maybe rampartj and rampart2p | ||||
| セット詳細 |
 rampart - ランパート (Trackball) | ||||
| 概 要 | 4面からあとでゲームボードが異なり動作が固まる。 | ||||
| 詳 細 | The problem was detected on MAMEUI64. When the player gets to Level 4 on Veteran, in at least some circumstances (possibly all), the board visible on-screen doesn't match what's held in memory. The actual board is for a different level, and the disparity not only makes it weird to play, but ultimately causes the game to hang. I've got screenshots, a recording of a playthrough where the problem happens, and two saved states I can provide. Ships end up sailing around on land, grunts travel through water, the player can build and place cannons on water. The castles, however, are placed according to the visible map, not the internal one. After finishing the board (it takes a long time!), board 5 locks up after selecting a Home Castle. Video of the bug happening is up on YouTube: | ||||
| 再現手順 | What I do: 1. Start a one-player game as Blue Army. 2. Play normally until Level 4 (it's the choice between two peninsula maps). I pick the one to the right. 3. Select the far-right castle for Home Castle. After selecting it, the problem should be evident immediately. Note that getting this far into Rampart is pretty difficult. For help in getting that far, I suggest going into the operator's menu and setting the game as easy as possible, playing with analog mouse controls, and setting the sensitivity on the X and Y axes to at least 50. Even then, Rampart is a challenging game. I do not know if getting that far in another way causes the error to not occur. My assumption, at this point, is that it's just not possible to play level 4 without it happening. | ||||
| 追加情報 | The attached file is a zipped save state (64-bit version of MAME v0.200) around where the problem has just occurred. If you need further information, such as the playthrough video (compressed it's around 200 megabytes), let me know where to upload it. There are screenshots of the problem in action in an Imgur gallery I made here: https://imgur.com/gallery/laN5bAn I also mentioned the bug in this thread in the MAMEdev forums: https://forum.mamedev.org/viewtopic.php?f=14&t=358&p=1132 There, Tafoid suggested it might be a problem with SLAPSTIC emulator, which I seem to remember was a issue with some previous versions? I have played Rampart through to completion in some previous versions of MAME, so I presume the error was introduced since then, maybe in the past four or five years or so? As an additional note--I have played Rampart in the arcade, and don't remember the digitized drums being quite so overwhelming as when it is emulated in MAME. Is this worth filing a separate bug for, or can the audio balance be manually adjusted somewhere? | ||||
| 添付ファイル |  1.zip (2018-10-18 08:46) | ||||
 rampartbug.inp (2020-09-03 16:00) | |||||
| rampart122.zip (2020-12-12 18:21) | |||||
| rampart.nv (2020-12-12 18:22) | |||||