- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
08159 | Interface | Minor | Always | Dec 20, 2021, 02:32 | Dec 23, 2021, 22:02 |
Tester | PepsiBoy428 | View Status | Public | Platform | MAME (Official Binary) |
Assigned To | cuavas | Resolution | Fixed | OS | Windows 10/11 (64-bit) |
Status [?] | Resolved | Driver | |||
Version | 0.238 | Fixed in Version | 0.239 | Build | 64-bit |
Fixed in Git Commit | c0e2654 | Github Pull Request # | |||
Summary | 08159: sf2049, sf2049se: Screen #0 setting reverts back to default | ||||
Description |
Here's a problem I encountered with the Screen #0 setting, the new setting saves at first but if you reboot the game a second time, the setting reverts back to default, the same happens with Rush 2049 Special Edition, This problem didn't happen in previous versions of MAME. Video of this bug is seen here: |
||||
Steps To Reproduce | Follow the steps in the video | ||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | 0.238 | ||||
Affected Sets / Systems | sf2049, sf2049se | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
2
No.19594
Tafoid Administrator
Dec 23, 2021, 19:03
|
Confirmed regression - November 1-2, 2021 https://github.com/mamedev/mame/commit/8ab63e2072f6cfe19b8f8e2acfbd29754d282c79 |
---|---|
No.19596
cuavas Administrator
Dec 23, 2021, 22:02
|
Not sure what causes this, but it has to do with when the first frame is drawn versus when system configuration is loaded. Fixing it gets rid of a comparison on the hot path that shouldn’t ever have been there, so that’s always good. |