Build Your Own Arcade Controls Forum
Software Support => GroovyMAME => Topic started by: pakoman on December 16, 2016, 10:40:21 am
-
Hi.
Is there a way to add one low res mode, for instance 256x240@60hz, to windows 10 plain Catalyst drivers -not CRT EMUdriver-?
I believe that Soft15khz and Winmodelines only work for older versions. I've already tried Vmmaker and plain drivers will reject everything below 440 lines. However Vmmaker works fine for EDID emulation on plain drivers.
My goal is to add only the modeline for the game I'd like to master to finish with one credit and as I only have one computer at the moment, I don't want to restart in "arcade mode" so the computer can still be used for internet access or other things.
I've found this: http://www.makeuseof.com/tag/how-to-set-a-custom-resolution-in-windows-10/ (http://www.makeuseof.com/tag/how-to-set-a-custom-resolution-in-windows-10/)
https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU (https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU)
However:
Standard resolutions:
Standard resolutions are mostly useful for CRT monitors and for adding lower resolutions with LCD monitors. Do not add the native resolution as a standard resolution.
AMD/ATI only supports the resolutions in the drop-down list. Other resolutions will be ignored by the driver. These will be listed in gray.
NVIDIA does not support more than 8 standard resolutions.
Standard resolutions are limited to 60-123 Hz. Use detailed resolutions to add other refresh rates.
I've tried it and it adds resolutions around 240p and are selectable! Although the screen doesn't sync properly. I have to test it further, but looks promising :)
-
EDIT: I posted in spanish, I don't know what I was thinking about...
I managed to add working 15khz progressive resolutions with this little program without the need of changing drivers or having to restart in safe mode under windows 10. I think it only admits 2 custom modes but hey... does the trick when not using a dedicated computer.
My bad I can't get a working resolution to fill the screen as this program seems to use slight different values. May somebody help me with this?:
The needed values are:
Horizontal Active, Front Porch, Sync width, Back Porch. Blanking, Total, Sync Polarity
Vertical Active, Front Porch, Sync width, Back Porch. Blanking, Total, Sync Polarity
And then Refresh rates (hz and Khz) and pixel clock.
-
I'm also wondering why vmmaker is rejecting the resolution of for example 640x448 using stock drivers, when in CRU I was able to add it by adjusting blanking so the horizontal frequency stays in monitor's range. Is it not intelligent enough :D ?
-
I'm also wondering why vmmaker is rejecting the resolution of for example 640x448 using stock drivers, when in CRU I was able to add it by adjusting blanking so the horizontal frequency stays in monitor's range. Is it not intelligent enough :D ?
It's not VMMaker who rejects it, it's the driver. VMMaker is just informing you about the driver's decision :)
VMMaker adds modes through the ADL library, which has a very crude resolution check. CRT Emudriver hacks that check. The modes added through the EDID follow a totally different path in the driver.
Pakoman's achievement is really interesting. I'll see how CRU is adding modes to the edid custom table, as it should be possible to add that feature to VMMaker, e.g. by accepting a modeline list when emulating an edid.
-
Pakoman's achievement is really interesting. I'll see how CRU is adding modes to the edid custom table, as it should be possible to add that feature to VMMaker, e.g. by accepting a modeline list when emulating an edid.
I'm glad you find it interesting :)
And it seems to work with Nvidia also (even maybe intel integrated graphics in the future).
Adding resolutions to the EDID instead of to the driver would work with GM/Switchres with non Ati cards?
PS: I've managed to get working full screen resolutions, although I don't fully understand the values. Even if I remember correctly GM was able to set the right vertical refresh. So it seems that GM works perfectly with this new approach (at least with latest ATI unpatched drivers)