Groovymame partially working without CRT Emudriver installed?

[pakoman]

Hi.

I'm using a laptop with mobility radeon 5650 and the catalyst drivers windows 10 installs by default with Groovymame 0.171 attached to a Sony FullHD TV through HDMI.

Mame.ini has 'generic15khz' monitor setting.

Mame seems to run at 720x480 or 640x480 both at 15 kHz and with correct refresh rates (I tried different games with different vertical refreshes and for all of them the scroll is smooth without tearing). Mame info splash screen shows the chosen resolution and refresh matches the game resolution. Some games like RType run at about 50% speed but other run perfect.

If I force -resolution 1900x1080 then I get the error 'switchres could not find a valid resolution'. Mame info splash screen shows no chosen resolution and refresh, just the game resolution. And games have tearing, Rtype doesn't run slow...  This is the same situation as if I use the laptop built in screen.

Even the TV info shows that resolution is 10bit or 480p (I think it has auto de-interlace) and the screen goes black and TV info pops up when there is a in-game change of resolution.

Is this possible?
How is windows 10 has already available those resolutions 640x480 and 720x480?
If so could we add same resolutions with winmodelines or something like that and they will work without installing the CRT Emudriver?


Cheers.

[Calamity]

Very explanatory topic subject

Yes, GroovyMAME can work to some extent using default drivers. This is because the AMD ADL api is present and usable. What CRT Emudriver does is to patch the drivers so you can install more than 10 modelines, and changes take effect on the fly. It's a big long to explain: official drivers also support on the fly changes but the native function takes too long to complete to be usable, because it has to rebuild all the mode list etc. When you use -video d3d9ex the native call is used because we do need it to convert e.g. 640x480@60 into 640x480@30, so GroovyMAME is actually installing that new mode without any additional software. The issue with this is that it's slow, but if you have a short modelist as is your case you probably won't notice it.

You can also use VMMaker without CRT Emudriver to add other modes. However note the limit is 10 modes.

The reason why you're getting 50% speed for R-type is unclear. Please post a log so I can check.

[pakoman]

Thanks 

This are actually very good news even more now that main Mame is incorporating Groovymame features. So at least playing at the right refresh for speed and smooth scroll may become more mainstream (pixel perfect resolutions would be another issue).

Games that change resolution take a lot to change, may be related to the TV or to what you said.

So, as with super-resolutions we don’t need a lot of them, it would be possible to add 2 or 3 resolutions and use super-resolutions with plain AMD drivers? For instance for my LED TV 1900x244@60 and 1900x288@50, even 1900x480@30.
Or even more 2560x244@60, 2560x288@50, 2560x480@30 to the CRT TV and use normal Windows 7/8/10 and computer instead of a dedicated machine. I guess it works the same way as CRT Emudrivers with different resolutions assigned to each screen. Although I’m afraid that it won’t detect a CRT TV without adding resistances to the VGA-SCART cable as there is no EDID emulation with plain drivers.

I think the possibility of playing at the right refresh rate is very interesting and should go into main Mame.


PS I’ll post a log for R-Type when I have time at home.

[pakoman]

RType runs at about 85% with 2 partial updates.


Is that what you want?

Code: [Select]


C:\Games\MAME>mame64 rtype -verbose
SwitchRes: v0.015m, Monitor: generic_15, Orientation: horizontal, Modeline generation: enabled
SwitchRes: Monitor range 15625.00-15750.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,288,448,576
SwitchRes: \\.\DISPLAY1: AMD Mobility Radeon HD 5000 Series (PCI\VEN_1002&DEV_68C1&SUBSYS_031C1025&REV_00)
SwitchRes: Device key: System\CurrentControlSet\Control\Video\{6D25AAAC-E93B-416F-AB6B-2DF2EEDD0852}\0000
ATI/AMD ADL init
ADL functions retrieved successfully.
Switchres: Searching for custom video modes...
Switchres: [  1]  640x 480 @ 60 : ATI ADL timing "640x480_60 31.462000KHz 59.927620Hz" 25.170000 640 656 752 800 480 490 492 525   -hsync -vsync
Switchres: [  2]  640x 480 @ 59 : system mode
Switchres: [  3]  720x 480 @ 59 : system mode
Switchres: [  4]  720x 480 @ 60 : ATI ADL timing "720x480_60 31.468000KHz 59.939049Hz" 27.000000 720 736 798 858 480 489 495 525   -hsync -vsync
Switchres: [  5]  720x 480 @ 29 : system mode
Switchres: [  6]  720x 480 @ 30 : ATI ADL timing "720x480_30 31.468000KHz 59.939049Hz" 27.000000 720 736 798 858 480 489 495 525   -hsync -vsync
Switchres: [  7]  720x 576 @ 59 : system mode
Switchres: [  8]  720x 576 @ 60 : system mode
Switchres: [  9]  720x 576 @ 50 : ATI ADL timing "720x576_50 31.250000KHz 50.000000Hz" 27.000000 720 732 796 864 576 581 586 625   -hsync -vsync
Switchres: [ 10]  720x 576 @ 25 : ATI ADL timing "720x576_25 31.250000KHz 50.000000Hz" 27.000000 720 732 796 864 576 581 586 625   -hsync -vsync
Switchres: [ 11]  800x 480 @ 60 : system mode
Switchres: [ 12]  800x 600 @ 60 : ATI ADL timing "800x600_60 37.878000KHz 60.315285Hz" 40.000000 800 840 968 1056 600 601 605 628   +hsync +vsync
Switchres: [ 13] 1024x 600 @ 60 : system mode
Switchres: [ 14] 1024x 768 @ 60 : ATI ADL timing "1024x768_60 48.363000KHz 60.003723Hz" 65.000000 1024 1048 1184 1344 768 771 777 806   -hsync -vsync
Switchres: [ 15] 1152x 648 @ 59 : system mode
Switchres: [ 16] 1152x 648 @ 60 : ATI ADL timing "1152x648_60 44.951000KHz 59.934666Hz" 74.170000 1152 1326 1366 1650 648 689 694 750   +hsync +vsync
Switchres: [ 17] 1152x 648 @ 50 : ATI ADL timing "1152x648_50 37.500000KHz 50.000000Hz" 74.250000 1152 1656 1696 1980 648 689 694 750   +hsync +vsync
Switchres: [ 18] 1280x 720 @ 59 : system mode
Switchres: [ 19] 1280x 720 @ 60 : ATI ADL timing "1280x720_60 44.951000KHz 59.934666Hz" 74.170000 1280 1390 1430 1650 720 725 730 750   +hsync +vsync
Switchres: [ 20] 1280x 720 @ 50 : ATI ADL timing "1280x720_50 37.500000KHz 50.000000Hz" 74.250000 1280 1720 1760 1980 720 725 730 750   +hsync +vsync
Switchres: [ 21] 1280x 768 @ 60 : system mode
Switchres: [ 22] 1280x1024 @ 60 : ATI ADL timing "1280x1024_60 63.981000KHz 60.019699Hz" 108.000000 1280 1328 1440 1688 1024 1025 1028 1066   +hsync +vsync
Switchres: [ 23] 1400x1050 @ 59 : system mode
Switchres: [ 24] 1400x1050 @ 60 : system mode
Switchres: [ 25] 1400x1050 @ 50 : system mode
Switchres: [ 26] 1400x1050 @ 29 : system mode
Switchres: [ 27] 1400x1050 @ 30 : system mode
Switchres: [ 28] 1400x1050 @ 23 : system mode
Switchres: [ 29] 1400x1050 @ 24 : system mode
Switchres: [ 30] 1600x 900 @ 60 : ATI ADL timing "1600x900_60 60.000000KHz 60.000000Hz" 108.000000 1600 1624 1704 1800 900 901 904 1000   +hsync +vsync
Switchres: [ 31] 1680x1050 @ 59 : system mode
Switchres: [ 32] 1680x1050 @ 60 : system mode
Switchres: [ 33] 1680x1050 @ 50 : system mode
Switchres: [ 34] 1680x1050 @ 29 : system mode
Switchres: [ 35] 1680x1050 @ 30 : system mode
Switchres: [ 36] 1680x1050 @ 23 : system mode
Switchres: [ 37] 1680x1050 @ 24 : system mode
Switchres: [ 38] 1776x1000 @ 59 : system mode
Switchres: [ 39] 1776x1000 @ 60 : ATI ADL timing "1776x1000_60 67.431000KHz 59.938667Hz" 148.350000 1776 1936 1980 2200 1000 1044 1049 1125   +hsync +vsync
Switchres: [ 40] 1776x1000 @ 50 : ATI ADL timing "1776x1000_50 56.250000KHz 50.000000Hz" 148.500000 1776 2376 2420 2640 1000 1044 1049 1125   +hsync +vsync
Switchres: [ 41] 1776x1000 @ 29 : system mode
Switchres: [ 42] 1776x1000 @ 30 : ATI ADL timing "1776x1000_30 33.713000KHz 29.967112Hz" 74.170000 1776 1936 1980 2200 1000 1044 1049 1125   +hsync +vsync
Switchres: [ 43] 1776x1000 @ 25 : ATI ADL timing "1776x1000_25 56.250000KHz 50.000000Hz" 148.500000 1776 2376 2420 2640 1000 1044 1049 1125   +hsync +vsync
Switchres: [ 44] 1776x1000 @ 24 : ATI ADL timing "1776x1000_24 27.000000KHz 24.000000Hz" 74.250000 1776 2486 2530 2750 1000 1044 1049 1125   +hsync +vsync
Switchres: [ 45] 1920x1080 @ 59 : system mode
Switchres: [ 46] 1920x1080 @ 60* : ATI ADL timing "1920x1080_60 67.431000KHz 59.938667Hz" 148.350000 1920 2008 2052 2200 1080 1084 1089 1125   +hsync +vsync
Switchres: [ 47] 1920x1080 @ 50 : ATI ADL timing "1920x1080_50 56.250000KHz 50.000000Hz" 148.500000 1920 2448 2492 2640 1080 1084 1089 1125   +hsync +vsync
Switchres: [ 48] 1920x1080 @ 29 : system mode
Switchres: [ 49] 1920x1080 @ 30 : ATI ADL timing "1920x1080_30 33.713000KHz 29.967112Hz" 74.170000 1920 2008 2052 2200 1080 1084 1089 1125   +hsync +vsync
Switchres: [ 50] 1920x1080 @ 25 : ATI ADL timing "1920x1080_25 56.250000KHz 50.000000Hz" 148.500000 1920 2448 2492 2640 1080 1084 1089 1125   +hsync +vsync
Switchres: [ 51] 1920x1080 @ 23 : system mode
Switchres: [ 52] 1920x1080 @ 24 : ATI ADL timing "1920x1080_24 26.970000KHz 23.973333Hz" 74.170000 1920 2558 2602 2750 1080 1084 1089 1125   +hsync +vsync
SwitchRes: Found 23 custom of 52 active video modes

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015m:[rtype] Calculating best video mode for 384x256@55.017605 orientation: normal

SwitchRes: [ 640]x[ 480]_(60=59.927620Hz)
   rng(0):  640 x 480_55.017605i 15.652509 [fract] scale(1, 1, 1) diff(40.00, 67.61, 0.0000) ratio(1.667, 1.875)

SwitchRes: [ 640]x[ 480]_[59=59.000000Hz] - locked

SwitchRes: [ 720]x[ 480]_[59=59.000000Hz] - locked

SwitchRes: [ 720]x[ 480]_(60=59.939049Hz)
   rng(0):  720 x 480_55.017605i 15.652509 [fract] scale(1, 1, 1) diff(46.67, 67.61, 0.0000) ratio(1.875, 1.875)

SwitchRes: [ 720]x[ 480]_[29=29.000000Hz] - locked

SwitchRes: [ 720]x[ 480]_(30=59.939049Hz)
   rng(0):  720 x 480_55.017605i 15.652509 [fract] scale(1, 1, 1) diff(46.67, 67.61, 0.0000) ratio(1.875, 1.875)

SwitchRes: [ 720]x[ 576]_[59=59.000000Hz] - locked

SwitchRes: [ 720]x[ 576]_[60=60.000000Hz] - locked

SwitchRes: [ 720]x[ 576]_(50=50.000000Hz)
   rng(0):  720 x 576_51.136364i 15.775568 [fract] scale(1, 2, 1) diff(46.67, 7.79, -3.8812) ratio(1.875, 2.250)

