Main Woodworking Reviews Software Monitor/Video Maximus Arcade
Audio/Jukebox/MP3 Project Announcements Artwork Consoles Buy/Sell/Trade Meet Up
Arcade Miscellaneous Everything Else Politics n Religion Forum Discussion Wiki Discussion GroovyMAME
DOS/WinCab Merit/JVL Touchscreen Automated Projects Driving & Racing Project Arcade Old Boards
Linux Restorations Pinball MaLa Frontend controls.dat Old Archives

Unread posts | New Replies | Recent posts | Arcade | Rules | Chatroom | Wiki | File Repository | RSS


  

Author Topic: GroovyMame for arcade monitors version 0.146u4_013f  (Read 47852 times)

0 Members and 1 Guest are viewing this topic.

krick

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1639
  • Gotta have blue hair.
    • Tank + Paladin = Tankadin
Re: GroovyMame for arcade monitors version 0143.013
« Reply #400 on: August 01, 2011, 06:34:46 pm »

Well, that's not really necessary, just convenient. If you use the default settings, generic CGA monitor timings are used, that means you are constrained to a narrower hfreq range around 15.7 kHz, what is fine for most games.

However, if you are possitive your monitor supports a wider range of hfreq then it's worth setting GroovyMAME so that it makes use of that extra horizontal frequency available. This is highly useful for running vertical games on horizontal monitor closer to their native vfreq.


Hmmm...   Makes sense.

The obvious next question is how can one be positive that their monitor supports a wider range of hfreq?

My monitor is an original "Polo", not a "Polo/2", "Polo/3", or "PoloStar".

According to this Hantarex Polo manual, which I believe is the correct one...

http://mame.3feetunder.com/byoac/hantarex_polo.pdf

...it supports...

Horizontal 15,700 500 Hz adjustable
Vertical 45-65 Hz adjustable



Higgs79

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 3
Re: GroovyMame for arcade monitors version 0143.013
« Reply #401 on: August 02, 2011, 07:21:20 am »
Calamity - Many thanks for the excellent explanation.

