-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-monitor support #9
Comments
Hey @andyvans, that's awesome. I don't think I've ever tried it with multiple monitors before. I see mame itself has a I think I have an extra screen available so I'll give your branch a try as soon as I can... |
It's pretty alpha at the moment. The screen cloning works but needs optimisation. The -numscreens x option works in two ways:
The problem with the opengl version of mame is that it just doesn't look as good. The directx 9 shaders make the games (particularly vector games) look much better on large screens. I will keep tweaking the code. It may work out, it may not. |
A note on the OpenGL version - this can look okay, but you need to be using the GLSL shaders instead of the HLSL shaders which are Direct3D only. The GLSL shaders don't appear to come out of the box with the official Windows versions of MAME, and the only ones I could find at a quick Google no longer work. That being said, I've tried raster GLSL shaders but not any vector ones. Your point may still stand. |
Couple of thoughts I had:
After reading about the |
Looking at http://wiki.mamedev.org/index.php/LAY_File_Basics_-_Part_I for #12 I notice that in the lay file you can control multi screens too - might be an option you could look into... |
Hey @andyvans I just had a chance to try out the multi screen cloning - very very cool! 👍 |
The latest changes seem much faster as the graphics work is now all native win32 - hardware context to hardware context. It is no longer going via managed objects. It also supports monitors with different resolutions e.g. it will scale to the destination screen size. I will need to test a high DPI monitor. Next, to improve speed of when exiting (mouse move/keystoke), I might force minimise the mame window to give the illusion of an instance shutdown. |
The minimise of the mame window is really good. The screen saver exits instantly. No lag at all. |
The layouts are interesting. Not quite for cloning, but for enhancing B&W games or adding a frame around the game. I guess game metadata could go into the layout if it was dynamically rendered per game. |
Would you mind creating a pull request? Purely because I have an appveyor build server and then I don't have to recompile each branch myself - my multi monitors are on a separate laptop I don't use often :) I will only accept it once you are finished...
Yeah they're not hugely useful in this scenario - although I notice that if you just add |
@mika76 The multi-monitor cloning works well. I have tried it with 2 & 3 monitors. It's hard to tell which is the original Mame screen. I will create a PR for you to look at. |
The one I tried previous was already brilliant so I can just imagine - such a great PR thanks! |
Cheers @mika76. I think I need to tweak the logic where the source and destination monitors don't have the same aspect ratio e.g. 16x9 vs 4x3. |
Hey there. I work with Matt and have also been playing around with your code. A nice distraction.
I have been toying with multi-support. At present only the primary monitor shows anything. I have tried a few options:
Option 3 seem best, but still need to test it a bit more. I have made either option 1 or 3 available via a checkbox setting. You can check it out here if you are interested.
https://github.com/andyvans/mamesaver/commits/master
The text was updated successfully, but these errors were encountered: