-= Helpp! About 2 give up - WG 25k7197 =-

[Rodman]

Hi People ! Gr8 work!

My setup:

Midway Mortal Kombat Cab
Original Monitor: WG 25k7197
GFX: Onboard ATI Radeon X1200

Win XP SP3
Catalyst: crt_emudriver_9.3_1.2a_xp32
Soft15kHz

Been runnin my cab linux - advmame/advmenu with a few generated modelines - loads fun, no probs...

Here in my new house - my new arcade / home cinema i am setting up from scratch once again - winXP this time - wanting to get pixelperfect mame ....

Sof15kHz produces some useable desktop modes (including 800x600i).
Most of the low res modes (Quickres switch) are not working.

VMMaker produces a ton of modes from the xml.

Only a handfull work, most are scrambled.

Presets tried: Generic, CGA, H9110


Please help!

Ablut to swich back 2 my linux setup (but i dont want to)

R.

Vmmaker creates

[Sledge]

Post your VMMaker.ini and mame.ini files
in VMMaker and mame try these settings:
Hantarex MTC 9110 (H9110)
monitor_specs0    15625-16670, 49.5-65, 2.000, 4.700, 8.000, 0.064, 0.160, 1.056, 0, 0, 288, 448

they supposedly have worked for someone else for a WG 25k7131 ..maybe similar for you

[Rodman]

Hi Sledge!

Thx for the quick reply!

My VMMaker.ini;

As u might see: dotclock has already been raised.... no change..
Didnt post my mame.ini - as i´m trying to fix my modes first...

Thx, R.




; VideoModeMaker - Options
; ------------------------
   
; 1. MAME
; -------

; Path for Mame executable, in case we want to extract xml information from it.

   MameExe = "G:\Mame149\mame.exe"

; Path for Mame ini folder, in case we want to create an ini file for each game.
; Important: existing ini files will be overwritten.

   IniPath = "G:\Mame\ini\"

; Mame options.

   ListFromXML = 1      ; Processes Mame XML and get video mode list from it
   GenerateXML = 1      ; Extracts XML from Mame (only needed once)
   OnlyListMain = 0   ; Only list resolutions for games contained in MameMain.txt
   GenerateInis = 0   ; Creates an ini file for each Mame game, in the IniPath folder
   SDLMame = 0      ; Use SDLMame specific options

; Monitor orientation

   MonitorHorizontal = 1   ; 0 = Rotating monitor: horizontal and vertical games at their native resolution
            ;     Suitable for users that physically rotate their CRTs
            ; 1 = Horizontal monitor: horizontal games run at their native resolution and
            ;     vertical games are rotated to fit in horizontal monitor   

   RotatingDesktop = 0   ; Specifies if both desktop and monitor are rotated

; Aspect ratio for vertical games on horizontal monitor
;    4:3 (keeps original aspect ratio)
;    3:3 (stretches to square format)
;    3:4 (stretches to full screen)
;   h:v (custom aspect ratio)

   VerticalAspect = "4:3"


; 2. MONITOR
; ----------

; Monitor Type. Valid types: D9800, D9400, D9200, EGA, VGA, MULTI, H9110, PAL, NTSC, GENERIC, CUSTOM

   MonitorType = "H9110"