SwitchRes: [ 720]x[ 576]_(25=50.000000Hz)
   rng(0):  720 x 576_51.136364i 15.775568 [fract] scale(1, 2, 1) diff(46.67, 7.79, -3.8812) ratio(1.875, 2.250)

SwitchRes: [ 800]x[ 480]_[60=60.000000Hz] - locked

SwitchRes: [ 800]x[ 600]_(60=60.315285Hz)
   rng(0):  out of range

SwitchRes: [1024]x[ 600]_[60=60.000000Hz] - locked

SwitchRes: [1024]x[ 768]_(60=60.003723Hz)
   rng(0):  out of range

SwitchRes: [1152]x[ 648]_[59=59.000000Hz] - locked

SwitchRes: [1152]x[ 648]_(60=59.934666Hz)
   rng(0):  out of range

SwitchRes: [1152]x[ 648]_(50=50.000000Hz)
   rng(0):  out of range

SwitchRes: [1280]x[ 720]_[59=59.000000Hz] - locked

SwitchRes: [1280]x[ 720]_(60=59.934666Hz)
   rng(0):  out of range

SwitchRes: [1280]x[ 720]_(50=50.000000Hz)
   rng(0):  out of range

SwitchRes: [1280]x[ 768]_[60=60.000000Hz] - locked

SwitchRes: [1280]x[1024]_(60=60.019699Hz)
   rng(0):  out of range

SwitchRes: [1400]x[1050]_[59=59.000000Hz] - locked

SwitchRes: [1400]x[1050]_[60=60.000000Hz] - locked

SwitchRes: [1400]x[1050]_[50=50.000000Hz] - locked

SwitchRes: [1400]x[1050]_[29=29.000000Hz] - locked

SwitchRes: [1400]x[1050]_[30=30.000000Hz] - locked

SwitchRes: [1400]x[1050]_[23=23.000000Hz] - locked

SwitchRes: [1400]x[1050]_[24=24.000000Hz] - locked

SwitchRes: [1600]x[ 900]_(60=60.000000Hz)
   rng(0):  out of range

SwitchRes: [1680]x[1050]_[59=59.000000Hz] - locked

SwitchRes: [1680]x[1050]_[60=60.000000Hz] - locked

SwitchRes: [1680]x[1050]_[50=50.000000Hz] - locked

SwitchRes: [1680]x[1050]_[29=29.000000Hz] - locked

SwitchRes: [1680]x[1050]_[30=30.000000Hz] - locked

SwitchRes: [1680]x[1050]_[23=23.000000Hz] - locked

SwitchRes: [1680]x[1050]_[24=24.000000Hz] - locked

SwitchRes: [1776]x[1000]_[59=59.000000Hz] - locked

SwitchRes: [1776]x[1000]_(60=59.938667Hz)
   rng(0):  out of range

SwitchRes: [1776]x[1000]_(50=50.000000Hz)
   rng(0):  out of range

SwitchRes: [1776]x[1000]_[29=29.000000Hz] - locked

SwitchRes: [1776]x[1000]_(30=29.967112Hz)
   rng(0):  out of range

SwitchRes: [1776]x[1000]_(25=50.000000Hz)
   rng(0):  out of range

SwitchRes: [1776]x[1000]_(24=24.000000Hz)
   rng(0):  out of range

