Build Your Own Arcade Controls Forum

Software Support => GroovyMAME => Topic started by: AzureKnight on April 29, 2016, 10:22:08 am

Title: Help! Error: SwitchRes: could not find a video mode that meets your specs
Post by: AzureKnight on April 29, 2016, 10:22:08 am
Hello all,

My functional but not finished machine got an overhaul about 8 months ago and one of the things I did was build a new computer in it.  I upgraded to allow myself to put in a Radeon HD4890 so I could use GroovyMame and SwitchRes to take advantage of my Wells Gardner D9400.

Most games work fine, but some don't.  For most of that time I didn't keep real close track of which games didn't work.  About a week or two ago I decided it was high time I fixed this issue so I started to track which games don't run.  When I run one of these games from MaLa it just looks like nothing happens, a quick MaLa load screen would flash and then nothing.  Just still sitting there at the MaLa game lists.  I had assumed my new ROM set just had some bad roms or the version I was trying to load was bad, etc.

Some games I know don't work:
Cyberball 2072
Gunsmoke
Sunset Riders

Last night I decided to troubleshoot.

I ran Cyberball directly from MAME and I get the following error popup:

"SwitchRes: could not find a video mode that meets your specs"

I have the option to click OK, when I do so the game runs fine.

If I run the game from command line the error pops in the command window and the game runs fine.  So obviously MaLa is getting the error and shutting down the thread.  So I need to get this error sorted out.

I've dug around these boards and the internet and couldn't fix the problem so I figured I would ask here.

To help you help me, some info:

I followed the following setup to get things running for Windows 7 using all their suggested settings:
http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=290 (http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=290)

Video Card: RADEON HD 4890
OS: Windows 7
Monitor: Wells Gardner D9400

It seemed to go smoothly enough.

I found a suggestion here on how to run GroovyMAME with a log dump so I'll post that here.  Any suggestions would be very welcome.  I am currently posting this from work so I can't test anything until I get home tonight.

Code: [Select]
SwitchRes: v0.015g, Monitor: d9400, Orientation: horizontal, Modeline generation: enabled
SwitchRes: Monitor range 15250.00-18000.00,40.00-80.00,2.187,4.688,6.719,0.190,0.191,1.018,0,0,224,288,448,576
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,288,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: Failed obtaining default video registry key
Switchres: Searching for custom video modes...
SwitchRes: Found 0 custom of 0 active video modes
SwitchRes: Setting option -noswitchres

SwitchRes: Entering switchres_modeline_setup
SwitchRes: v0.015g:[] Calculating best video mode for 0x0@0.000000 orientation: normal
SwitchRes: Setting option -noswitchres
Video: Monitor 00000000067D3CF8 = "\\.\DISPLAY1" (primary)
Direct3D: Warning - Unable find any D3D9 DLLs; disabling post-effect rendering
Direct3D: Using Direct3D 9
window_proc: WM_NCACTIVATE
blit_lock = TRUE
SwitchRes: Resolution change from 0x0@0.000000 normal to 672x240@0.000000 normal
Direct3D: Configuring adapter #0 = ATI Radeon HD 4800 Series
Direct3D: Using dynamic textures
Direct3D: YUV format = RGB
Direct3D: Max texture size = 8192x8192
Direct3D: Device created at 640x480
blit_unlock = TRUE
window_proc: WM_PAINT
Blitting thread created
winwindow_video_window_create: blit_lock = TRUE
RawInput: APIs detected
Blitting thread started
Input: Adding Mouse #0: HID-compliant mouse
Input: Adding Gun #0: HID-compliant mouse
Input: Adding Mouse #1: HID-compliant mouse
Input: Adding Gun #1: HID-compliant mouse
Input: Adding Kbd #0: Standard PS/2 Keyboard
Input: Adding Kbd #1: HID Keyboard Device
Input: Adding Kbd #2: HID Keyboard Device
DirectInput: Using DirectInput 8
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 ':jsa:cpu' created
Region ':gfx1' created
Region ':gfx2' created
Region ':gfx3' created
Region ':jsa:oki1' created
Region ':eeprom:eeprom' created
Starting Cyberball 2072 (2 player, rev 4) ':'
Optional device 'rscreen' not found
Optional device 'lscreen' not found
Optional device 'mob2' not found
Optional device 'alpha2' not found
Optional device 'playfield2' not found
Optional device 'dac2' not found
Optional device 'dac1' not found
Optional device 'dac' not found
Optional device 'extra' not found
Optional device 'audiocpu' not found
Optional device ':slapstic' not found
Optional shared pointer 'paletteram' not found
Optional device 'soundcomm' not found
Optional device 'oki' not found
Optional device 'audiocpu' not found
Optional shared pointer 'yscroll' not found
Optional shared pointer 'xscroll' not found
Optional device 'earom' not found
  (missing dependencies; rescheduling)
Starting M68000 ':maincpu'
Starting Atari EEPROM Interface (2816) ':eeprom'
Starting Parallel EEPROM 2816 (2048x8) ':eeprom:eeprom'
Starting gfxdecode ':gfxdecode'
Starting palette ':palette'
Starting Tilemap ':playfield'
Starting Tilemap ':alpha'
Starting Atari Motion Objects ':mob'
Optional shared pointer 'slip' not found
  (missing dependencies; rescheduling)
Starting Video Screen ':screen'
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Atari JSA II Sound Board ':jsa'
Optional memory bank 'oki2hi' not found
Optional memory bank 'oki2lo' not found
Optional memory bank 'oki1hi' not found
Optional memory bank 'oki1lo' not found
Optional device 'oki2' not found
  (missing dependencies; rescheduling)
