Setting up for Win7, LCD, and Nvidia Card??

[lettuce]

Ok i am wanting to get groovyMAME working on my media PC that is connected to my LCD screen, im running windows 7 and am using a Nvidia GTX 560 Ti card. What settings do i need to use to get Groovymame working with this type of setup?

[lettuce]

Anyone, have tried setting it up, but when ever i load a rom i get a message saying something about too many modelines??

[Calamity]

Bear in mind that this build is mainly targeted to WinXP, CRT, and ATI Card  

However, read the last posts in the main thread where it's explained how to use this with an LCD screen. You'll need to install Powerstrip for that.

That error you're reporting seems to be a bug, please report your logs with -v -md 4 params so we can fix it:
http://forum.arcadecontrols.com/index.php?topic=113382.0

[lettuce]

Thanks for the reply. Ok just to make sure, i have downloded:

groovymame32_0143.013c_test.rar
VMMaker 1.3b + Arcade_OSD_1.3.rar
Powerstrip

and installed them (not sure if i need VMMaker, as using LCD, Win 7 and Nvidia card)

These are the only options i have changed in the VMMaker.ini file:

MonitiorType = 'lcd'

monitor_specs0            29000.00-50000.00,50.00-70.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,1920,1080

and in the mame.ini file:

monitor lcd
monitor_aspect 16:9
cleanstretch 1

Then from the command prompt i go to the mame directory and use the following command to load a rom:

mame 1942 -ps -monitor lcd -video d3d

upon doing this i get the following message (the line, "SwitchRes: Warning, too many active modelines for storage 251" is repeated loads of times):

SwitchRes: Warning, too many active modelines for storage 251
SwitchRes: Warning, too many active modelines for storage 251
SwitchRes: Failed opening System\CurrentControlSet\Control\Video\{DEB039CC-B704-
4F53-B43E-9DD4432FA2E9}\0000 registry entry with error 5

-----------------------------------------------------
Exception at EIP=01C6F0AB (not found): ACCESS VIOLATION
While attempting to read memory at 00000044
-----------------------------------------------------
EAX=00000000 EBX=00233858 ECX=000003F5 EDX=000003F4
ESI=FFFFFFFF EDI=00233858 EBP=0028FEC8 ESP=00231A40
-----------------------------------------------------
Stack crawl:
  0028FEC8: 01C6F0AB (not found)
  0028FF88: 00401422 (not found)
  0028FF94: 7529339A (BaseThreadInitThunk+0x0012)
  0028FFD4: 77409ED2 (RtlInitializeExceptionChain+0x0063)
  0028FFEC: 77409EA5 (RtlInitializeExceptionChain+0x0036)

C:\Mame>

Am i doing everything correctly??

[Calamity]

groovymame32_0143.013c_test.rar
VMMaker 1.3b + Arcade_OSD_1.3.rar
Powerstrip

Fine, but you don't need the VMMaker app as you're not using an ATI card.

These are the only options you should need to change in mame.ini:

monitor lcd
monitor_aspect 16:9
monitor_specs0            29000.00-50000.00,50.00-70.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,1080,1080

You'll probably need to raise that hfreq 50000 figure to something around 70000 or so, check your TV's documentation or use the MonInfo app to get the right ranges.

However that won't fix things because the main problem is this:

SwitchRes: Warning, too many active modelines for storage 251

This is probably a bug that I introduced with the last patches, or a maybe there are actually too many video modes available in your system. Could you please check with Arcade_OSD the number of resolutions reported, just activate one of the modes and you'll see the number between ().

[lettuce]

This is the info i got from moninfo........

Monitor
  Model name............... SAMSUNG
  Manufacturer............. Samsung
  Plug and Play ID......... SAM05EA
  Serial number............ n/a
  Manufacture date......... 2009, ISO week 25
  Filter driver............ None
  -------------------------
  EDID revision............ 1.3
  Input signal type........ Digital
  Color bit depth.......... Undefined
  Display type............. RGB color
  Screen size.............. 160 x 90 mm (7.2 in)
  Power management......... Not supported
  Extension blocs.......... 1 (CEA-EXT)
  -------------------------
  DDC/CI................... Not supported

Color characteristics
  Default color space...... Non-sRGB
  Display gamma............ 2.20
  Red chromaticity......... Rx 0.640 - Ry 0.330
  Green chromaticity....... Gx 0.300 - Gy 0.600
  Blue chromaticity........ Bx 0.150 - By 0.060
  White point (default).... Wx 0.313 - Wy 0.329
  Additional descriptors... None