SwitchRes: [1920]x[1080]_[59=59.000000Hz] - locked

SwitchRes: [1920]x[1080]_[60=59.938667Hz]
   rng(0):  out of range

SwitchRes: [1920]x[1080]_(50=50.000000Hz)
   rng(0):  out of range

SwitchRes: [1920]x[1080]_[29=29.000000Hz] - locked

SwitchRes: [1920]x[1080]_(30=29.967112Hz)
   rng(0):  out of range

SwitchRes: [1920]x[1080]_(25=50.000000Hz)
   rng(0):  out of range

SwitchRes: [1920]x[1080]_[23=23.000000Hz] - locked

SwitchRes: [1920]x[1080]_(24=23.973333Hz)
   rng(0):  out of range

SwitchRes: [rtype] (1) horizontal (384x256@55.017605)->(720x480@55.017605)
   rng(0):  720 x 480_55.017605i 15.652509 [fract] scale(1, 1, 1) diff(46.67, 67.61, 0.0000) ratio(1.875, 1.875)
SwitchRes: Modeline "720x480_60 15.652509KHz 55.017605Hz" 14.775968 720 752 824 944 480 506 512 569 interlace  -hsync -vsync
Switchres: saving    ATI ADL timing "720x480_60 31.468000KHz 59.939049Hz" 27.000000 720 736 798 858 480 489 495 525   -hsync -vsync
Switchres: updating  SwitchRes: Setting option -rotate
SwitchRes: Setting option -noror
SwitchRes: Setting option -autoror
SwitchRes: Setting option -norol
SwitchRes: Setting option -noautorol
SwitchRes: Setting option -noblack_frame_insertion
SwitchRes: Setting option -nomultithreading
SwitchRes: Setting option -notriplebuffer
SwitchRes: Setting option -syncrefresh
SwitchRes: Setting option -waitvsync
SwitchRes: Setting option -keepaspect
SwitchRes: Setting option -filter
SwitchRes: Setting option -prescale 1
Video: Monitor 00000000088CB4A8 = "\\.\DISPLAY1" (primary)
Direct3D: Using Direct3D 9
window_proc: WM_NCACTIVATE
blit_lock = TRUE
Physical width 1920, height 1080
Direct3D: Configuring adapter #0 = AMD Mobility Radeon HD 5000 Series
Direct3D: Adapter has Vendor ID: 1002 and Device ID: 68C1
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 16384x16384
Direct3D: Device created at 720x480
Direct3D: First scanline: 31, Last scanline: 511, Break scanline: 511, Delay scanline: -25
blit_unlock = TRUE
RawInput: APIs detected
Input: Adding Mouse #0: PS/2 Compatible Mouse
Input: Adding Gun #0: PS/2 Compatible Mouse
Input: Adding Mouse #1: Microsoft USB IntelliMouse Optical
Input: Adding Gun #1: Microsoft USB IntelliMouse Optical
Input: Adding Kbd #0: Standard PS/2 Keyboard
DirectInput: Using DirectInput 8
Input: Adding Joy #0: USB Joystick
window_proc: WM_PAINT
blit_lock = FALSE
window_proc: WM_PAINT:END
stream_buffer_size = 37888
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
Region ':maincpu' created
Region ':sprites' created
Region ':gfx2' created
Region ':gfx3' created
Starting R-Type (World) ':'
Optional I/O port 'JumperJ3' not found
Optional shared pointer 'spriteram2' not found
Optional shared pointer 'majtitle_rowscr' not found
Optional device 'dac' not found
Optional device 'mcu' not found
  (missing dependencies; rescheduling)
Starting V30 ':maincpu'
Starting Z80 ':soundcpu'
Starting 8259 PIC ':upd71059c'
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Video Screen ':screen'
Starting Speaker ':lspeaker'
  (missing dependencies; rescheduling)
Starting Speaker ':rspeaker'
  (missing dependencies; rescheduling)
