| カテゴリ | 重要度 | ステータス | 解決状況 | 登録日時 | 最終更新 |
|---|---|---|---|---|---|
 システムコア | 機能追加 | 認証済み | 未処理 | 2020-06-11 11:06 | 2020-06-12 09:39 |
| テスター | Tafoid | 担当者 | ソース | ||
| バージョン | 0.221 | 発生バージョン | 修正バージョン | ||
| 修正コミット | プルリク | ||||
| フラグ | |||||
| セット | DRC Cores | ||||
| セット詳細 | |||||
| 概 要 | ゲームの情報画面でDRC情報、DRCロックについて不足している。 | ||||
| 詳 細 | In instances where there is a DRC core in MAME, there is no way of knowing if -DRC or -NODRC are having any effect. For a good period of time back in late 2013 through mid 2014, all cores which had DRC did display this fact if they were activated or not. This concept was scrapped, however, when all the cores were summarily "modernized" and all usage cases where the Game Information would show that it was employing the DRC were overlooked and not readded. There are also some driver cases where DRC maybe be disabled by default for various reasons, but you are not allowed you to use these machines with the DRC compatible cores, even if the -DRC trigger is activated. The user should have these available to them if they wish, or if (as would be in my case) checking for breakage comparing DRC and non-DRC tests. I'm also sure there is big developer advantage, too, of allowing default off DRC to be activated with out changing source code. I'd argue using set_force_no_drc as a function is a bit too extreme. | ||||
| 再現手順 | |||||
| 追加情報 | |||||
| 添付ファイル | |||||