- --
Viewing Issue Advanced Details
[ Jump to Notes ]
| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 02790 | Core | Critical (emulator) | Always | Dec 30, 2008, 23:16 | Jan 1, 2009, 01:22 |
| Tester | john_iv | View Status | Public | Platform | MAMEUI |
| Assigned To | aaron | Resolution | Fixed | OS | Windows XP/Vista 64-bit |
| Status [?] | Resolved | Driver | |||
| Version | 0.128u7 | Fixed in Version | 0.129 | Build | 64-bit |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 02790: Mame will crash on single monitor system if set to numscreens 2 in the *.ini. | ||||
| Description |
If you are running Mame or MameUI on a two monitor system and then move that ini over to a one monitor system and attempt to run, it will crash on the single monitor system. MameUI crashes and Mame itself does some weird flickering / multisession related too? |
||||
| Steps To Reproduce |
Use these mame.ini settings on a single monitor system. # # WINDOWS VIDEO OPTIONS # video d3d numscreens 2 window 1 maximize 1 keepaspect 1 prescale 3 effect none waitvsync 0 syncrefresh 0 |
||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | 0.118u5 | ||||
| Affected Sets / Systems | |||||
|
Attached Files
|
|||||
Relationships
| There are no relationship linked to this issue. |
Notes
1
 No.03442
Tafoid Administrator
Dec 30, 2008, 23:43
|
Regression testing points to 0.118u5. If memory serves, this is the first version with the current compile tools - could this be a compile issue? |
|---|