Starting Irem M72 Audio Custom ':m72'
Optional memory region '^samples' not found
Starting YM2151 ':ymsnd'
Starting R-Type (World) ':'
Optional I/O port 'JumperJ3' not found
Optional shared pointer 'spriteram2' not found
Optional shared pointer 'majtitle_rowscr' not found
Optional device 'dac' not found
Optional device 'mcu' not found
  (missing dependencies; rescheduling)
Starting Speaker ':lspeaker'
Starting Speaker ':rspeaker'
Starting R-Type (World) ':'
Optional I/O port 'JumperJ3' not found
Optional shared pointer 'spriteram2' not found
Optional shared pointer 'majtitle_rowscr' not found
Optional device 'dac' not found
Optional device 'mcu' not found
Average speed: 83.93% (22 seconds)
Switchres: restoring ATI ADL timing "720x480_60 31.468000KHz 59.939049Hz" 27.000000 720 736 798 858 480 489 495 525   -hsync -vsync
ATI/AMD ADL close
Sound: buffer overflows=3 underflows=0
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE

[pakoman]

I tried to add custom resolutions to plain Catalyst 15 drivers and so far:

-VMMaker allows to create an EDID and to add custom resolutions.
-Everything above 480 lines is rejected by the driver.
-It only allows around 5 custom modes
-I can only use the added custom modes if I use the TV as secondary screen extended desktop with the laptop built-in screen as main primary one. I can use them as desktop resolution so they work.
-If I only use the TV, the custom modes can’t be used. So there’s no point for mame, unless…
-If I use both screens and force Mame to use the 2nd screen with –screen //./DISPLAY 2. It actually runs on the 2nd screen –TV- but doesn’t pick the custom resolution even with –resolution 2560x512 command line.

Maybe it works better with something above 31khz, but that’s not quite interesting. Is this all can we achieve with plain drivers?

[emubastard]

Very explanatory topic subject

Yes, GroovyMAME can work to some extent using default drivers. This is because the AMD ADL api is present and usable. What CRT Emudriver does is to patch the drivers so you can install more than 10 modelines, and changes take effect on the fly. It's a big long to explain: official drivers also support on the fly changes but the native function takes too long to complete to be usable, because it has to rebuild all the mode list etc. When you use -video d3d9ex the native call is used because we do need it to convert e.g. 640x480@60 into 640x480@30, so GroovyMAME is actually installing that new mode without any additional software. The issue with this is that it's slow, but if you have a short modelist as is your case you probably won't notice it.

You can also use VMMaker without CRT Emudriver to add other modes. However note the limit is 10 modes.

The reason why you're getting 50% speed for R-type is unclear. Please post a log so I can check.

Trying to wrap my head around this.

I use d3d9ex in order to get interlace working.  It takes about 4 seconds from launch to execution of the rom when I play an interlaced game.  I hear the USB beeps and boops like a device is being installed.  That doesn't seem particularly bad to me.

Is it possible for groovymame to reserve one modeline to install all the various modes it will use on the fly for running games?  Sure would be a nice option for using official drivers, especially if you have a mixed use system or cabinet that plays newer games as well.  Maybe this could end the modeline limit issues by just continually reprogramming one modeline over and over as needed.

Personally I don't switch in an out of games every second so a 4 second delay isn't hurting me, and I'm using d3d9ex anyway.

[Calamity]

I tried to add custom resolutions to plain Catalyst 15 drivers and so far:

-VMMaker allows to create an EDID and to add custom resolutions.
-Everything above 480 lines is rejected by the driver.
-It only allows around 5 custom modes
-I can only use the added custom modes if I use the TV as secondary screen extended desktop with the laptop built-in screen as main primary one. I can use them as desktop resolution so they work.
-If I only use the TV, the custom modes can’t be used. So there’s no point for mame, unless…
-If I use both screens and force Mame to use the 2nd screen with –screen //./DISPLAY 2. It actually runs on the 2nd screen –TV- but doesn’t pick the custom resolution even with –resolution 2560x512 command line.

Maybe it works better with something above 31khz, but that’s not quite interesting. Is this all can we achieve with plain drivers?

