Software Support > GroovyMAME
CRT range and vertical positioning
makya:
Yes, we have to know which monitor to use beforehand.
Milsancho:
--- Quote from: makya on October 18, 2023, 11:42:30 am ---Multi-monitor support: Switchres 2.0 can handle up to 4 displays simultaneously, each with its own separate configuration. Default Switchres settings for all displays are read from MAME's usual .ini system, but now you can create specific per-display .ini files, named display0.ini, display1.ini, etc., that allow independent configuration for each display. Vertical synchronization (-syncrefresh) is always done to display #0.
Most importantly, the user can decide which exact monitor the output will go to in a multi-monitor setup. While this is not a new feature, it now works reliably on both Windows and Linux. As usual, set the option -screen <screen> for that. Remind that in Windows <screen> is typically \\.\DISPLAY1, \\.\DISPLAY2, etc., while in Linux (SDL2) you have screen0, screen1, etc.[/i]
I believe that you have to tell GM which monitor to use, then you can define different ranges for each monitor, by means of displayX.ini files.
--- End quote ---
Thanks, I somehow missed that!
So, if I understand properly, the CRT range definitions should go within displayX.ini files (and be deleted from mame.ini)? I'm likely missing something quite elementary, but why are several consecutive crt_rangeX lines within Groovymame's original mame.ini file if so, though?
Besides, the syntax for -screen is like this and it goes within a particular game's ini?
-screen \\.\DISPLAY1
If there's no defined -screen, Groovymame will always pick the first display according to Windows? And for all this to work, does Groovymame need that the desktop has been extended, I presume? If it hasn't and there's just one active screen, what Groovy will do when it reads another -screen instruction?
Too many questions, I'm afraid, but seems by setup is not usual at all.
makya:
It is useful to have several ranges even on a single monitor. I don't know how arcade monitors behave, but tv sets can be temperamental and using several ranges is almost mandatory, at least for me it is (I compile my own version of GM to extend the max number of ranges according to my needs).
The syntax for -screen is correct.
By default, I believe GM will pick the first monitor available in windows.
I don't know if the desktop needs to be extended or if it could work on a cloned desktop.
If -screen is set to a non exisiting monitor, you wont get any picture (just tried \\.\DISPLAY2 on a single monitor PC)
All that said, in case you want to use one monitor at a time, you should not go the displayX.ini way, because Vertical synchronization (-syncrefresh) is always done to display #0.
Please describe precisely what you want to achieve.
Milsancho:
--- Quote from: makya on October 19, 2023, 01:19:36 pm ---It is useful to have several ranges even on a single monitor. I don't know how arcade monitors behave, but tv sets can be temperamental and using several ranges is almost mandatory, at least for me it is (I compile my own version of GM to extend the max number of ranges according to my needs).
--- End quote ---
I indeed must be missing something elementary, because I fail to understand this bit. In the case of only one 15khz TV, doesn't Groovy calculate the best modeline for every instance according to the specified CRT range? Why is it better several CRT ranges instead of only one which "includes" all the others? Is it just for different geometry situations? How does Groovy even know which range to pick every time?
--- Quote ---By default, I believe GM will pick the first monitor available in windows.
I don't know if the desktop needs to be extended or if it could work on a cloned desktop.
If -screen is set to a non exisiting monitor, you wont get any picture (just tried \\.\DISPLAY2 on a single monitor PC)
All that said, in case you want to use one monitor at a time, you should not go the displayX.ini way, because Vertical synchronization (-syncrefresh) is always done to display #0.
Please describe precisely what you want to achieve.
--- End quote ---
Windows 7, R7 200 series card (VGA, HDMI, DVI-D), CRT Emu Driver with Vulkan compatibility (by psakhis), 15khz RGB TV, 31-to-102 kHz PC CRT.
At phase 1 I just want to have both monitors connected but use them alternatively. So I'll just tell Windows which monitor is active every time before launching Groovymame or whatever with the screen properties app.
Here resides the first question I got, I think: After installing Emu Driver, which is the best way to enable/activate Edid emulation for both monitors so that I can extend or clone the desktop safely. Or even if, given the particular setup of mine, I should follow the installation guide at Calamity's site to the letter.
For Groovymame, I don't care if I have to create preventively an ini for every game which otherwise could natively use both, a progressive mode or the interlaced version, given that both video modes will likely be possible on my system once I generate the modes for the different vertical frequencies both monitors are capable, but what I don't want is that Groovy tries to run a game at 31khz if it's the 15khz TV the one in use (obviously).
I also want to run Windows games and other emulators, some of them at 15khz, many of them at 31khz and beyond.
There's the second question I have, should I install 15 and 31khz (and beyond) modes at once from an edited user_modes.ini for Video mode maker? Are high resolution interlaced modes (for 15khz) just distinguised by the "@ 30.000000" mark there?
I'm sure I'll need to make use of the standalone Switchres app, but I'll ask about it at its moment not to complicate it too much for now.
For the same reason, I'll leave for the future a phase 2 where both monitors can be used simultaneously on those games using natively two screens, lol.
By the way, have the discussions on Groovy and Tools moved to discord or elsewhere these days?
Substring:
WHat I'd like to stress with my previous unanswered question, is that right now you're forced to know which roms will go to 15kHz, and which roms will go to 31kHz
With this in mind, you'd need to create shortcuts pointing to the right .ini (where you can set the screen, no need ot use the command line switch). Going through a single launch script is doable, but would require to parse a file with games resolution and refresh rate
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version