; Monitor CUSTOM. These values will be used if MonitorType = "CUSTOM"
;
; monitor_specs0-6  HfreqMin-HfreqMax, VfreqMin,VfreqMax, HFrontPorch, HSyncPulse, HBackPorch, VfrontPorch, VSyncPulse, VBackPorch, HSyncPol, VSyncPol, ActiveLinesLimit, VirtualLinesLimit
;
;    * HfreqMin-HfreqMax: Minimum and maximum horizontal frequency, in Hz. Defines the range of horizontal frequencies the monitor is capable to sync.
;       The higher the horizontal frequency, the higher the vertical resolution available for the same vertical refresh.
;       The higher the horizontal frequency, the higher the vertical refresh available for the same vertical resolution.
;       The higher the horizontal frequency, the lower the horizontal amplitude of active video (narrower picture).
;
;   * VFreqMin-VfreqMax: Minimum and maximum vertical frequency, in Hz, Defines the range of vertical frequencies the monitor is capable to sync.
;
;   * HFrontPorch, HSyncPulse, HBackPorch: Horizontal timing and geometry, values in µs
;
;   * VfrontPorch, VSyncPulse, VBackPorch: Vertical timing and geometry, values in ms
;
;   * HSyncPol,VSyncPol: sync polarities, 0 = negative, 1 = positive.
;
;   * ActiveLinesLimit: Vertical resolutions until ActiveLinesLimit value included, are generated as progressive, regardless the possibility
;                           of obtaining the required vertical refresh value.
;
;   * VirtualLinesLimit: Vertical resolutions above ActiveLinesLimit and below VirtualLinesLimit are virtualized, that is, an interlaced resolution
;                            bigger that the native one is generated, with the right refresh, and "hardware stretch" is applied.
;                            Vertical resolutions above VirtulaLinesLimit are generated as interlaced, without any stretching.

   ;monitor_specs0    15625-16200, 49.50-200.00, 2.000, 4.700, 8.000, 0.064, 0.160, 1.056, 0, 0, 288, 448
        monitor_specs0    15250-15700, 49.5-65, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 288, 448

; Tolerance for horizontal frequency, in kHz, enables extending the range defined by [ HfreqMin, HfreqMax ]
; The resulting allowed frequency range will be [ HfreqMin - HfreqTolerance, HfreqMax + HfreqTolerance ]

   HfreqTolerance = 0.010


; 3. MODELINE GENERATOR
; ---------------------