Timing characteristics
  Horizontal scan range.... 26-68kHz
  Vertical scan range...... 24-60Hz
  Video bandwidth.......... 230MHz
  CVT standard............. Not supported
  GTF standard............. Not supported
  Additional descriptors... None
  Preferred timing......... Yes
  Native/preferred timing.. 1920x1080p at 60Hz (16:9)
    Modeline............... "1920x1080" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
  Detailed timing #1....... 1280x720p at 60Hz (16:9)
    Modeline............... "1280x720" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync

Standard timings supported
     640 x  480p at  60Hz - IBM VGA

EIA/CEA-861 Information
  Revision number.......... 3
  IT underscan............. Not supported
  Basic audio.............. Supported
  YCbCr 4:4:4.............. Supported
  YCbCr 4:2:2.............. Supported
  Native formats........... 1
  Detailed timing #1....... 1280x720p at 50Hz (16:9)
    Modeline............... "1280x720" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
  Detailed timing #2....... 1920x1080i at 60Hz (16:9)
    Modeline............... "1920x1080" 74.250 1920 2008 2052 2200 1080 1084 1094 1124 interlace +hsync +vsync
  Detailed timing #3....... 1920x1080i at 50Hz (16:9)
    Modeline............... "1920x1080" 74.250 1920 2448 2492 2640 1080 1084 1094 1124 interlace +hsync +vsync
  Detailed timing #4....... 720x480p at 60Hz (16:9)
    Modeline............... "720x480" 27.000 720 736 798 858 480 489 495 525 -hsync -vsync

CE video identifiers (VICs) - timing/formats supported
    1920 x 1080p at  60Hz - HDTV (16:9, 1:1) [Native]
    1920 x 1080p at  50Hz - HDTV (16:9, 1:1)
    1280 x  720p at  60Hz - HDTV (16:9, 1:1)
    1280 x  720p at  50Hz - HDTV (16:9, 1:1)
    1920 x 1080i at  60Hz - HDTV (16:9, 1:1)
    1920 x 1080i at  50Hz - HDTV (16:9, 1:1)
     720 x  480p at  60Hz - EDTV (16:9, 32:27)
     720 x  576p at  50Hz - EDTV (16:9, 64:45)
    1920 x 1080p at  24Hz - HDTV (16:9, 1:1)
    1920 x 1080p at  25Hz - HDTV (16:9, 1:1)
    1920 x 1080p at  30Hz - HDTV (16:9, 1:1)
    NB: NTSC refresh rate = (Hz*1000)/1001

CE audio data (formats supported)
  LPCM    2-channel, 16/20/24 bit depths at 32/44/48 kHz

CE speaker allocation data
  Channel configuration.... 2.0
  Front left/right......... Yes
  Front LFE................ No
  Front center............. No
  Rear left/right.......... No
  Rear center.............. No
  Front left/right center.. No
  Rear left/right center... No
  Rear LFE................. No

CE video capability data
  CE scan behavior......... Supports overscan and underscan
  IT scan behavior......... Supports overscan and underscan
  PT scan behavior......... Not supported
  RGB quantization range... Not supported
  YCC quantization range... Not supported

CE vendor specific data (VSDB)
  IEEE registration number. 0x000C03
  CEC physical address..... 1.0.0.0
  Supports AI (ACP, ISRC).. Yes
  Supports 48bpp........... No
  Supports 36bpp........... Yes
  Supports 30bpp........... Yes
  Supports YCbCr 4:4:4..... Yes
  Supports dual-link DVI... No
  Maximum TMDS clock....... 225MHz

Report information
  Date generated........... 21/08/2011
  Software revision........ 2.60.0.964
  Data source.............. Real-time 0x0051
  Operating system......... 6.1.7601.2.Service Pack 1

Raw data
  00,FF,FF,FF,FF,FF,FF,00,4C,2D,EA,05,00,00,00,00,19,13,01,03,80,10,09,78,0A,EE,91,A3,54,4C,99,26,
  0F,50,54,20,00,00,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,01,02,3A,80,18,71,38,2D,40,58,2C,
  45,00,A0,5A,00,00,00,1E,01,1D,00,72,51,D0,1E,20,6E,28,55,00,A0,5A,00,00,00,1E,00,00,00,FD,00,18,
  3C,1A,44,17,00,0A,20,20,20,20,20,20,00,00,00,FC,00,53,41,4D,53,55,4E,47,0A,20,20,20,20,20,01,DD,
  02,03,23,71,4B,90,1F,04,13,05,14,03,12,20,21,22,23,09,07,07,83,01,00,00,E2,00,0F,67,03,0C,00,10,
  00,B8,2D,01,1D,00,BC,52,D0,1E,20,B8,28,55,40,A0,5A,00,00,00,1E,01,1D,80,18,71,1C,16,20,58,2C,25,
  00,A0,5A,00,00,00,9E,01,1D,80,D0,72,1C,16,20,10,2C,25,80,A0,5A,00,00,00,9E,8C,0A,D0,8A,20,E0,2D,
  10,10,3E,96,00,A0,5A,00,00,00,18,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,5C

