The NEW Build Your Own Arcade Controls
Software Support => GroovyMAME => Topic started by: schmerzkaufen on September 09, 2019, 06:34:04 pm
-
@Calamity: I don't know if you remember I've notified you of that issue, for quite a long time now Arcade OSD has been refusing to copy the required modeline (copy to clipboard is greyed-out)
Personally I have been using the same old one I've managed to copy a long time ago when you were instructing me, 'copy to clipboard' was still working back then, but soon after that any new attempt failed.
But today I've talked to two aspiring LCD users (one going for the full/dynamic method, and one nVidia user going for the static) who are both stuck right at the start of the guide because of that issue.
That means the LCD guide in its current state isn't appliable, so, is there a way to 'fix' Arcade OSD for us ? or any other way to acquire that precious modeline ?
Just running a log and copy the default picked 60Hz 'monitor range' when switchres is set to default 'lcd' maybe ?
Thanks.
PS: for readers here's the LCD guide in question: http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=374
-
I am one of the users working with schmerzkaufen. Let me know how I can help and test and I will. Would an older version of ArcadeOS possibly work?
-
It's working here, Arcade OSD is fine.
In order to follow the method in the guide, Arcade OSD must be able to read the timings from the current desktop mode. When this works, the mode is show as "custom" and the timings are accesible for copying.
Arcade OSD can't read the timings from Nvidia cards, so you need to find an alternative method to get its native modeline (Nvidia control panel, read monitor's EDID, etc.) and use that modeline to create a crt range manually. But since GM wont use this crt range to actually change the video timings on Nvidia you can ignore this step and use the dummy range in GM's log as a starting point, as you suggest.
The issue with your particular case (schmerzkaufen) is probably IIRC that your monitor didn't report its native mode correctly due to the interlace flag.
-
It's working here, Arcade OSD is fine.
In order to follow the method in the guide, Arcade OSD must be able to read the timings from the current desktop mode. When this works, the mode is show as "custom" and the timings are accesible for copying.
But it's not working fine, I have an AMD and so does savj14, copy to clipboard is greyed out, same issue I've had for a long time, as I said; it worked before, so something changed at some point.
so you need to find an alternative method to get its native modeline (Nvidia control panel, read monitor's EDID, etc.)
But what method ? that's exactly what we're asking about. It's nowhere to be found in either control panels and we don't know how to read EDIDs. Whether for AMD or nVidia, how to get that native modeline if we cannot use Arcade OSD ?
Is what I said about copying it from a log valid or not ?
The guide is not working for either AMD or nVidia users without that modeline obviously.
The issue with your particular case (schmerzkaufen) is probably IIRC that your monitor didn't report its native mode correctly due to the interlace flag.
All three of us have the same kind of LCD monitors: able to display custom Hz 1080p or 1200p modes from 50 to 75-85, I don't think mine only is the issue.
(well I can confirm mine can, and the other guy I know too, and high chances savj14's as well)
-
But it's not working fine, I have an AMD and so does savj14, copy to clipboard is greyed out, same issue I've had for a long time, as I said; it worked before, so something changed at some point.
Before it was not working correctly, it was reading a modeline that didn't match the mode reported, causing issues in GM as you know. Now it's fixed an when there's a mismatch it discards the timings read.
Reading video timings is not always possible, even on AMD. This doesn't mean the program is broken.
However, even if you can't read the timings from the desktop mode, there's a chance you can read the timings of another video mode, and use those instead by modifying the resolution and freq values in the same way as explained in the guide.
-
Also, for reading monitor's EDID there's a free app called Monitor Asset Manager (https://www.entechtaiwan.com/util/moninfo.shtm). This is probably the easiest way to get any panel's native modeline.
-
However, even if you can't read the timings from the desktop mode, there's a chance you can read the timings of another video mode, and use those instead by modifying the resolution and freq values in the same way as explained in the guide.
I'm not sure I understand exactly how this could work as the other mode's values are likely quite different, could you give us an example ?
Anyway I'll give that a try myself, but the guide needs an update as it is likely that more users will find themselves in the same situation.
Also, for reading monitor's EDID there's a free app called Monitor Asset Manager (https://www.entechtaiwan.com/util/moninfo.shtm). This is probably the easiest way to get any panel's native modeline.
Thanks a lot I will try it.
EDIT: okay so I get the following
Detailed timing #1....... 1920x1080p at 60Hz (16:9)
Modeline............... "1920x1080" 148,500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Now I have to figure how to turn this into a crt_range line...
WARNING: moninfo made my monitor turn to green screen like every 5 seconds. So after I was done using it, I uninstalled it and restarted my PC, and it stopped.
-
Ok, so you get this modeline:
"1920x1080" 148,500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Now edit it like this (notice the bits in bold, pay attention to the dot replacing the comma):
modeline "1920x1080_60" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Then in GM replace the "modeline auto" option in mame.ini with the line above. Run a random game with logging enabled and GM will produce a crt range matching the provided modeline. Copy it, and undo the changes in mame.ini. Then resume the guide from there.
-
Like this ? or am I supposed to change back 'monitor' to something else first?
(also at 'resolution' I still have my dummy mode written, do I erase it? I'm asking these things in advance to avoid messing up too much)
#
# CORE SWITCHRES OPTIONS
#
modeline_generation 1
monitor custom
orientation horizontal
connector auto
interlace 1
doublescan 1
super_width 2560
changeres 1
powerstrip 0
lock_system_modes 0
lock_unsupported_modes 0
refresh_dont_care 0
dotclock_min 0
sync_refresh_tolerance 2.0
frame_delay 0
vsync_offset 0
black_frame_insertion 0
modeline "1920x1080_60" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
ps_timing auto
lcd_range auto
crt_range0 auto
-
Correct. Monitor as "custom" is correct. Set resolution as "auto", although the modeline option should override it anyway.
-
Ok here's the log. I must always apologize for my incompetence :-[ but where is it ? (I mean the line I have to use as my base crt_range)
-
It's in there by the top:
SwitchRes: user modeline "1920x1080_60 67.500000KHz 60.000000Hz" 148.500000 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
SwitchRes: Monitor range 67275.00-67725.00,59.80-60.20,0.593,0.296,0.997,0.059,0.074,0.533,1,1,1080,1080,0,0
-
Ooh I'm so blind-dumb lol. Thanks, I will be back in a moment after applying the guide to confirm.
-
Ok everything seems to work perfectly fine, thanks a million as ususual. ;)
Note the differences between my old modeline;
56250-84375,50.00-75.00,0.741,1.157,1.898,0.015,0.045,0.507,0,1,1080,1080,0,0
And the new I've just made;
56250-84375,50.00-75.00,0.593,0.296,0.997,0.059,0.074,0.533,1,1,1080,1080,0,0
-
So it worked fine for the other guy too (using a laptop with dedicated nVidia and external monitor)
What's the status for you savj14 ?