Cannot get user defined monitor ranges to work?

[Topgun68]

I have done so much reading over the last two weeks that I can't do it anymore. I'm about to just turn off Switchres and use mame without it but I gotta ask for help here in case I am overlooking something real simple.

I am using fresh install of Win 7 Pro with an AMD ATI Radeon HD 6450 and CRT_EMUDRIVER with a Betson Kortek KT-2914F CRT. 47 Modes were installed using super Modes. I am not sure if it matterts, but I cannot see any resolutions below 2560 by 480 in windows, even though they work fine using Arcade_OSD.

Essentially, I cannot get Groovymame .263 to use the custom crt_range0 that Calamity provided MANY people to resolve the vertical resolutions above 240p, or 256p to work. I copied it into a vertical.ini file and made sure it was in the correct ini folder but looks like it is not being read in the logs. I can see it attempting to load in the logs but it always defaults to 2560 x 288p resolution. To make sure it wasnt a path problem I used a clean build of GM from github with only a handul of roms and clean mame.ini file. The strange thing is that even if I remove CRT_RANGE0 from the ini file it still uses the 288 resolution. I know the mame.ini is being read since if I delete all the crt ranges, then I get the "could not find a video mode.." message and it loads the default resolution. I do have monitor custom in btoh mame.ini and vertical.ini. I've tried every single config change I could find and nothing is working, but for the sake of creating this log file I used a clean mame.ini   

I don't like to ask for help without doing my due diligence, but I gave it all I got.  Thanks for any ideas..

[Calamity]

Hi Topgun68,

Your vertical.ini file isn't being parsed for some reason. Fix that and you'll fix all. I can't say why it's not being parsed.

I just replicated your mame.ini, and dropped your vertical.ini (renamed extension) in the same folder where mame.exe is, and got this:

Code: [Select]

Attempting load of mame.ini
Parsing mame.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of vertical.ini
Parsing vertical.ini
Attempting load of raster.ini
Parsing raster.ini
Attempting load of source\galaga.ini
Attempting load of digdug.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of vertical.ini
Parsing vertical.ini
Attempting load of raster.ini
Parsing raster.ini
Attempting load of source\galaga.ini
Attempting load of digdug.ini
Video: Monitor 1092878645 = "\\.\DISPLAY1" (primary)
Video: Monitor 146935003 = "\\.\DISPLAY2"
Direct3D: Using Direct3D 9Ex
Switchres(v2.2.0) add display[0]
Switchres: Monitor range 15625.00-16200.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,240,448,480
Switchres: Monitor range 18001.00-19000.00,40.00-80.00,2.187,4.688,6.719,0.140,0.191,0.950,0,0,280,320,0,0
Switchres: Monitor range 20501.00-29000.00,40.00-80.00,2.910,3.000,4.440,0.451,0.164,1.048,0,0,320,384,0,0
Switchres: Monitor range 29001.00-32000.00,40.00-80.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,384,480,0,0
Switchres: Monitor range 32001.00-34000.00,40.00-80.00,0.636,3.813,1.906,0.020,0.106,0.607,0,0,480,576,0,0
Switchres: Monitor range 34001.00-38000.00,40.00-80.00,1.000,3.200,2.200,0.020,0.106,0.607,0,0,576,600,0,0
Switchres: display[0] options: monitor[custom] generation[on]
Switchres: Monitor range 15625.00-16200.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,240,448,480
Switchres: Monitor range 18001.00-19000.00,40.00-80.00,2.187,4.688,6.719,0.140,0.191,0.950,0,0,280,320,0,0
Switchres: Monitor range 20501.00-29000.00,40.00-80.00,2.910,3.000,4.440,0.451,0.164,1.048,0,0,320,384,0,0
Switchres: Monitor range 29001.00-32000.00,40.00-80.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,384,480,0,0
Switchres: Monitor range 32001.00-34000.00,40.00-80.00,0.636,3.813,1.906,0.020,0.106,0.607,0,0,480,576,0,0
Switchres: Monitor range 34001.00-38000.00,40.00-80.00,1.000,3.200,2.200,0.020,0.106,0.607,0,0,576,600,0,0
Switchres: \\.\DISPLAY2: AMD Radeon (TM) R9 200 Series (PCI\VEN_1002&DEV_6811&SUBSYS_048D1043&REV_00)
Switchres: Device key: System\CurrentControlSet\Control\Video\{175D4303-A242-11EC-844B-806E6F6E6963}\0000
ATI/AMD ADL init
AMD driver version 20.10(patched)
ADL functions retrieved successfully.
Switchres: Searching for custom video modes...

