| カテゴリ | 重要度 | ステータス | 解決状況 | 登録日時 | 最終更新 |
|---|---|---|---|---|---|
 システムコア | 低 | 解決済み | 修正済み | 2013-12-30 13:33 | 2013-12-31 15:24 |
| テスター | AWJ | 担当者 | AWJ | ソース | |
| バージョン | 0.152 | 発生バージョン | 修正バージョン | 0.153 | |
| 修正コミット | プルリク | ||||
| フラグ | 64ビット限定 | ||||
| セット | all | ||||
| セット詳細 | |||||
| 概 要 | 64ビットビルドのスクリーンショットが32ビットに比べ青の要素の値が1多い。 | ||||
| 詳 細 | The attached file is the output of pngcmp on screenshots of the test grid screen in polepos taken with a 32-bit MAME build (left) and a 64-bit build (center). Although the two screenshots look identical to the naked eye, the merciless gaze of pngcmp reveals that every blue pixel is different. If you open the png in a graphics editor and use a "select by color" tool, you can see that the blue pixels in the 64-bit screenshot aren't even all the same color as each other! In the 32-bit screenshot, every single blue pixel is RGB(45, 67, 157). In the 64-bit screenshot, most of the blue pixels are RGB(45, 67, 158), but the blue pixels at the lower and right edges of the blue squares are RGB(46, 68, 158). | ||||
| 再現手順 | |||||
| 追加情報 | This bug seems to be caused by the SSE2 versions of the RGB utility functions (in emu/video/rgbsse.h), which are currently only used by 64-bit builds. If I modify emu/video/rgbutil.* to force use of the generic C implementation (emu/video/rgbgen.h), the errors go away and 64-bit screenshots become 100% identical to 32-bit screenshots. | ||||
| 添付ファイル |  diff.png (2013-12-30 13:33) | ||||