So, 148.500,1920,2008,2052,2200,1080,1084,1089,1125,1080,1080 is what i need to use for the modeline??

[Calamity]

These are the values you need:

Timing characteristics
  Horizontal scan range.... 26-68kHz
  Vertical scan range...... 24-60Hz

[/quote]

This is how they're used in the monitor_specs line:

monitor_specs0            26000.00-68000.00,48.00-60.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,1080,1080

Also, you can extract the optimal porch values for your TV from its preferred modeline:

   Modeline............... "1920x1080" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync

But you can't use the numbers in the modeline directly, you need to calculate the values out of those numbers. You can use PowerStrip for this or even Arcade_OSD, activating the 1920x1080 video mode and going into geometry settings to grab the timing values. However you don't need to do this as GroovyMAME will get the timings directly from PowerStrip. Only the values explained above should be needed.

[lettuce]

groovymame32_0143.013c_test.rar
VMMaker 1.3b + Arcade_OSD_1.3.rar
Powerstrip

Fine, but you don't need the VMMaker app as you're not using an ATI card.

These are the only options you should need to change in mame.ini:

monitor lcd
monitor_aspect 16:9
monitor_specs0            29000.00-50000.00,50.00-70.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,1080,1080

You'll probably need to raise that hfreq 50000 figure to something around 70000 or so, check your TV's documentation or use the MonInfo app to get the right ranges.

However that won't fix things because the main problem is this:

SwitchRes: Warning, too many active modelines for storage 251

This is probably a bug that I introduced with the last patches, or a maybe there are actually too many video modes available in your system. Could you please check with Arcade_OSD the number of resolutions reported, just activate one of the modes and you'll see the number between ().

Ok have tried to load Arcade_OSD but just get a small black window and the egg timer all the time, does this work in windows 7?? Is there a way to cut down the available video modes in my system so mame works??

EDIT: I dont think this is a bug in your latest test build as i have just downloaded groovymame64_0143.01b and still get the error message...

SwitchRes: Warning, too many active modelines for storage 251

[lettuce]

Ok have tried to load Arcade_OSD but just get a small black window and the egg timer all the time, does this work in windows 7?? Is there a way to cut down the available video modes in my system so mame works??

EDIT: I dont think this is a bug in your latest test build as i have just downloaded groovymame64_0143.01b and still get the error message...

SwitchRes: Warning, too many active modelines for storage 251

Is this possible?

[Calamity]

It's strange you have so many video modes available in that system, probably several instances of each mode are being listed for some reason. I've just arrived today, hopefully in a day or two I can make a patch so it won't crash because of that, I'm curious to see which modes are listed. By the way, have you tried Hyperspin in that system?

[lettuce]

It's strange you have so many video modes available in that system, probably several instances of each mode are being listed for some reason. I've just arrived today, hopefully in a day or two I can make a patch so it won't crash because of that, I'm curious to see which modes are listed. By the way, have you tried Hyperspin in that system?

How do i check to see what modes are listed? No i havent tried Hyperspin yet, will that make a difference?

[Calamity]

How do i check to see what modes are listed? No i havent tried Hyperspin yet, will that make a difference?
[/quote]

I was just curious as HS is known to crash when many resolutions are available, but I don't know if it only happens with my hacked drivers or is a general rule.

[lettuce]

Calamity, you come up with a patch for this yet so it doesnt crash?

[Calamity]

Calamity, you come up with a patch for this yet so it doesnt crash?

Hi lettuce,

I've just uploaded a patch that should at least avoid the crash, check here:

http://mario.groovy.org/GroovyMame/WindowsATIDrivers/

file is groovymame32_0143.013c_test2.rar

Please run it from command line like this:

      mame 1942 -ps -monitor lcd -video d3d -v -md 4 >1942.txt

Then post here the txt log file so we can check which video modes your system is reporting.

Thanks!

[lettuce]

Ok have attached the 1942.txt file.

Mame run fine now, no error messages.....but the display didnt look that great very blocky on my LCD screenn guess thats cos there no filtering going on. What the best way to get a more authentic arcade monitor look?