Starting M6502 ':jsa:cpu'
Starting Atari Sound Communications ':jsa:soundcomm'
Starting YM2151 ':jsa:ym2151'
Starting OKI6295 ':jsa:oki1'
Starting Cyberball 2072 (2 player, rev 4) ':'
Optional device 'rscreen' not found
Optional device 'lscreen' not found
Optional device 'mob2' not found
Optional device 'alpha2' not found
Optional device 'playfield2' not found
Optional device 'dac2' not found
Optional device 'dac1' not found
Optional device 'dac' not found
Optional device 'extra' not found
Optional device 'audiocpu' not found
Optional device ':slapstic' not found
Optional shared pointer 'paletteram' not found
Optional device 'soundcomm' not found
Optional device 'oki' not found
Optional device 'audiocpu' not found
Optional shared pointer 'yscroll' not found
Optional shared pointer 'xscroll' not found
Optional device 'earom' not found
  (missing dependencies; rescheduling)
Starting Atari Motion Objects ':mob'
Optional shared pointer 'slip' not found
Starting Speaker ':mono'
  (missing dependencies; rescheduling)
Starting Atari JSA II Sound Board ':jsa'
Optional memory bank 'oki2hi' not found
Optional memory bank 'oki2lo' not found
Optional memory bank 'oki1hi' not found
Optional memory bank 'oki1lo' not found
Optional device 'oki2' not found
Starting Cyberball 2072 (2 player, rev 4) ':'
Optional device 'rscreen' not found
Optional device 'lscreen' not found
Optional device 'mob2' not found
Optional device 'alpha2' not found
Optional device 'playfield2' not found
Optional device 'dac2' not found
Optional device 'dac1' not found
Optional device 'dac' not found
Optional device 'extra' not found
Optional device 'audiocpu' not found
Optional device ':slapstic' not found
Optional shared pointer 'paletteram' not found
Optional device 'soundcomm' not found
Optional device 'oki' not found
Optional device 'audiocpu' not found
Optional shared pointer 'yscroll' not found
Optional shared pointer 'xscroll' not found
Optional device 'earom' not found
  (missing dependencies; rescheduling)
Starting Speaker ':mono'
Starting Cyberball 2072 (2 player, rev 4) ':'
Optional device 'rscreen' not found
Optional device 'lscreen' not found
Optional device 'mob2' not found
Optional device 'alpha2' not found
Optional device 'playfield2' not found
Optional device 'dac2' not found
Optional device 'dac1' not found
Optional device 'dac' not found
Optional device 'extra' not found
Optional device 'audiocpu' not found
Optional device ':slapstic' not found
Optional shared pointer 'paletteram' not found
Optional device 'soundcomm' not found
Optional device 'oki' not found
Optional device 'audiocpu' not found
Optional shared pointer 'yscroll' not found
Optional shared pointer 'xscroll' not found
Optional device 'earom' not found
SwitchRes: Resolution change from 672x240@0.000000 normal to 672x240@59.922749 normal
Average speed: 99.99% (9 seconds)
window_proc: WM_NCACTIVATE
blit_lock = TRUE
window_proc: WM_DESTROY
blit_lock = TRUE
Blitting thread destroyed
Title: Re: Help! Error: SwitchRes: could not find a video mode that meets your specs
Post by: Calamity on April 29, 2016, 10:41:08 am
Here's the issue:

Code: [Select]
SwitchRes: Failed obtaining default video registry key
What is defined for the -screen option in mame.ini? Is it "auto"?

Try using the option -screen \\.\DISPLAY1
Title: Re: Help! Error: SwitchRes: could not find a video mode that meets your specs
Post by: AzureKnight on April 29, 2016, 10:47:57 am
Here's the issue:

Code: [Select]
SwitchRes: Failed obtaining default video registry key
What is defined for the -screen option in mame.ini? Is it "auto"?

Try using the option -screen \\.\DISPLAY1

I was kicking myself this morning for not bringing my mame.ini as well  :)

I am almost positive it is set to "2560x0" (assuming I am thinking of the right setting).  If not it would most likely be "auto".

I will try that tonight, thank you!
Title: Re: Help! Error: SwitchRes: could not find a video mode that meets your specs
Post by: Calamity on April 29, 2016, 10:51:08 am
-screen, not -resolution
Title: Re: Help! Error: SwitchRes: could not find a video mode that meets your specs
Post by: AzureKnight on April 29, 2016, 10:59:46 am

I'll be honest, I'm following tutorials and setting settings without really understanding what they do.  I'm actually a programmer and I hate myself for doing this, but time is tough to come by.  I noticed that you suggested -screen instead of -resolution.  One of the things I stumbled on last night was to set -resolution to 2560x0, when I went to try it I noticed that -screen was set to this value already and everything else in the block of settings was "auto".  That is why I recall that specific setting being set to "2560x0". 

Now I'm certain that is very likely my issue, I must have gone to set -resolution back when I was doing the setup and screwed up and set -screen by mistake.  PEBKAC (Problem Exists Between Keyboard And Chair)   ::)

Calamity, I know this has been said before by many here, but I'll say it again: Thank You  :applaud:

Seriously, thank you.  You have dedicated so much of that precious time to helping total strangers have an awesome, nostalgic gaming experience.  You have helped put a smile on my face and joy in my heart.
Title: Re: Help! Error: SwitchRes: could not find a video mode that meets your specs
Post by: AzureKnight on April 30, 2016, 11:57:38 am
That was the issue, thank you again!
Title: Re: Help! Error: SwitchRes: could not find a video mode that meets your specs
Post by: a7mag3ddon on April 07, 2020, 12:14:43 pm
Hi All,

Not sure if this is still valid for the current 2020 Mame.ini but i cant see a -screen setting in there?

i am also getting the switch res warning.