|
Potential problem with vsync+multiple monitors?
#286160 - 05/13/12 04:53 AM
|
|
|
I can't seem to reproduce this consistently, but I figure I should pass this along to see if anyone else has any ideas.
Using VSYNC with multiple monitors has a rough 50% chance of causing MAME to run normally until the emulation starts (read: pre-start warnings about not supporting cocktail rotation work fine) but once the game actually starts up, MAME stops taking input at all and has to be end-tasked.
It MIGHT be multithreaded-related, as turning that on seems to have made it worse, but I'm not 100% sure. I don't have enough to go on to get this to MAMETesters, so I figure my best bet is to get this one over here to see if anyone else can reproduce it.
|
---
Try checking the MAME manual at http://docs.mamedev.org
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: Potential problem with vsync+multiple monitors?
[Re: Firehawke]
#286317 - 05/14/12 10:25 PM
|
|
|
I'm not sure vsync on has a coherent meaning on multiple monitors. You're displaying one game with one refresh rate on two monitors with potentially differing fixed refresh rates, after all.
|
|
|
|
Re: Potential problem with vsync+multiple monitors?
[Re: R. Belmont]
#286331 - 05/14/12 11:58 PM
|
|
|
How exactly can we limit tearing without introducing additional frame latency (read: triple buffering) on a multiple monitor setup, then?
|
---
Try checking the MAME manual at http://docs.mamedev.org
|
|
Previous 
Index 
Next 
Threaded 
Potential problem with vsync+multiple monitors?
Reply
[Re: 