When running groovymame with a fresh mame.ini I do get games running too fast.  That said I have not yet checked whether directdraw acceleration is enabled.  This may take me a while as I'm using an nlited and minlogon'd install of xp and dxdiag has been stripped out :(

krick - If you do manage to find correct specs for the hantarex polo I will be very intererested.  I will keep searcing as well.  In the meantime I will try the H9110 and let you know how I get on.

Thanks again to both of you

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #402 on: August 02, 2011, 08:27:27 am »
Hmmm...   Makes sense.

The obvious next question is how can one be positive that their monitor supports a wider range of hfreq?

My monitor is an original "Polo", not a "Polo/2", "Polo/3", or "PoloStar".

According to this Hantarex Polo manual, which I believe is the correct one...

http://mame.3feetunder.com/byoac/hantarex_polo.pdf

...it supports...

Horizontal 15,700 500 Hz adjustable
Vertical 45-65 Hz adjustable

Well, the horizontal range reported by Hantarex MTC 9110 is exactly the same, so we can expect that they work in a similar way. This is what I found: the [-500 Hz, 500 Hz] adjustable interval is NOT fixed around the 15.7 figure: in other words, it doesn't mean [15.200, 16.200]. Rather than that, it means that you have a 100 Hz window that you can move up or down using the hfreq potenciometer, being its lower adjustment possible [14.700, 15.700], and [15.700, 16.700] the higher possible, which is the one I use in order to get more lines out of that chassis. Resolutions below 15.7 kHz are not a problem because the modeline generator stuffs them with extra porch lines until they reach 15.7 kHz.

By the way, I assume you are aware yours is a multisync chassis, it also allows accepts 25 kHz signals. The problem is that it's not automatic, you need to manually change a jumper in the chassis to switch 15/25Khz.

When running groovymame with a fresh mame.ini I do get games running too fast.  That said I have not yet checked whether directdraw acceleration is enabled.  This may take me a while as I'm using an nlited and minlogon'd install of xp and dxdiag has been stripped out :(

Those unofficial XPs are problematic when installing CRT_Emudriver, I believe that's because they usually have newer stock display drivers and silently refuse to accept ours. You usually need to reinstall it several times, after completely uninstalling the stock driver from the Device Manager.

As an alternative test, use Arcade_OSD and run the measure_vfreq test to check if the scroll is smooth, without tearing and you get a reasonable vfreq figure.

If ddraw acceleration is disabled, all the rest is worthless. GroovyMAME relies on vsync funtionallity to properly temporize emulation.

Another possibilty is that you have manually disabled the vsync from your video card control panel. You shouldn't install any control panel (CCC) but if you do, make sure the vsync option is set so that applications decide whether to use it or not, never use the other options to override application's decisions, otherwise GroovyMAME may not have access to vsync functions.


caskad

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 61
Re: GroovyMame for arcade monitors version 0143.013
« Reply #403 on: August 06, 2011, 08:36:05 pm »


thx for the hard work !



« Last Edit: August 07, 2011, 06:59:42 pm by caskad »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #404 on: August 19, 2011, 02:26:22 pm »
This is a highly experimental build of GroovyMAME, please use it with care.

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


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


I don't have much time today and I'm leaving tomorrow for a week, I'll try to explain all the details, hopefully will be easy to use.
I'll be updating this thread in the next hours...

New features:

- "Magic resolutions".
- Improved scaling support.
- Support for LCD monitors via Powerstrip.

Magic resolutions
----------------

This is an attempt to overcome the unfamous Hyperspin issue. We keep our mode table short by using a 16-30 "magic" resolutions instead a hundred of them. This was already suggested by bitbytebit but at the moment I hadn't figured a way to make it work. The idea is to create a list like this:

Code: [Select]
## Mame ##

1234 x 240 @ 60.000000 mame
1234 x 256 @ 60.000000 mame
1234 x 272 @ 60.000000 mame
1234 x 288 @ 60.000000 mame
1234 x 304 @ 60.000000 mame
1234 x 320 @ 60.000000 mame
1234 x 336 @ 60.000000 mame
1234 x 352 @ 60.000000 mame
1234 x 368 @ 60.000000 mame
1234 x 384 @ 60.000000 mame
1234 x 400 @ 60.000000 mame
1234 x 416 @ 60.000000 mame
1234 x 432 @ 60.000000 mame
1234 x 448 @ 60.000000 mame
1234 x 464 @ 60.000000 mame
1234 x 480 @ 60.000000 mame
1234 x 496 @ 60.000000 mame
1234 x 512 @ 60.000000 mame
1234 x 528 @ 60.000000 mame
1234 x 544 @ 60.000000 mame
1234 x 560 @ 60.000000 mame
1234 x 576 @ 60.000000 mame
1234 x 592 @ 60.000000 mame
1234 x 608 @ 60.000000 mame
1234 x 624 @ 60.000000 mame
1234 x 640 @ 60.000000 mame
1234 x 656 @ 60.000000 mame
1234 x 672 @ 60.000000 mame
1234 x 688 @ 60.000000 mame
1234 x 704 @ 60.000000 mame
1234 x 720 @ 60.000000 mame
1234 x 736 @ 60.000000 mame
1234 x 752 @ 60.000000 mame
1234 x 768 @ 60.000000 mame
1234 x 784 @ 60.000000 mame
1234 x 800 @ 60.000000 mame

...where the xres is a dummy value. Then, for instance, in order to create resolution 320x240 we use the 1234x240 resolution and recalculate it with the right values on the fly. So we can create all resolutions used by MAME out of that list.

You may be wondering why not to use dummy values for both xres and yres, so we could do with only one magic resolution. The reason is that it only works for Catalyst 9.3. If yres value doesn't match it will cause a serious crash in Catalyst 6.5. That's why, by default, I've implemented the most conservative method.

The other limitation is that the "magic" resolution must be bigger than the one we want to create, otherwise the OS won't reserve enough memory for the mode. GroovyMAME already checks this for us.

Be aware I've only tested this with this two setups (which are my current ones):

- WinXP 64 + Catalyst 6.5
- WinXP 32 + Catalyst 9.3

It would be good to test the same for the other two combinations:

- WinXP 64 + Catalyst 9.3
- WinXP 32 + Catalyst 6.5

In order to setup your system for this method, download the new VMMaker 1.3b, edit vmmaker.ini as usual with your monitor type. Make sure you use the new ReslList.txt file. Then run VMMaker to install the new resolutions and restart.

Remind to set this options to zero (vmmaker.ini) as we don't need to list roms data from MAME's xml anymore:

   ListFromXML = 0
   GenerateXML = 0
   GenerateInis = 0

Pixel doubling & scaling
----------------------

Selection of scaled resolutions by any factor (x2, x3, ...) is performed automatically so you don't have to mess with options anymore. Just set up your monitor properly, using a monitor_specs line if necessary, both in vmmaker.ini and mame.ini so VMMaker calculates the right resolutions for your monitor and GroovyMAME knows which ones to pick up.

I've been testing with a SVGA CRT monitor which supports up to 1280x1024. In order to cover its whole range I needed to use this line:

   monitor_specs_0 = "29100-70000, 50-100, 1.000, 1.000, 3.000, 0.014, 0.044, 0.524, 0, 0, 1024, 800"

The last values are important. 1024 (active lines limit) limits the vertical resolution to the one accepted by the monitor. Notice that I set the virtual lines limit value to 800, as this has the side effect to limit the vertical minimum resolution to 400 (800/2). So this produces resolutions from 400 to 1024 vertical lines.

LCD monitors & Powerstrip
-------------------------

Experimental PowerStrip support has been added. It only updates current desktop resolution by now, so it can be tweaked to any desired refresh rate on the fly. So this is ideal for using with LCD monitors which actually support variable refresh rates (not all of them do).

Notice that you don't need CRT_Emudriver for this. Actually it's better not to use it.

This should work with any card supported by PowerStrip.

In order to use this feature:

- Download and install PowerStrip. Reboot. Leave PowerStrip's default options.
- Make sure to set up your desktop resolution to the LCD's native resolution.
- Set monitor option to "lcd"
- Use a proper monitor_specs line*
- Run groovymame with this options:

groovymame 1942 -ps -monitor lcd -video d3d

-ps / powerstrip is a new option that allows you to enable PowerStrip support if it's found in the system.
 monitor lcd is a new type of monitor which
-video d3d is recommended when scaling is involved, as it increases performance a lot

So for the monitor_specs line, you can just modify this one to fit your monitor:

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

...being the last values the vertical resolution of your monitor (mine is 1280x800)

Porch values are ignored here, but vertical-horizontal freq. ranges are considered internally for the modeline calculator to make decisions, so try to use the right values for those. Many LCDs just sync properly to frequencies around 60 Hz, so you can use the monitor_specs line to limit the range of vertical frequencies sent to the monitor.

You can also choose which monitor you want to use:

groovymame 1942 -ps -monitor lcd -video d3d -screen \\.\DISPLAY1

or

groovymame 1942 -ps -monitor lcd -video d3d -screen \\.\DISPLAY2

« Last Edit: August 19, 2011, 05:15:48 pm by Calamity »

cotmm68030

  • Guest
  • Trade Count: (0)
Re: GroovyMame for arcade monitors version 0143.013
« Reply #405 on: August 19, 2011, 03:22:58 pm »
Very exciting. This will continue to work with a 31kHz monitor given it's defined appropriately in the vmmaker.ini?

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #406 on: August 19, 2011, 03:49:39 pm »
Ok Cal I tested.

Good news is Hyperspin runs. Bad news is games dont display correctly.
I am running win xp 32bit with 9.3 cat drivers
Billabs multic sync monitor.
Let me tell you what I did.


Test 1
1. Backedup old mame.exe, mame.ini, Vmmaker.exe, vmmaker.ini, arcade OSD, reslist.txt
2. Used groovymame32_0143.013c_test.rar + VMMaker 1.3b + Arcade_OSD_1.3.rar
3. Config vmaker.ini to my monitor
4. renamed groovymame to mame.exe and also genereated new mame.ini via mame -cc
5. edited mame.ini to reflect my d9800 (Yes I used lowercase d in the .ini File)
5. ran vmmaker
6. reboot
7. ran pacman

Test 2

1. I looked at my vmmaker.ini file and changed those 2 lines from 0 to 1 since that how my original ones looked.
2. ran vmmaker Got a different message ( enclosed Screen shots)
3. reboot
4. Ran Pacman



Mame options.

   ListFromXML = 1      ; Processes Mame XML and get video mode list from it
   GenerateXML = 1      ; Extracts XML from Mame (only needed once)

I included files for your review. IF you want you can talk to me on MSN messenger. Dompernice@hotmail.com
I also noticed the nag screen removal didnt work even though its set to 1 by default.
« Last Edit: August 19, 2011, 03:52:41 pm by bent98 »

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #407 on: August 19, 2011, 04:19:00 pm »
bent98,

Set this options to zero:

   ListFromXML = 0
   GenerateXML = 0

... as we don't need to list xml data any more with this method.

AND set:

 UpdateRegistry = 1

... so the registry is updated with the new modes.


cotmm68030,

Scaling for 31Khz, etc. is AUTOMATIC now, so you don't need to specify anything but possibly the yresmin value, no dotclockmin needed, etc. I'll explain it above...

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #408 on: August 19, 2011, 04:51:43 pm »
I just tried and when I run pacman monitor goes black and i an hear game running but cant see anything

Parsing mame.ini
Parsing mame.ini
SwitchRes: Entering switchres_modeline_setup (0)
SwitchRes: Monitor: d9800 Orientation: horizontal Aspect 4:3
SwitchRes: MonitorLimits 15250.00-18000.00,40.00-80.00,2.187,4.688,6.719,0.190,0.191,1.018,0,0,288.0,448
SwitchRes: Hardware limits (60.6061Hz)-> YresMin= 230p, YresMax= 271p(542i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x542
SwitchRes: Starting with Horizontal freq of 19.072 and Vertical refresh of 60.61
SwitchRes: Horizontal frequency too high 19.072 vfreq 60.606
SwitchRes: Lowered horizontal frequency to  18000.000 from 19.072
SwitchRes: Vertical frequency changed to 57.508 from 60.606
SwitchRes: Original Vref 60.606061 != 57.507987
SwitchRes: # 15.250Khz -> 18.000Khz: ( | Hfreq Change | Vref Change | )
SwitchRes: # pacman [11] 400x288@57.51 18.0000Khz
SwitchRes: ModeLine          "400x288x57.51" 9.647999 400 424 472 536 288 291 294 313 -HSync -VSync

SwitchRes: MonitorLimits 18001.00-19000.00,40.00-80.00,2.187,4.688,6.719,0.140,0.191,0.950,0,0,288.0,448
SwitchRes: Hardware limits (60.6061Hz)-> YresMin= 274p, YresMax= 289p(578i)
SwitchRes: Logical limit YresMin (448/2) = 224p
SwitchRes: Setup monitor limits min=184x224 max=0x578
SwitchRes: Starting with Horizontal freq of 18.924 and Vertical refresh of 60.61
SwitchRes: # 18.001Khz -> 19.000Khz: ( Perfect Resolution )
SwitchRes: # pacman
SwitchRes: ModeLine          "400x288x60.61" 10.286544 400 424 472 544 288 291 295 312 -HSync -VSync

SwitchRes: MonitorLimits 20501.00-29000.00,40.00-80.00,2.910,3.000,4.440,0.451,0.164,1.048,0,0,480.0,768
SwitchRes: Hardware limits (60.6061Hz)-> YresMin= 304p, YresMax= 430p(860i)
SwitchRes: Logical limit YresMin (768/2) = 384p
SwitchRes: Setup monitor limits min=184x384 max=0x860
SwitchRes: Virtualized to 1136x848@60.61 28.6061Khz
SwitchRes: Starting with Horizontal freq of 28.577 and Vertical refresh of 60.61
SwitchRes: # 20.501Khz -> 29.000Khz: ( | Interlace | Doubleres | Virtualize | )
SwitchRes: # pacman [12] 1136x848@60.61 28.6364Khz
SwitchRes: ModeLine          "1136x848x60.61" 45.589089 1136 1264 1392 1592 848 874 883 945 -HSync -VSync interlace

SwitchRes: MonitorLimits 29001.00-32000.00,40.00-80.00,0.636,3.813,1.906,0.318,0.064,1.048,0,0,576.0,768
SwitchRes: Hardware limits (60.6061Hz)-> YresMin= 437p, YresMax= 481p(962i)
SwitchRes: Logical limit YresMin (768/2) = 384p
SwitchRes: Setup monitor limits min=184x384 max=0x962
SwitchRes: Starting with Horizontal freq of 38.222 and Vertical refresh of 60.61
SwitchRes: Horizontal frequency too high 38.222 vfreq 60.606
SwitchRes: Lowered horizontal frequency to  32000.000 from 38.222
SwitchRes: Vertical frequency changed to 51.447 from 60.606
SwitchRes: Original Vref 60.606061 != 51.446945
SwitchRes: # 29.001Khz -> 32.000Khz: ( | Hfreq Change | Vref Change | Doubleres | )
SwitchRes: # pacman [14] 800x576@51.45 32.0000Khz
SwitchRes: ModeLine          "800x576x51.45" 31.743999 800 816 936 992 576 586 588 622 -HSync -VSync

SwitchRes: MonitorLimits 32001.00-34000.00,40.00-80.00,0.636,3.813,1.906,0.020,0.106,0.607,0,0,576.0,768
SwitchRes: Hardware limits (60.6061Hz)-> YresMin= 505p, YresMax= 535p(1070i)
SwitchRes: Logical limit YresMin (768/2) = 384p
SwitchRes: Setup monitor limits min=184x384 max=0x1070
SwitchRes: Starting with Horizontal freq of 36.532 and Vertical refresh of 60.61
SwitchRes: Horizontal frequency too high 36.532 vfreq 60.606
SwitchRes: Lowered horizontal frequency to  34000.000 from 36.532
SwitchRes: Vertical frequency changed to 56.572 from 60.606
SwitchRes: Original Vref 60.606061 != 56.572379
SwitchRes: # 32.001Khz -> 34.000Khz: ( | Hfreq Change | Vref Change | Doubleres | )
SwitchRes: # pacman [14] 800x576@56.57 34.0000Khz
SwitchRes: ModeLine          "800x576x56.57" 34.271999 800 816 944 1008 576 577 581 601 -HSync -VSync

SwitchRes: MonitorLimits 34001.00-38000.00,40.00-80.00,1.000,3.200,2.200,0.020,0.106,0.607,0,0,600.0,768
SwitchRes: Hardware limits (60.6061Hz)-> YresMin= 536p, YresMax= 598p(1196i)
SwitchRes: Logical limit YresMin (768/2) = 384p
SwitchRes: Setup monitor limits min=184x384 max=0x1196
SwitchRes: Starting with Horizontal freq of 36.532 and Vertical refresh of 60.61
SwitchRes: # 34.001Khz -> 38.000Khz: ( | Doubleres | )
SwitchRes: # pacman [3] 800x576@60.61 36.5455Khz
SwitchRes: ModeLine          "800x576x60.61" 37.714908 800 832 952 1032 576 577 581 603 -HSync -VSync

SwitchRes v0.013: [pacman] (1) vertical (288x224@60.61)->(400x288@60.61)->(400x288@60.61)
SwitchRes: # pacman 400x288@60.61 18.9091Khz
SwitchRes:    ModeLine          "400x288x60.61" 10.286544 400 424 472 544 288 291 295 312 -HSync -VSync
SwitchRes: DefaultVideo 'System\CurrentControlSet\Control\Video\{6D0C80E8-65AE-416B-94ED-9469D6966463}\0000'
SwitchRes: DALDTMCRTBCD320X448X0X60:
 SwitchRes: (61853/68) Modeline 11.770000 320 328 376 400 448 457 459 490
SwitchRes: DALDTMCRTBCD320X480X0X50:
 SwitchRes: (61687/68) Modeline 11.590000 320 328 376 400 480 519 521 580
SwitchRes: DALDTMCRTBCD496X384X0X60:
 SwitchRes: (60796/68) Modeline 17.400000 496 544 600 680 384 396 400 427
SwitchRes: DALDTMCRTBCD512X224X0X60:
 SwitchRes: (62059/68) Modeline 10.000000 512 536 584 656 224 231 234 254
SwitchRes: DALDTMCRTBCD512X239X0X60:
 SwitchRes: (62000/68) Modeline 10.260000 512 536 584 656 239 242 245 261
SwitchRes: DALDTMCRTBCD512X240X0X60:
 SwitchRes: (61992/68) Modeline 10.310000 512 536 584 656 240 243 246 262
SwitchRes: DALDTMCRTBCD512X384X0X60:
 SwitchRes: (60668/68) Modeline 18.040000 512 568 624 704 384 396 400 427
SwitchRes: DALDTMCRTBCD512X448X0X60:
 SwitchRes: (60562/68) Modeline 18.360000 512 520 592 624 448 457 459 490
SwitchRes: DALDTMCRTBCD640X224X0X60:
 SwitchRes: (61385/68) Modeline 12.420000 640 672 728 816 224 231 234 254
SwitchRes: DALDTMCRTBCD640X240X0X50:
 SwitchRes: (61284/68) Modeline 12.420000 640 672 728 816 240 265 268 305
SwitchRes: DALDTMCRTBCD640X480X0X60:
 SwitchRes: (59314/68) Modeline 25.200000 640 656 752 800 480 490 492 525
SwitchRes: DALDTMCRTBCD1234X240X0X60:
 SwitchRes: (58107/68) Modeline 24.680000 1232 1288 1400 1568 240 243 246 262
SwitchRes: DALDTMCRTBCD1234X256X0X60:
 SwitchRes: (57821/68) Modeline 26.650000 1232 1288 1416 1592 256 259 262 279
SwitchRes: DALDTMCRTBCD1234X272X0X60:
 SwitchRes: (57493/68) Modeline 28.940000 1232 1296 1432 1624 272 276 279 297
SwitchRes: DALDTMCRTBCD1234X288X0X60:
 SwitchRes: (57223/68) Modeline 30.850000 1232 1296 1440 1648 288 291 295 312
SwitchRes: DALDTMCRTBCD1234X304X0X60:
 SwitchRes: (57217/68) Modeline 31.470000 1232 1320 1416 1552 304 314 317 338
SwitchRes: DALDTMCRTBCD1234X320X0X60:
 SwitchRes: (56893/68) Modeline 33.740000 1232 1328 1432 1584 320 330 333 355
SwitchRes: DALDTMCRTBCD1234X336X0X60:
 SwitchRes: (56611/68) Modeline 35.810000 1232 1336 1440 1600 336 346 350 373
SwitchRes: DALDTMCRTBCD1234X352X0X60:
 SwitchRes: (56291/68) Modeline 38.100000 1232 1344 1456 1624 352 363 367 391
SwitchRes: DALDTMCRTBCD1234X368X0X60:
 SwitchRes: (55966/68) Modeline 40.440000 1232 1352 1472 1648 368 380 384 409
SwitchRes: DALDTMCRTBCD1234X384X0X60:
 SwitchRes: (55608/68) Modeline 43.040000 1232 1360 1488 1680 384 396 400 427
SwitchRes: DALDTMCRTBCD1234X400X0X60:
 SwitchRes: (55678/68) Modeline 43.680000 1232 1256 1424 1504 400 431 433 484
SwitchRes: DALDTMCRTBCD1234X416X0X60:
 SwitchRes: (55654/68) Modeline 43.680000 1232 1256 1424 1504 416 439 441 484
SwitchRes: DALDTMCRTBCD1234X432X0X60:
 SwitchRes: (55630/68) Modeline 43.680000 1232 1256 1424 1504 432 447 449 484
SwitchRes: DALDTMCRTBCD1234X448X0X60:
 SwitchRes: (55473/68) Modeline 44.690000 1232 1264 1432 1520 448 457 459 490
SwitchRes: DALDTMCRTBCD1234X464X0X60:
 SwitchRes: (55218/68) Modeline 46.570000 1232 1264 1440 1528 464 474 476 508
SwitchRes: DALDTMCRTBCD1234X480X0X60:
 SwitchRes: (54938/68) Modeline 48.640000 1232 1264 1448 1544 480 490 492 525
SwitchRes: DALDTMCRTBCD1234X496X0X60:
 SwitchRes: (54773/68) Modeline 49.730000 1232 1264 1456 1552 496 504 507 534
SwitchRes: DALDTMCRTBCD1234X512X0X60:
 SwitchRes: (54728/68) Modeline 49.910000 1232 1264 1456 1552 512 513 516 536
SwitchRes: DALDTMCRTBCD1234X528X0X60:
 SwitchRes: (54530/68) Modeline 51.400000 1232 1264 1456 1552 528 529 533 552
SwitchRes: DALDTMCRTBCD1234X544X0X60:
 SwitchRes: (54173/68) Modeline 54.080000 1232 1288 1464 1584 544 545 549 569
SwitchRes: DALDTMCRTBCD1234X560X0X60:
 SwitchRes: (53963/68) Modeline 55.690000 1232 1288 1464 1584 560 561 565 586
SwitchRes: DALDTMCRTBCD1234X576X0X60:
 SwitchRes: (53681/68) Modeline 57.790000 1232 1288 1472 1600 576 577 581 602
SwitchRes: DALDTMCRTBCD1234X592X0X60:
 SwitchRes: (53423/68) Modeline 59.720000 1232 1288 1480 1608 592 593 597 619
SwitchRes: DALDTMCRTBCD1234X608X0X60:
 SwitchRes: (56250/68) Modeline 31.520000 1232 1320 1416 1552 608 627 634 677 interlace
SwitchRes: DALDTMCRTBCD1234X624X0X60:
 SwitchRes: (56058/68) Modeline 32.690000 1232 1328 1424 1568 624 644 651 695 interlace
SwitchRes: DALDTMCRTBCD1234X640X0X60:
 SwitchRes: (55877/68) Modeline 33.790000 1232 1328 1432 1584 640 659 666 711 interlace
SwitchRes: DALDTMCRTBCD1234X656X0X60:
 SwitchRes: (55707/68) Modeline 34.820000 1232 1336 1440 1592 656 676 683 729 interlace
SwitchRes: DALDTMCRTBCD1234X672X0X60:
 SwitchRes: (55545/68) Modeline 35.860000 1232 1336 1440 1600 672 692 699 747 interlace
SwitchRes: DALDTMCRTBCD1234X688X0X60:
 SwitchRes: (55373/68) Modeline 36.900000 1232 1336 1448 1608 688 709 717 765 interlace
SwitchRes: DALDTMCRTBCD1234X704X0X60:
 SwitchRes: (55174/68) Modeline 38.150000 1232 1344 1456 1624 704 725 733 783 interlace
SwitchRes: DALDTMCRTBCD1234X720X0X60:
 SwitchRes: (54972/68) Modeline 39.410000 1232 1344 1464 1640 720 743 751 801 interlace
SwitchRes: DALDTMCRTBCD1234X736X0X60:
 SwitchRes: (54798/68) Modeline 40.490000 1232 1352 1472 1648 736 759 767 819 interlace
SwitchRes: DALDTMCRTBCD1234X752X0X60:
 SwitchRes: (54594/68) Modeline 41.780000 1232 1352 1480 1664 752 776 784 837 interlace
SwitchRes: DALDTMCRTBCD1234X768X0X60:
 SwitchRes: (54389/68) Modeline 43.090000 1232 1360 1488 1680 768 792 800 855 interlace
SwitchRes: DALDTMCRTBCD1234X784X0X60:
 SwitchRes: (54259/68) Modeline 43.900000 1232 1360 1488 1680 784 808 817 871 interlace
SwitchRes: DALDTMCRTBCD1234X800X0X60:
 SwitchRes: (54052/68) Modeline 45.230000 1232 1360 1496 1696 800 824 833 889 interlace
SwitchRes: Found 44 custom of 83 active modelines
  • SwitchRes: 320 x 200 @ 60p-> 0.00 System Modeline
  • [1]SwitchRes: 320 x 200 @ 75p-> 0.00 System Modeline
    [2]SwitchRes: 320 x 240 @ 60p-> 0.00 System Modeline
    [3]SwitchRes: 320 x 240 @ 75p-> 0.00 System Modeline
    [4]SwitchRes: 320 x 448 @ 60p-> 0.00 Custom Modeline
    [5]SwitchRes: 400 x 300 @ 60p-> 94.00 System Modeline
    [6]SwitchRes: 400 x 300 @ 75p-> 94.00 System Modeline
    [7]SwitchRes: 496 x 384 @ 60p-> 53.65 Custom Modeline
    [8]SwitchRes: 512 x 224 @ 60p-> 0.00 Custom Modeline
    [9]SwitchRes: 512 x 239 @ 60p-> 0.00 Custom Modeline
    [10]SwitchRes: 512 x 240 @ 60p-> 0.00 Custom Modeline
    [11]SwitchRes: 512 x 384 @ 60p-> 51.13 Custom Modeline
    [12]SwitchRes: 512 x 384 @ 75p-> 51.13 System Modeline
    [13]SwitchRes: 512 x 448 @ 60p-> 40.41 Custom Modeline
    [14]SwitchRes: 640 x 224 @ 60p-> 0.00 Custom Modeline
    [15]SwitchRes: 640 x 400 @ 60p-> 32.50 System Modeline
    [16]SwitchRes: 640 x 400 @ 75p-> 32.50 System Modeline
    [17]SwitchRes: 640 x 480 @ 60p-> 20.50 Custom Modeline
    [18]SwitchRes: 640 x 480 @ 72p-> 20.50 System Modeline
    [19]SwitchRes: 640 x 480 @ 75p-> 20.50 System Modeline
    [20]SwitchRes: 640 x 480 @ 85p-> 20.50 System Modeline
    [21]SwitchRes: 720 x 480 @ 60p-> 13.56 System Modeline
    [22]SwitchRes: 800 x 600 @ 56p-> 92.00 System Modeline
    [23]SwitchRes: 800 x 600 @ 60p-> 92.00 System Modeline
    [24]SwitchRes: 800 x 600 @ 70p-> 92.00 System Modeline
    [25]SwitchRes: 800 x 600 @ 72p-> 92.00 System Modeline
    [26]SwitchRes: 800 x 600 @ 75p-> 92.00 System Modeline
    [27]SwitchRes: 800 x 600 @ 85p-> 92.00 System Modeline
    [28]SwitchRes: 1024 x 768 @ 60p-> 49.13 System Modeline
    [29]SwitchRes: 1024 x 768 @ 70p-> 49.13 System Modeline
    [30]SwitchRes: 1024 x 768 @ 72p-> 49.13 System Modeline
    [31]SwitchRes: 1024 x 768 @ 75p-> 49.13 System Modeline
    [32]SwitchRes: 1024 x 768 @ 85p-> 49.13 System Modeline
    [33]SwitchRes: 1152 x 864 @ 60p-> 64.44 System Modeline
    [34]SwitchRes: 1152 x 864 @ 70p-> 64.44 System Modeline
    [35]SwitchRes: 1152 x 864 @ 75p-> 64.44 System Modeline
    [36]SwitchRes: 1152 x 864 @ 85p-> 64.44 System Modeline
    [37]SwitchRes: 1234 x 240 @ 60p-> 0.00 Custom Modeline
    [38]SwitchRes: 1234 x 256 @ 60p-> 0.00 Custom Modeline
    [39]SwitchRes: 1234 x 272 @ 60p-> 0.00 Custom Modeline
    [40]SwitchRes: 1234 x 288 @ 60p-> 100.00 Custom Modeline
    [41]SwitchRes: 1234 x 304 @ 60p-> 87.98 Custom Modeline
    [42]SwitchRes: 1234 x 320 @ 60p-> 83.24 Custom Modeline
    [43]SwitchRes: 1234 x 336 @ 60p-> 78.96 Custom Modeline
    [44]SwitchRes: 1234 x 352 @ 60p-> 75.06 Custom Modeline
    [45]SwitchRes: 1234 x 368 @ 60p-> 71.51 Custom Modeline
    [46]SwitchRes: 1234 x 384 @ 60p-> 68.24 Custom Modeline
    [47]SwitchRes: 1234 x 400 @ 60p-> 65.24 Custom Modeline
    [48]SwitchRes: 1234 x 416 @ 60p-> 62.48 Custom Modeline
    [49]SwitchRes: 1234 x 432 @ 60p-> 59.91 Custom Modeline
    [50]SwitchRes: 1234 x 448 @ 60p-> 57.53 Custom Modeline
    [51]SwitchRes: 1234 x 464 @ 60p-> 55.31 Custom Modeline
    [52]SwitchRes: 1234 x 480 @ 60p-> 53.24 Custom Modeline
    [53]SwitchRes: 1234 x 496 @ 60p-> 51.31 Custom Modeline
    [54]SwitchRes: 1234 x 512 @ 60p-> 49.49 Custom Modeline
    [55]SwitchRes: 1234 x 528 @ 60p-> 47.79 Custom Modeline
    [56]SwitchRes: 1234 x 544 @ 60p-> 46.19 Custom Modeline
    [57]SwitchRes: 1234 x 560 @ 60p-> 44.67 Custom Modeline
    [58]SwitchRes: 1234 x 576 @ 60p-> 92.24 Custom Modeline
    [59]SwitchRes: 1234 x 592 @ 60p-> 89.54 Custom Modeline
    [60]SwitchRes: 1234 x 608 @ 60i-> 66.98 Custom Modeline
    [61]SwitchRes: 1234 x 624 @ 60i-> 64.55 Custom Modeline
    [62]SwitchRes: 1234 x 640 @ 60i-> 62.24 Custom Modeline
    [63]SwitchRes: 1234 x 656 @ 60i-> 60.05 Custom Modeline
    [64]SwitchRes: 1234 x 672 @ 60i-> 57.96 Custom Modeline
    [65]SwitchRes: 1234 x 688 @ 60i-> 55.97 Custom Modeline
    [66]SwitchRes: 1234 x 704 @ 60i-> 54.06 Custom Modeline
    [67]SwitchRes: 1234 x 720 @ 60i-> 52.24 Custom Modeline
    [68]SwitchRes: 1234 x 736 @ 60i-> 50.51 Custom Modeline
    [69]SwitchRes: 1234 x 752 @ 60i-> 48.84 Custom Modeline
    [70]SwitchRes: 1234 x 768 @ 60i-> 47.24 Custom Modeline
    [71]SwitchRes: 1234 x 784 @ 60i-> 45.71 Custom Modeline
    [72]SwitchRes: 1234 x 800 @ 60i-> 44.24 Custom Modeline
    [73]SwitchRes: 1280 x 720 @ 60p-> 68.75 System Modeline
    [74]SwitchRes: 1280 x 1024 @ 60p-> 72.13 System Modeline
    [75]SwitchRes: 1280 x 1024 @ 70p-> 72.13 System Modeline
    [76]SwitchRes: 1280 x 1024 @ 75p-> 72.13 System Modeline
    [77]SwitchRes: 1600 x 1200 @ 60p-> 88.00 System Modeline
    [78]SwitchRes: 1792 x 1344 @ 60p-> 67.00 System Modeline
    [79]SwitchRes: 1800 x 1440 @ 60p-> 79.89 System Modeline
    [80]SwitchRes: 1920 x 1080 @ 60p-> 56.33 System Modeline
    [81]SwitchRes: 1920 x 1200 @ 60p-> 71.33 System Modeline
    [82]SwitchRes: 1920 x 1440 @ 60p-> 74.33 System Modeline
    SwitchRes: Index 40/83 modeline DALDTMCRTBCD1234X288X0X60 score 100.00 matches
    SwitchRes: Got Custom modeline
1232x288@59.998911 - DALDTMCRTBCD1234X288X0X60:
        "1234x288@60" 30.850000 1232 1296 1440 1648 288 291 295 312 -HSync -VSync
SwitchRes: Setting modeline registry entry for DALDTMCRTBCD1234X288X0X60
SwitchRes: Set Registry mode DALDTMCRTBCD1234X288X0X60 with:
SwitchRes: (62184/57223/62184) Modeline 10.280000 400 424 472 544 288 291 295 312
SwitchRes: Setting Option -keepaspect
SwitchRes: Setting Option -redraw 0
SwitchRes: Setting Option -rotate
SwitchRes: Setting Option -nosoundsync
SwitchRes: Enabling VSYNC
SwitchRes: Setting Option -nothrottle
SwitchRes: Setting Option -waitvsync
SwitchRes: Setting Option -resolution 1234x288@60
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
DirectDraw: Using DirectDraw 7
Blitting thread created
winwindow_video_window_create: blit_lock = TRUE
Blitting thread started
window_proc: WM_NCACTIVATE
window_proc: blit_lock = TRUE
DirectDraw: Configuring device Radeon X1950 Series 
DirectDraw: primary surface created: 1234x288x32 (R=00FF0000 G=0000FF00 B=000000FF)
DirectDraw: New blit size = 224x288
DirectDraw: blit surface created: 224x288x32 (R=00FF0000 G=0000FF00 B=000000FF)
complete_create: blit_lock = FALSE
window_proc: WM_PAINT
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #0: Microsoft USB IntelliMouse Optical
Input: Adding Gun #0: Microsoft USB IntelliMouse Optical
Input: Adding Mouse #1: HID-compliant mouse
Input: Adding Gun #1: HID-compliant mouse
Input: Adding Mouse #2: HID-compliant mouse
Input: Adding Gun #2: HID-compliant mouse
Input: Adding Kbd #0: HID Keyboard Device
Input: Adding Kbd #1: HID Keyboard Device
Input: Adding Kbd #2: HID Keyboard Device
DirectInput: Using DirectInput 7
Input: Changing default joystick map = s8.4s8.44s8.4445
  s8888888s
  4s88888s6
  44s888s66
  444555666
  444555666
  444555666
  44s222s66
  4s22222s6
  s2222222s
Input: Changing default joystick map = s8.4s8.44s8.4445
  s8888888s
  4s88888s6
  44s888s66
  444555666
  444555666
  444555666
  44s222s66
  4s22222s6
  s2222222s
Starting Driver Device 'root'
  (missing dependencies; rescheduling)
Starting Z80 'maincpu'
Starting Video Screen 'screen'
Starting Speaker 'mono'
  (missing dependencies; rescheduling)
Starting Namco 'namco'
Starting Driver Device 'root'
  (missing dependencies; rescheduling)
Starting Speaker 'mono'
Starting Driver Device 'root'
window_proc: WM_NCACTIVATE
window_proc: blit_lock = TRUE
window_proc: WM_DESTROY
window_proc: blit_lock = TRUE
Blitting thread ended
Blitting thread destroyed
SwitchRes: Resetting modeline registry entry for DALDTMCRTBCD1234X288X0X60
SwitchRes: Set Registry mode DALDTMCRTBCD1234X288X0X60 with:
SwitchRes: (57223/57223/57223) Modeline 30.850000 1232 1296 1440 1648 288 291 295 312

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #409 on: August 19, 2011, 05:21:22 pm »
BTW

Monitor is capable of 1024x768 max. Not sure why it shows resolutions all the way up to 1920x1440.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #410 on: August 19, 2011, 05:30:00 pm »
I just tried and when I run pacman monitor goes black and i an hear game running but cant see anything

Great...  ???

Your logs look right, but that sounds too bad. Its a relief that it didn't crash. Funny thing is that I have the same setup (XP 32 + 9.3) but testing on a SVGA CRT with a Radeon X300 and it works fine here. On my cab (XP 64 6.5) Radeon 9250 its working great too... Maybe it's a problem with newer cards... don't know. I'll need to do more testing when I'm back. Thanks for testing anyway.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #411 on: August 19, 2011, 05:32:17 pm »
BTW

Monitor is capable of 1024x768 max. Not sure why it shows resolutions all the way up to 1920x1440.

Just something to try: go to screen / properties / advanced / monitor and uncheck the box "Hide modes this monitor can't show...

Maybe the 1234 figure is fooling Win.

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #412 on: August 19, 2011, 05:33:08 pm »
I have a X1900XT. THats not that new

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #413 on: August 19, 2011, 05:34:51 pm »
Just tried that. It didnt work. Same thing. Black screen

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #414 on: August 19, 2011, 05:40:58 pm »
Just tried that. It didnt work. Same thing. Black screen

Can you see these 1234 resolutions in Arcade_OSD? Do they work?

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #415 on: August 19, 2011, 06:37:28 pm »
Yes,

I tried about 10 of them and they all work

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #416 on: August 19, 2011, 07:58:15 pm »
Sniff Sniff. I cant wait another week.  :hissy:

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #417 on: August 21, 2011, 05:58:49 am »
Yes,

I tried about 10 of them and they all work

I won't be able to do any testing until I'm back but the "magic" resolutions thing might be a big FAIL after all. Which really sucks as it as it seemed too good to be true, as it allowed doing all the MAME resolutions out of a bunch of them. The fact is that it's working in my systems but there can be hundreds of reasons why it could be failing as it is such a big hack of things, so I'll probably drop that functionality.

However there's still that other option to test in VMMaker that might help with the HS issue. It's the Only32BPPModes option. If you enable that, only 32 bits per pixel modes will be enabled, so that will reduce the total list of modes quite a bit. In order to use that option, set up VMMaker as before (with options to list from XML enabled), and use the old ReslList.txt without the new 1234 modes.

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #418 on: August 31, 2011, 04:10:31 pm »
Well, if your back from Vacation and stilling willing to attempt work on the magic resolutions I'd love to test further.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #419 on: August 31, 2011, 04:48:43 pm »
Well, if your back from Vacation and stilling willing to attempt work on the magic resolutions I'd love to test further.

Thanks a lot. I'd really like to try a little more with that method before I decide to trash it, it was a lot of work and patches to Mame to achieve that but after all it's just an experiment.

If you still have the same setup as you had last week, you could try some ideas:

- Use -video d3d instead of ddraw to see if it makes any difference.
- Enter a fixed magic resolution by command line, like this (only valid for Cat 9.3):

      groovymame toki -magic_resolution 640x480@60

      NOTE: make sure to choose rom a which resolution is smaller than 640x480

- Press the print screen key while the picture is black and paste the result in the Paint app to see if its rendering the game.
- Check your monitor OSD while the picture is black to see if your getting a 15kHz signal.


bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #420 on: September 01, 2011, 08:49:25 am »
I will try frogger and dkong. how to i select d3d instead of dd?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #421 on: September 01, 2011, 09:03:50 am »
I will try frogger and dkong. how to i select d3d instead of dd?

Thanks!

Also try some horizontal game. To select d3d use a command line like this:

       groovymame toki -video d3d -magic_resolution 640x480@60

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #422 on: September 01, 2011, 09:10:46 am »
Ok

I always use the same resolution and refresh in the command lines correct?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #423 on: September 01, 2011, 10:03:00 am »
Ok

I always use the same resolution and refresh in the command lines correct?

Yep, I picked that one (640x480@60) because it's shown as avaliable and "custom" in your logs. If it works as intended, GroovyMAME should create any resolution needed using that one as (the resolution must fit inside 640x480, that's the only condition for Cat 9.3).

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #424 on: September 01, 2011, 01:53:09 pm »
When I used that command line it works great! Displays pefectly.

I tried Asteriods, simpsons, donkey kong, pacman, mr do, dig dug and frogger!

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #425 on: September 01, 2011, 02:01:45 pm »
is it the d3d thats making it work?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #426 on: September 01, 2011, 03:40:29 pm »
When I used that command line it works great! Displays pefectly.

I tried Asteriods, simpsons, donkey kong, pacman, mr do, dig dug and frogger!

Great news man!

Make sure they are run in their native refresh (press F11 -> 100%?). Try games like mk, robocop, ddragon, etc. which don't run at 60 Hz.

To know if it was because of direct3d try running games with the -video ddraw param instead.

You can permanently set that magic resolution in mame.ini by adding this option:

magic_resolution 640x480@60

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #427 on: September 01, 2011, 03:47:48 pm »
Ok

ddraw displays game but its shifted all the way up and to the left off the screen. I took a screenshot of donkey kong. D3d works flawless. DDragon, robocopy mk fine all 100% when f11 is pressed.

Why is ddraw not working?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #428 on: September 01, 2011, 04:21:57 pm »
Ok

ddraw displays game but its shifted all the way up and to the left off the screen. I took a screenshot of donkey kong. D3d works flawless. DDragon, robocopy mk fine all 100% when f11 is pressed.

Why is ddraw not working?

So with d3d you can actually see how the resolution switches to match the game's one, I mean dkong, mk, ddragon, etc. use a real progressive resolution, not a stretched picture on a 640x480 interlaced resolution, don't they?

I don't know why ddraw doesn't work, it should work the same than d3d, at least it does here, so I hope it's not an illusion and d3d is not doing a stretched display.

Actually that screen capture you made must be the same for ddraw and d3d, as that's the real framebuffer MAME uses internally, it's only that we're hacking the modeline so the only visible part on the screen is a smaller left-top rectangle with the correct size contained inside the framebuffer.

If you are positive the resolutions are genuine try launching games from HS, that after all was the motivation of all this :D


bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #429 on: September 01, 2011, 04:42:26 pm »
Yes it runs fine from Hyperspin. How do I tell if D3d is running same as Ddraw? I mean the OSD shows it running at 15Khz. I have enxlose a screenshot of it running d3d mode.

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #430 on: September 01, 2011, 04:46:53 pm »
The monitor does make a clicking sound and switch to that resolution. I also compared the OSD for both d3d and ddraw and they are both 16.5Khz at 60.5hz refresh. Except for the fact ddraw is off the screen.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #431 on: September 01, 2011, 04:50:41 pm »
Yes it runs fine from Hyperspin. How do I tell if D3d is running same as Ddraw? I mean the OSD shows it running at 15Khz. I have enxlose a screenshot of it running d3d mode.

Perfect! That means it's working, I want to believe. So with ddraw you can see the whole framebuffer with the game on the left-top corner (as the screeshot shows)? Weird. But with d3d the size is correct and the picture is just as good as when you used normal modelines is it? Anyway if d3d works just stick with it.

It would be good to see if it works with the 1234x resolutions now with -video d3d. That would be good so we can use the same method with Cat 6.5/9.3. To test that just run the same command line with -video d3d without the -magic_resolution param.


bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #432 on: September 01, 2011, 05:07:34 pm »
I just tested command line without the magic_resolution param and it worked just fine

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #433 on: September 01, 2011, 06:29:22 pm »
Still love to know why ddraw image shifts up. CAn you check you code? Do you want me to run debug?

caskad

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 61
Re: GroovyMame for arcade monitors version 0143.013
« Reply #434 on: September 01, 2011, 07:07:07 pm »
great, i will try this new magic resolution :)

One stupide question, about my new cab (mj25), i've a platinium hantarx 9100 and videocolors screen.


in vmmaker, i can use d9100? (don't know if it's screen or platinum who involved in modeline:))