I guess you mean anything below 480 lines is rejected.

Anyway, this setup *should* work, even with regular drivers. I mean, having the VGA as \\.\DISPLAY2, and an emulated EDID on it, is the proper way to do it.

You need to be careful as to where you install the custom modes. Make sure you pick the right output (\\.\DISPLAY2). The method we use for HD 5000+ cards applies custom modes only to a given output, contrary to legacy cards where all custom modes got messed across different outputs. Note that right after installing an emulated edid, the display numbers are garbled. What I do is to exit the current session and log in again, this restores the usual numbers which are preserved on different sessions.

Besides, keep in mind turning given a mode from progressive to interlace is not possible unless you use -video d3d9ex, and even then it's not usually a good idea. This is the problem with the rtype log you posted, it's trying to produce an interlaced mode out of 720x480-31kHz. This is because you're using the native driver modes as a base. Instead, install proper 15 kHz modes on the VGA output, and just use them (assuming this is possible at all).

[pakoman]

Thanks for your help, very kind as always 

Yes, I mean below, my mistake.

It seems that the only modes I can add are 2560x512, 2560x496 and 2560x480 with super resolutions.
Or 768x512 id I use user_modes.ini.

All other modes are rejected.

With Catalyst 15 it makes no different having the HDMI connected or not and I tried all combinations of Outputs, so I guess this is the best I can achieve with plain drivers. So |I guess plain drivers are not best for this, unless you don't mind using interlaced resolutions -which I hate-.

ArcadeOSD and VMMaker work great, can emulate EDIDs and so...but the drivers are quite limited

[Calamity]

Is it possible for groovymame to reserve one modeline to install all the various modes it will use on the fly for running games?

That is not possible. What could be done is to create modes on the fly as required, then delete them on exit, as the Linux build do.

However the problem is, slowness aside, that regular Catalyst drivers won't accept modes below 480p. CRT Emudriver has a specific patch for this.

It'd be nice patched drivers wouldn't be required for this. Anyone from AMD reading this? Please remove the limitation. Anyway I don't think anyone apart from us is using this API.

[pakoman]

However the problem is, slowness aside, that regular Catalyst drivers won't accept modes below 480p. CRT Emudriver has a specific patch for this.

Is possible to easily patch other Catalyst versions or that's why you are using that specific version?

[Calamity]

Is possible to easily patch other Catalyst versions or that's why you are using that specific version?

That specific version (12.8 ) is the last one known to have available debugging symbols. It was the one that came with Windows 8.0. I believe I should be able to patch Catalyst 15 based on that knowledge, even if debugging symbols for AMD drivers are not available for any newer version.

[emubastard]

Delete me

[emubastard]

Delete me

[pakoman]

Is possible to easily patch other Catalyst versions or that's why you are using that specific version?

That specific version (12.8 ) is the last one known to have available debugging symbols. It was the one that came with Windows 8.0. I believe I should be able to patch Catalyst 15 based on that knowledge, even if debugging symbols for AMD drivers are not available for any newer version.

If you think it's worth the effort it would be nice, specially for setups not using dedicated cabinets. Don't know what other changes brings version 15.

[Calamity]

If you think it's worth the effort it would be nice, specially for setups not using dedicated cabinets. Don't know what other changes brings version 15.

It was my next immediate project, although the GroovyMAME merge has taken priority I'm afraid. Anyway I insist it should be possible to do what you want with 12.8.

[pakoman]

Well, it seems that normal Catalyst drivers DO ADMIT modes below 480 lines in Windows 10 after all.


Actually with this Custom Resolution Utility (CRU) it is possible to add custom resolutions to the EDID created with Vmmaker:
http://www.makeuseof.com/tag/how-to-set-a-custom-resolution-in-windows-10/
https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU

Custom Resolution Utility (CRU) allows custom resolutions to be defined for both AMD/ATI and NVIDIA GPUs by creating EDID overrides directly in the registry without dealing with .inf files.

Maybe you find it interesting.