[Calamity]

Ok have attached the 1942.txt file.

Mame run fine now, no error messages.....but the display didnt look that great very blocky on my LCD screenn guess thats cos there no filtering going on. What the best way to get a more authentic arcade monitor look?

Thanks for the log, it helped me to catch a bug that I've just fixed. Now the refresh will be more accurate when using LCD & PowerStrip. I've made this new build as groovymame32_0143.013c_test.rar and deleted the other files. Make sure to get the new one.  It would be great if you have could get me the new log for 1942.

Yep it's supposed to look blocky as it's not stretching nor filtering the image if possible, only scaling. Use the new hlsl effects to make it look like an arcade monitor. You'll need a pretty decent card to use it fluently at 1920x1080.

[lettuce]

OK have attached the new log. GFX card should be up to the job, am using a Nvidia GTX 560 Ti card. What command do i need to run so hlsl is enabled?

But i did get an error  message  when  i quit  out  of 1942........



Have just tried some other roms but their displaying in 16:9 not 4:3, why is this?

[Calamity]

Thanks for the log! I wanted to check is the bug was fixed, I see it is.

Just ignore that error message, it's because your running it in Win7, but as you're using PowerStrip the access to the registry is unnecessary.

If you want the correct the aspect ratio (4:3), open mame.ini and edit these options:

monitor_aspect 16:9
keepaspect 1

HLSL effects are somewhat tricky to set up, I'm not the best one to give you that info, this thread may help you:

http://www.mameworld.info/ubbthreads/showflat.php?Cat=&Number=255593

Also, try adding the -syncrefresh -soundsync params to your commandline or mame.ini to get rid of tearing and sound stuttering. When doing this, try games like mk or donpachi which run at refresh rates different than 60, and check if you can get smooth scrolling and if your TV can handle those refresh rates properly.

[lettuce]

Cheers Calamity!!!

So in a fresh mame.ini file what are the only options i should be changing for the perfect setup for using an LCD display??

[Calamity]

Cheers Calamity!!!

So in a fresh mame.ini file what are the only options i should be changing for the perfect setup for using an LCD display??

In your case:

monitor lcd
monitor_aspect 16:9
monitor_specs0            26000.00-68000.00,48.00-60.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,1080,1080
powerstrip 1

video d3d
keepaspect 1
syncrefresh 1
soundsync 1

[lettuce]

Cheers Calamity!!!

So in a fresh mame.ini file what are the only options i should be changing for the perfect setup for using an LCD display??

In your case:

monitor lcd
monitor_aspect 16:9
monitor_specs0            26000.00-68000.00,48.00-0.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,1080,1080
powerstrip 1                
video d3d
keepaspect 1
syncrefresh 1
soundsync 1

Ok i have created a new config file and added the changes you listed plus also HLSL enabled. I am now greeted with the following error message......




Also the modeline you listed had an error in, just incase anyone else was going ti use it...

26000.00-68000.00,48.00-0.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,1080,1080 (WRONG)
26000.00-68000.00,48.00-60.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,1080,1080  (CORRECT)


EDIT

Found out why, i needed the HLSL folder with the .fx file in. But now when i load a rom, i just get a black screen for a while and then different coloured screens slowly coming up, if i press '5' for credit the screen stops changing colour now and again and goes straight to a black screen again!!

[Calamity]

You need the hlsl folder and the artwork folder too, download mainstream MAME and grab the folders from there, hopefully it's that.

Thanks, I fixed the modeline in case someone used it.

[lettuce]

Just tried Mortal Kombat, and i my LCD tells me that the mode isnt supported 

[Calamity]

Just tried Mortal Kombat, and i my LCD tells me that the mode isnt supported 

mk runs at 54 Hz...

Try by changing your values from 48.00-60.00 to 55.00-60.00 or so until you find the right ones where your TV works fine.

[lettuce]

Just tried Mortal Kombat, and i my LCD tells me that the mode isnt supported  

mk runs at 54 Hz...

Try by changing your values from 48.00-60.00 to 55.00-60.00 or so until you find the right ones where your TV works fine.

It seem to be working now at 48.00-60.00, it must have been because i was test the desktop res set to 720p and not 1080p. Isnt it better to have my desktop res as low as possible to get a more authentic arcade look??

Regarding the 48.00-60.00 value i take it this is refering to the refresh rate that the LCD accepts? So what happens to roms that have a lower refresh than 48??

EDIT: Tried MK 1,2, and 3 all work fine, but mk 4 give me the mode not supportted bu my LCD. What Hz's does MK4 run at?