but i try too this magic resolution soon !


Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #435 on: September 02, 2011, 08:23:42 am »
I just tested command line without the magic_resolution param and it worked just fine

Great, so we can keep the same method for both versions of the driver.

So this should finally be the workaround we needed for HS. As we can make all Mame resolutions using a much lower amount of them then HS will start without problems.

Still love to know why ddraw image shifts up. CAn you check you code? Do you want me to run debug?

I'm afraid I need to reproduce that issue here. What happens is that for the 9.3 version I'm checking here with a CRT SVGA monitor, and the issue doesn't happen. But I think I know what you're seeing as it's the same I saw here at the beginning before I made the patches. So I need to set up one of my cabinets with Cat 9.3 and a newer card (both have a 9250 at the moment) to try to find the problem.

Fortunately it's working for d3d, and after all that's the setting I intended to recommend when using "magic" resolutions, because with ddraw I was seeing another issue sometimes, as if it wasn't fast enough to deal with the artificially big frame buffers we're using with this patch.

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #436 on: September 02, 2011, 08:25:55 am »
great, i will try this new magic resolution :)

One stupide question, about my new cab (mj25), i've a platinium hantarx 9100 and videocolors screen.


in vmmaker, i can use d9100? (don't know if it's screen or platinum who involved in modeline:))

but i try too this magic resolution soon !


I haven't heard of that "platinum" model... However it's likely you can use the H9110 setting just fine with your Hantarex.

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #437 on: September 02, 2011, 08:28:19 am »
I need to upgrade my video card. Whats the fastest 3d card you recommend that still works best with groovymame?

Calamity

  • Moderator
  • Trade Count: (0)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 3494
Re: GroovyMame for arcade monitors version 0143.013
« Reply #438 on: September 02, 2011, 12:31:28 pm »
I need to upgrade my video card. Whats the fastest 3d card you recommend that still works best with groovymame?

The most powerful fully supportd card is the HD 4890, however for arcade use you may be interested in a lower consume or silent card (no fan), krick provided some links here:

http://forum.arcadecontrols.com/index.php?topic=113885.0

bent98

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 448
  • Hyperspin Moderator
Re: GroovyMame for arcade monitors version 0143.013
« Reply #439 on: September 03, 2011, 07:48:40 pm »
Any chance this method will work with 7 64 bit?

  
 

Sitemap 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28