; Total number of modelines to generate. Here are the recommended values for each driver version:
; CRT_Emudriver, based on Catalyst 6.5:   160 modes (accepts up to 200, but above 160 HyperSpin will refuse to load)
; CRT_Emudriver, based on Catalyst 9.3:   120 modes (accepts some more but above 120 you can get some blue screens)
; Regular Catalyst                    :    60 modes (won't accept any more)

   TotalModes = 120

; If enabled, only creates modes with 32 bits per pixel color depth

   Only32BPPModes = 0

; Method for mode table generation. If Mame xml is processed, that will create a lot of different video modes, so the mode table
; will be optimized keeping the most relevant ones, and dropping the rest, to keep below the TotalModes value.
;
; 0 = Static table: modelines are generated keeping their original vertical refresh. This method is intended to be used in
;     combination with ini files for each game.
;
; 1 = Dynamic table: a table of dummy modes is created using xres and yres values while ignoring vfreq. This method is intended
;     to be used in combination with Switchres or Groovymame. No ini files are required using this method (you should disable the
;     GenerateInis option).
;
; 2 = Magic table: a table of 'magic resolutions' is created, by ignoring xres and vfreq and just keeping yres. This method greatly reduces
;     the total number of modes in the list. It's only supported by GroovyMAME, and is intended as a workaround for the Hyperspin issue.

   ModeTableMethod_Custom = 0
   ModeTableMethod_XML = 1

; Minimum resolution values (these will be used instead of lower values)

   XresMin_XML = 240
   YresMin_XML = 240
   YresRound_XML = 4

   XresMin_Custom = 240
   YresMin_Custom = 160
   YresRound_Custom = 0

; Minimum dotclock value allowed by the video card, in MHz (i.e. DotClockMin = 7.010)

   DotClockMin = 7.010

; Number of iterations used by the mode generator [0,5]. The higher the number of iterations, the bigger the accuracy of the vertical
; refreshed obtained, normally at the cost of increasing the horizontal frequency strictly required.

   Iterations = 0

; Specifies if the refresh label is multiplied by 10 before rounding (experimental).

   VFreqLabelx10 = 0

; 4. DRIVER
; ---------

; Path for the driver folder

   DriverPath = ".\Driver\"

; If UpdateRegistry is enabled, UpdateDriver will only work if the driver version found in DriverPath matches the one installed
; in the system.

   UpdateRegistry = 1   ; Specifies if the video card registry section will be updated with the new video modes
            ; (will only work in combination with CRT_EMUDriver).
      
   UpdateDriver = 0   ; Specifies if the driver files in DriverPath will be updated with the new video modes, for
            ; future installations.

   AnyCatalyst = 0      ; Allows modelines to be installed for any Catalyst version. This option is experimental and
            ; known to produce some problems.

[Sledge]

try changing these:

MonitorType = "H9110"
to
MonitorType = "CUSTOM"

TotalModes = 120
to
TotalModes = 100
above is just for safety sake, you can raise it later

ModeTableMethod_Custom = 0
to
ModeTableMethod_Custom = 1

let us know if it helps...

How are you testing the modes? in ArcadeOSD?
Also.. I'm not sure why your VMMaker.ini is formatted differently to mine.. do you have the latest version?

[Rodman]

Testing with ArcadeOSD

My ver is: VMMaker_1.3c_Arcade_OSD_1.3b

Is there a newer one???

R.

[Sledge]

Nope.. that's it.. but your file looks a bit different to mine.. (I was looking at my old one)
it's been updated all good

[Calamity]

Hi Rodman,

Try increasing the dotclockmin to 8.0, and use the same value in mame.ini. That should work. Also, post your modelines.txt file to double check if it's doing what's supposed to do.

[Rodman]

Here are the testresults....

After deinstalling Soft15khz
and reinstallyng the modified Catalyst

Monitor: CUSTOM
Max Modes 100
CustomM 1

Created 100 Modes, 3 dropped

Only a handfull working just as before....

lowestworking: 312x288

with soft15kHz not installed all the interlaced modes (640X480, 800x600,1024x768) not working....

Where is the problem?

My gfx card is supported and working since some modes are doin well
the monitor works well....

what can i do .......

 

R.

@ Calamity:

Thx for your gr8 work!!!!!!!!!!

Tryin your settings -
does VMMaker use the mame.ini???

Thx, R.

[Sledge]

no.. it only looks at the mame.exe to extract videomodes from..

[Calamity]

lowestworking: 312x288

This is completely normal and expected with that card.

with soft15kHz not installed all the interlaced modes (640X480, 800x600,1024x768) not working....

This shouldn't happen, so... post your modelines.txt to see what's happening. It's probably pushing the hfreq a little bit too high for your current monitor adjustment, did you try tweaking the hfreq/vfreq potentiometers?

[Rodman]

How was the correct line for the pclock in mame.ini...

is it
dotclockmin  8000

[Calamity]

It's the same format, in MHz: dotclock_min 8.0

Look for the right option under "SWITCHRES CORE OPTIONS".

Anyway, that's only for GroovyMAME, I thought you were already testing games, so try fixing your modes first with VMMaker.

[Rodman]

Thats what i thougt - no ... far from testin games 

here is my modes

Modeline "376x256_59 16.23KHz 58.58Hz" 8.030 376 392 432 496 256 258 261 277 -hsync -vsync
Modeline "376x272_55 16.23KHz 55.38Hz" 8.030 376 392 432 496 272 274 277 293 -hsync -vsync
Modeline "384x256_58 16.18KHz 58.42Hz" 8.160 384 400 440 504 256 258 261 277 -hsync -vsync
Modeline "384x288_52 16.18KHz 52.37Hz" 8.160 384 400 440 504 288 290 293 309 -hsync -vsync
Modeline "400x240_60 15.64KHz 59.91Hz" 8.130 400 416 456 520 240 242 245 261 -hsync -vsync
Modeline "400x248_60 16.15KHz 60.03Hz" 8.510 400 416 456 528 248 250 253 269 -hsync -vsync
Modeline "400x256_59 16.21KHz 58.51Hz" 8.540 400 416 456 528 256 258 261 277 -hsync -vsync
Modeline "400x264_57 16.21KHz 56.87Hz" 8.540 400 416 456 528 264 266 269 285 -hsync -vsync
Modeline "400x272_55 16.21KHz 55.32Hz" 8.540 400 416 456 528 272 274 277 293 -hsync -vsync
Modeline "400x280_54 16.21KHz 53.85Hz" 8.540 400 416 456 528 280 282 285 301 -hsync -vsync
Modeline "400x288_52 16.21KHz 52.45Hz" 8.540 400 416 456 528 288 290 293 309 -hsync -vsync
Modeline "416x240_60 15.66KHz 59.99Hz" 8.500 416 432 472 544 240 242 245 261 -hsync -vsync
Modeline "416x256_58 16.20KHz 58.48Hz" 8.820 416 432 472 544 256 258 261 277 -hsync -vsync
Modeline "432x240_60 15.67KHz 60.04Hz" 8.760 432 448 488 560 240 242 245 261 -hsync -vsync
Modeline "432x248_60 16.13KHz 59.97Hz" 9.430 432 456 504 584 248 250 253 269 -hsync -vsync
Modeline "432x256_58 16.18KHz 58.42Hz" 9.460 432 456 504 584 256 258 261 277 -hsync -vsync
Modeline "432x264_57 16.18KHz 56.78Hz" 9.460 432 456 504 584 264 266 269 285 -hsync -vsync
Modeline "432x272_55 16.18KHz 55.23Hz" 9.460 432 456 504 584 272 274 277 293 -hsync -vsync
Modeline "432x280_54 16.18KHz 53.76Hz" 9.460 432 456 504 584 280 282 285 301 -hsync -vsync
Modeline "432x288_52 16.18KHz 52.37Hz" 9.460 432 456 504 584 288 290 293 309 -hsync -vsync
Modeline "448x240_60 15.67KHz 60.04Hz" 9.390 448 472 520 600 240 242 245 261 -hsync -vsync
Modeline "456x240_60 15.66KHz 60.01Hz" 9.530 456 480 528 608 240 242 245 261 -hsync -vsync
Modeline "456x256_58 16.19KHz 58.45Hz" 9.850 456 480 528 608 256 258 261 277 -hsync -vsync
Modeline "456x264_57 16.19KHz 56.81Hz" 9.850 456 480 528 608 264 266 269 285 -hsync -vsync
Modeline "464x240_60 15.65KHz 59.98Hz" 9.650 464 488 536 616 240 242 245 261 -hsync -vsync
Modeline "464x256_59 16.21KHz 58.51Hz" 9.990 464 488 536 616 256 258 261 277 -hsync -vsync
Modeline "480x160_60 15.64KHz 59.92Hz" 9.890 480 504 552 632 160 202 205 261 -hsync -vsync
Modeline "480x200_60 15.64KHz 59.92Hz" 9.890 480 504 552 632 200 222 225 261 -hsync -vsync
Modeline "480x240_60 15.64KHz 59.92Hz" 9.890 480 504 552 632 240 242 245 261 -hsync -vsync
Modeline "480x256_58 16.20KHz 58.48Hz" 10.220 480 504 552 632 256 258 261 277 -hsync -vsync
Modeline "480x464_60 15.64KHz 60.03Hz" 9.870 480 504 552 632 464 474 479 521 interlace -hsync -vsync
Modeline "480x480_60 15.64KHz 60.03Hz" 9.870 480 504 552 632 480 482 487 521 interlace -hsync -vsync
Modeline "496x192_60 15.69KHz 60.13Hz" 10.150 496 520 568 648 192 218 221 261 -hsync -vsync
Modeline "496x240_60 15.69KHz 60.13Hz" 10.150 496 520 568 648 240 242 245 261 -hsync -vsync
Modeline "496x256_59 16.21KHz 58.50Hz" 10.620 496 520 568 656 256 258 261 277 -hsync -vsync
Modeline "496x480_60 15.62KHz 59.98Hz" 10.140 496 520 568 648 480 482 487 521 interlace -hsync -vsync
Modeline "512x192_60 15.65KHz 59.95Hz" 10.520 512 536 584 672 192 218 221 261 -hsync -vsync
Modeline "512x224_60 15.65KHz 59.95Hz" 10.520 512 536 584 672 224 234 237 261 -hsync -vsync
Modeline "512x239_60 15.65KHz 59.95Hz" 10.520 512 536 584 672 239 241 244 261 -hsync -vsync
Modeline "512x240_60 15.65KHz 59.95Hz" 10.520 512 536 584 672 240 242 245 261 -hsync -vsync
Modeline "512x244_60 15.84KHz 60.00Hz" 10.650 512 536 584 672 244 245 248 264 -hsync -vsync
Modeline "512x256_58 16.20KHz 58.49Hz" 11.000 512 536 592 680 256 258 261 277 -hsync -vsync
Modeline "512x288_52 16.20KHz 52.44Hz" 11.000 512 536 592 680 288 290 293 309 -hsync -vsync
Modeline "512x448_60 15.62KHz 59.98Hz" 10.510 512 536 584 672 448 466 471 521 interlace -hsync -vsync
Modeline "512x478_60 15.62KHz 59.98Hz" 10.510 512 536 584 672 478 481 486 521 interlace -hsync -vsync
Modeline "512x480_60 15.62KHz 59.98Hz" 10.510 512 536 584 672 480 482 487 521 interlace -hsync -vsync
Modeline "512x512_58 16.20KHz 58.39Hz" 11.000 512 536 592 680 512 515 520 555 interlace -hsync -vsync
Modeline "528x240_60 15.67KHz 60.02Hz" 10.910 528 552 608 696 240 242 245 261 -hsync -vsync
Modeline "544x240_60 15.64KHz 59.93Hz" 11.140 544 568 624 712 240 242 245 261 -hsync -vsync
Modeline "544x242_60 15.73KHz 60.03Hz" 11.190 544 568 624 712 242 243 246 262 -hsync -vsync
Modeline "544x480_60 15.64KHz 60.05Hz" 11.120 544 568 624 712 480 482 487 521 interlace -hsync -vsync
Modeline "560x240_60 15.67KHz 60.03Hz" 11.520 560 584 640 736 240 242 245 261 -hsync -vsync
Modeline "576x240_60 15.65KHz 59.97Hz" 11.780 576 600 656 752 240 242 245 261 -hsync -vsync
Modeline "592x240_60 15.65KHz 59.98Hz" 12.020 592 616 672 768 240 242 245 261 -hsync -vsync
Modeline "600x240_60 15.66KHz 59.99Hz" 12.170 600 624 680 776 240 242 245 261 -hsync -vsync
Modeline "608x240_60 15.65KHz 59.98Hz" 12.260 608 632 688 784 240 242 245 261 -hsync -vsync
Modeline "624x288_52 16.20KHz 52.42Hz" 13.230 624 648 712 816 288 290 293 309 -hsync -vsync
Modeline "640x200_60 15.67KHz 60.05Hz" 13.040 640 664 728 832 200 222 225 261 -hsync -vsync
Modeline "640x224_60 15.67KHz 60.05Hz" 13.040 640 664 728 832 224 234 237 261 -hsync -vsync
Modeline "640x240_60 15.67KHz 60.05Hz" 13.040 640 664 728 832 240 242 245 261 -hsync -vsync
Modeline "640x244_60 15.82KHz 59.92Hz" 13.180 640 664 728 832 244 245 248 264 -hsync -vsync
Modeline "640x256_58 16.20KHz 58.50Hz" 13.720 640 672 736 848 256 258 261 277 -hsync -vsync
Modeline "640x480_60 15.62KHz 59.95Hz" 12.980 640 664 728 832 480 482 487 521 interlace -hsync -vsync
Modeline "648x240_60 15.67KHz 60.04Hz" 13.140 648 672 736 840 240 242 245 261 -hsync -vsync
Modeline "656x240_60 15.67KHz 60.04Hz" 13.280 656 680 744 848 240 242 245 261 -hsync -vsync
Modeline "656x256_59 16.21KHz 58.52Hz" 14.010 656 688 752 864 256 258 261 277 -hsync -vsync
Modeline "664x496_60 16.18KHz 60.06Hz" 14.090 664 696 760 872 496 499 504 539 interlace -hsync -vsync
Modeline "672x224_60 15.66KHz 60.00Hz" 13.760 672 704 768 880 224 234 237 261 -hsync -vsync
Modeline "672x240_60 15.66KHz 60.00Hz" 13.760 672 704 768 880 240 242 245 261 -hsync -vsync
Modeline "672x256_58 16.20KHz 58.47Hz" 14.530 672 704 776 896 256 258 261 277 -hsync -vsync
Modeline "672x272_55 16.20KHz 55.28Hz" 14.530 672 704 776 896 272 274 277 293 -hsync -vsync
Modeline "672x288_52 16.20KHz 52.42Hz" 14.530 672 704 776 896 288 290 293 309 -hsync -vsync
Modeline "688x240_60 15.65KHz 59.95Hz" 14.030 688 720 784 896 240 242 245 261 -hsync -vsync
Modeline "688x512_58 16.19KHz 58.34Hz" 14.780 688 720 792 912 512 515 520 555 interlace -hsync -vsync
Modeline "704x240_60 15.64KHz 59.92Hz" 14.530 704 736 808 928 240 242 245 261 -hsync -vsync
Modeline "704x256_58 16.20KHz 58.48Hz" 15.040 704 736 808 928 256 258 261 277 -hsync -vsync
Modeline "704x272_55 16.20KHz 55.29Hz" 15.040 704 736 808 928 272 274 277 293 -hsync -vsync
Modeline "704x480_60 15.64KHz 60.03Hz" 14.490 704 736 808 928 480 482 487 521 interlace -hsync -vsync
Modeline "704x528_57 16.20KHz 56.74Hz" 15.040 704 736 808 928 528 531 536 571 interlace -hsync -vsync
Modeline "720x240_60 15.64KHz 59.93Hz" 14.780 720 752 824 944 240 242 245 261 -hsync -vsync
Modeline "728x544_55 16.21KHz 55.23Hz" 15.550 728 760 832 960 544 547 552 587 interlace -hsync -vsync
Modeline "736x240_60 15.66KHz 60.00Hz" 15.040 736 768 840 960 240 242 245 261 -hsync -vsync
Modeline "736x256_59 16.21KHz 58.53Hz" 15.690 736 768 840 968 256 258 261 277 -hsync -vsync
Modeline "736x272_55 16.21KHz 55.33Hz" 15.690 736 768 840 968 272 274 277 293 -hsync -vsync
Modeline "752x240_60 15.66KHz 60.01Hz" 15.260 752 784 856 976 240 242 245 261 -hsync -vsync
Modeline "752x560_54 16.20KHz 53.72Hz" 15.940 752 784 856 984 560 563 568 603 interlace -hsync -vsync
Modeline "768x240_60 15.67KHz 60.04Hz" 15.640 768 800 872 1000 240 242 245 261 -hsync -vsync
Modeline "768x256_58 16.18KHz 58.42Hz" 16.340 768 800 880 1008 256 258 261 277 -hsync -vsync
Modeline "768x512_58 16.18KHz 58.32Hz" 16.340 768 800 880 1008 512 515 520 555 interlace -hsync -vsync
Modeline "768x576_52 16.18KHz 52.29Hz" 16.340 768 800 880 1008 576 579 584 619 interlace -hsync -vsync
Modeline "1088x256_58 16.20KHz 58.49Hz" 23.160 1088 1136 1248 1432 256 258 261 277 -hsync -vsync
Modeline "1280x240_60 15.66KHz 59.99Hz" 25.930 1280 1328 1448 1656 240 242 245 261 -hsync -vsync

[Calamity]

Ok. Now check 376x256@59.

If it's out of sync, try moving the h-freq potentiometer slowly until it syncs.

[Rodman]

Getting the manual from WG homepage.... tryin....

If u help me get this right you´ll surely receive some nice austrian beer !
Promise

R. 

[Calamity]

That sounds good!

If you don't want to mess with your monitor, try these settings in VMMaker:

MonitorType = "CUSTOM"
monitor_specs0    15650-15700, 49.5-65, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 288, 448

These are super conservative and you won't get the best out of the vertical games in terms of resolution@refresh, but it should be good enough for now.

The best settings, in my opinion, when dealing with GroovyMAME/GroovyUME and cards with difficulties for low dotclocks (=> horizontal scaling required), is to use magic resolutions:

ModeTableMethod_XML = 2

[Sledge]

monitor_specs0    156250-15700

ERROR?                 ^^^^

[Calamity]

monitor_specs0    156250-15700

ERROR?                 ^^^^

Sure, my mistake, I've edited my post, thanks.

[Rodman]

Sir thou art a fu...n genius !

It was the V-Hold........

Man man man man man man man man man

How many hours did i spend on that now .....
LOL

I considered it alright becouse some modes worked flawlessly..... damn damn damn...

Status:
All the generated modes are working perfectly....


To Do:
- Check if there even is a low dotclock problem ......
- Setup Groovymame and hyperspin (or Advmenuplus)
- Finish MK on very hard (again)

Any idea what the precise specs for my 25k7197 would be???


Calamity - thx again!
Cant be more happy!

Please email or PM me a postal adress!

R.

[Sledge]

Any idea what the precise specs for my 25k7197 would be???

best idea would be to adjust them through ArcadeOSD on a res like 640x288 or 640x256 (depending on whether you have limited it to that height) and write those settings down..
then put them into mame.ini/vmmaker

see how it goes...

[Rodman]

Thx again - a few new questions have risen....


- How do i remove modes? (I want to remove the interlaced ones)
   I suppuse it aint enough to remove from modelines file ....
   Does groovymame / switchres use the registry modes or where are they stored???

- Please specify how to read out the specsline for my monitor form an ArcadeOSD Mode

Thx!

 
 

[Sledge]

use Winmodelines to remove modelines

[Rodman]

Thx!

What modes does groovymame use?
The ones stored in the registry?

Advmane used modes stored in the .ini file

Thx

[lcmgadgets]

Jeopardy answer: Rodman, Sledge, Calamity.

Question: Who r 3 guys on the byoac forum who I don't remember seeing before today who have now joined the ranks of those who work, talk, & think several quantums above my level?

You're a credit to this site, guys. Keep posting!   

[Rodman]

lol

i

[Calamity]

Hi Rodman,

You don't really need to remove interlaced modes. VMMaker is creating those because it understands you're going to need them for GroovyMAME. You could just instruct GroovyMAME not to use interlaced modes if you like. If you really really want to get ride of those modes then get Winmodelines, this tool will allow you to edit the modelines stored in the registry.

GroovyMAME creates its own modelines on the fly, overriding the ones in the registry, which are just used as dummy modes (we need a previous definition in order to actually be able to edit it on the fly).

For a standard arcade monitor, it's actually faster to center the picture by using the monitor controls. All modelines should have been created with similar borders, so it should be easy to find a more or less universal geometry adjustment.

[Sledge]

Jeopardy answer: Rodman, Sledge, Calamity.

Question: Who r 3 guys on the byoac forum who I don't remember seeing before today who have now joined the ranks of those who work, talk, & think several quantums above my level?

You're a credit to this site, guys. Keep posting!   

please... no.. don't event think of putting me in the same category as Calamity...
I've got barely a clue about this stuff

[Rodman]

You could just instruct GroovyMAME not to use interlaced modes if you like. If you really really want to get ride of those modes then get Winmodelines...

Perfect - thats what i was looking for...

I suppose groovymame uses the /ini/mame.ini file ...
 - can i put my monitorspecsline in there?
 - how is the command to disable interlaced modes?

GroovyMAME creates its own modelines on the fly, overriding the ones in the registry, which are just used as dummy modes (we need a previous definition in order to actually be able to edit it on the fly).

I c.....
What are the modes ArcadeOSD is using - ? the ones stored in the registry?
As far as my test show it aint the modes in the modelines.txt file...

For a standard arcade monitor, it's actually faster to center the picture by using the monitor controls. All modelines should have been created with similar borders, so it should be easy to find a more or less universal geometry adjustment.

Roger that!
As i am using your "super conservative" specs line with success, i am still lacking some modes - is there a way to get my exact monitor specs readings from ArcadeOSD?


Regards, gr8 work,
R.

[Calamity]

I suppose groovymame uses the /ini/mame.ini file ...
 - can i put my monitorspecsline in there?
 - how is the command to disable interlaced modes?

To disable interlaced modes, in mame.ini:

interlace 0

To add your custom specs, in mame.ini:

monitor custom
crt_range0    15650-15700, 49.5-65, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576

(notice the crt_range is slightly different to the monitor_specs lines)

What are the modes ArcadeOSD is using - ? the ones stored in the registry?
As far as my test show it aint the modes in the modelines.txt file...

ArcadeOSD uses the registry modelines, and can edit them, etc. Those should match the ones in Modeline.txt

As i am using your "super conservative" specs line with success, i am still lacking some modes - is there a way to get my exact monitor specs readings from ArcadeOSD?

Of course you can get your exact monitor specs from ArcadeOSD, but you can't do this by blindly tweaking the values, you need to actually understand what you're doing. Honestly the only relevant value for your practical case is how high you can push the horizontal frequency. So you can find it out by incrementing the remarked value by short steps:

crt_range0    15650-15700, 49.5-65, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576

For each value, launch pacman and see if it syncs. It will probably stop syncing once you reach 16200 or something. Keep the value right before it stops syncing.

[Rodman]

Gr8!
Thx Calamity!

I hope i find time 2morrow after my sons 4th bday party to do some testing!

Regards,
R