[Calamity]

It seem to be working now at 48.00-60.00, it must have been because i was test the desktop res set to 720p and not 1080p. Isnt it better to have my desktop res as low as possible to get a more authentic arcade look??

Nop. Modern drivers seem to emulate lower resolutions when a LCD monitor is attached, so the only genuine resolution is the LCD's native one. If a "emulated" resolution is enabled, PowerStrip won't be able to use the new settings.

The other reason is that if a non-native resolution is used, the LCD screen will need to perform scaling. It's better to perform scaling on the software side so we have full control on the results and feed the screen with a already scaled picture. Then use MAME HLSL options to achieve the arcade look, which achieve better results the higher the resolution is. The problem is that if the resolution is too high, the video card won't be powerful enough to work fluently with HLSL enabled.

Another reason is that the higher the native resolution of our LCD, more chances are that we'll achieve a clean integer scaling of most original resolutions.

Regarding the 48.00-60.00 value i take it this is refering to the refresh rate that the LCD accepts? So what happens to roms that have a lower refresh than 48??

EDIT: Tried MK 1,2, and 3 all work fine, but mk 4 give me the mode not supportted bu my LCD. What Hz's does MK4 run at?

Games with refresh lower than 48 Hz are very rare, anyway they're refresh will be raised to 48.

In mk, go to the character selection screen and observe the scroll, let me know if it is smooth. Press F11 to check if the games runs 100%

[lettuce]

Do you mean the scrolling on the title screen where the characters faces are scolling up and down on the sides, or on the tower where it says who you'll be fighting?? In both instances the scrolling is smooth, but it says that its running at 110%!!

[Calamity]

Do you mean the scrolling on the title screen where the characters faces are scolling up and down on the sides, or on the tower where it says who you'll be fighting?? In both instances the scrolling is smooth, but it says that its running at 110%!!

Both are relevant, but they should run at 100% (54 Hz). Are you launching mk from command line or from the internal MAME's UI? I'd need to see the logs to know what's not working.

[lettuce]

From the command line....i have noticed a few games not running at 100% speed, some slower 98% and some a bit fast 105% etc. What command line did i need to input to get you the logs...same as before??

[Calamity]

Yes, same command line, -v -md 4 >romname.txt is what's needed for the logs.

It sounds like powerstrip option is not working otherwise you'd have more or less constant 100%.

[lettuce]

Ok have attached the file for mk. Was i supposed to do anything special with powerstrip other than just install it?

On a side note im still unable to get HLSL option to work, i can hear the game running in the background but i get just a black display that changes colour now and again, i can  get the in game menu system (TAB) to display however!? So at the moment am just using a scanline png effect.

[Calamity]

Thanks, it's a bug, similar to the other one, I'll have a fix for it tomorrow.

I don't know what is wrong with HLSL, try testing the same in normal MAME to see if it works.

[lettuce]

Has this Bug been...squashed yet?

[Calamity]

Has this Bug been...squashed yet?

Yes, I've just uploaded a new test version that should fix that.

[lettuce]

cool, can i use the same mame.ini file?

[lettuce]

Just tried the latest version, and MK is still running at 110%

[Calamity]

Just tried the latest version, and MK is still running at 110%

Oh damn. I know what the bug is but for some reason it's still there. I'm going to do a do a bullet proof fix. If you had a moment to paste that log it would be interesting.

[lettuce]

Regarding the HLSL setting, i have downloaded mameui32 and copied over the mame.ini file from groovymame and HLSL works fine (however mame is running at super speed). I then copied groovymame exe file into the mameui32 folder to see if it was some folder or file groovymame may have been missing in order for HLSL to work correctly but this didnt work, i still got the black screen with it changing colour now and again.

I have a idea on this though, as i tried running HLSL with mortal kombat and as usual got a black display but then after a few seconds got loads of different colour flashing up.....now MK has the character faces scrolling down each side of the screen on the title screen doesnt it, which this flashing display kind of simulated. Its as if when running HLSL its magnitifed the screen loads of times so all im seeing is just one pixel that is taking up the whole screen hence the different coloured fast flashing display on MK, would this make sense??

ill get the log in a few mins for ya

[lettuce]

OK have attached 2 files one with HLSL running and one without, maybe the HLSL one will show a bug why it isnt working with Groovymame?

[Calamity]

I'm sure I got HLSL working here, however that issue you're seeing might be a consecuence of something I broke with the last patches in this experimental groovymame build, not sure. Unfortunately we can't test against the "official" groovymame build because that one didn't work in your system.