Anyway before you go any further: your picture shows that the game is using the second range actually (crt_range1, 18 kHz), so unless you void that one too GM will insist on using it.

[Topgun68]

Hi Topgun68,

Your vertical.ini file isn't being parsed for some reason. Fix that and you'll fix all. I can't say why it's not being parsed.

I just replicated your mame.ini, and dropped your vertical.ini (renamed extension) in the same folder where mame.exe is, and got this:

Code: [Select]

Attempting load of mame.ini
Parsing mame.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of vertical.ini
Parsing vertical.ini
Attempting load of raster.ini
Parsing raster.ini
Attempting load of source\galaga.ini
Attempting load of digdug.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of mame.ini
Parsing mame.ini
Attempting load of vertical.ini
Parsing vertical.ini
Attempting load of raster.ini
Parsing raster.ini
Attempting load of source\galaga.ini
Attempting load of digdug.ini
Video: Monitor 1092878645 = "\\.\DISPLAY1" (primary)
Video: Monitor 146935003 = "\\.\DISPLAY2"
Direct3D: Using Direct3D 9Ex
Switchres(v2.2.0) add display[0]
Switchres: Monitor range 15625.00-16200.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,240,448,480
Switchres: Monitor range 18001.00-19000.00,40.00-80.00,2.187,4.688,6.719,0.140,0.191,0.950,0,0,280,320,0,0
Switchres: Monitor range 20501.00-29000.00,40.00-80.00,2.910,3.000,4.440,0.451,0.164,1.048,0,0,320,384,0,0
Switchres: Monitor range 29001.00-32000.00,40.00-80.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,384,480,0,0
Switchres: Monitor range 32001.00-34000.00,40.00-80.00,0.636,3.813,1.906,0.020,0.106,0.607,0,0,480,576,0,0
Switchres: Monitor range 34001.00-38000.00,40.00-80.00,1.000,3.200,2.200,0.020,0.106,0.607,0,0,576,600,0,0
Switchres: display[0] options: monitor[custom] generation[on]
Switchres: Monitor range 15625.00-16200.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,192,240,448,480
Switchres: Monitor range 18001.00-19000.00,40.00-80.00,2.187,4.688,6.719,0.140,0.191,0.950,0,0,280,320,0,0
Switchres: Monitor range 20501.00-29000.00,40.00-80.00,2.910,3.000,4.440,0.451,0.164,1.048,0,0,320,384,0,0
Switchres: Monitor range 29001.00-32000.00,40.00-80.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,384,480,0,0
Switchres: Monitor range 32001.00-34000.00,40.00-80.00,0.636,3.813,1.906,0.020,0.106,0.607,0,0,480,576,0,0
Switchres: Monitor range 34001.00-38000.00,40.00-80.00,1.000,3.200,2.200,0.020,0.106,0.607,0,0,576,600,0,0
Switchres: \\.\DISPLAY2: AMD Radeon (TM) R9 200 Series (PCI\VEN_1002&DEV_6811&SUBSYS_048D1043&REV_00)
Switchres: Device key: System\CurrentControlSet\Control\Video\{175D4303-A242-11EC-844B-806E6F6E6963}\0000
ATI/AMD ADL init
AMD driver version 20.10(patched)
ADL functions retrieved successfully.
Switchres: Searching for custom video modes...

Anyway before you go any further: your picture shows that the game is using the second range actually (crt_range1, 18 kHz), so unless you void that one too GM will insist on using it.

Wow, that was it all this time.  It was not parsing the vertical.ini because I was just using crt_range0 that was being discussed in this thread instead of the crt_range1 that my system was using.  Well when I remove that range I get the resolution 768 by 576P where nothing is cut off, but it is still way higher than what the vertical games call for, but now I can read up on all the threads on how to use Arcade OSD knowing that the vertical.ini is being parsed when I put the correct crt_range in it.     

THANKS for that info!