CabMame

[Gray_Area]

If the refresh is matched/preserved, everything should run fine. I'm wondering if maybe you guys aren't going at it the hard way.

It depends on the monitor capabilities (and the amount of custom resolutions your video card supports) which most can't match all the games so Cabmame patches make up for that using sound sync/redraw/speed hacks.

I was under the impression that the chain of things was MAME>video hardware>monitor, with your efforts largely based in forcing/seducing the video hardware into doing MAME's bidding.


Regarding Tron: so you're saying a 15khz/60hz monitor can display Tron with the re-draw feature?

[bitbytebit]

If the refresh is matched/preserved, everything should run fine. I'm wondering if maybe you guys aren't going at it the hard way.

It depends on the monitor capabilities (and the amount of custom resolutions your video card supports) which most can't match all the games so Cabmame patches make up for that using sound sync/redraw/speed hacks.

I was under the impression that the chain of things was MAME>video hardware>monitor, with your efforts largely based in forcing/seducing the video hardware into doing MAME's bidding.


Regarding Tron: so you're saying a 15khz/60hz monitor can display Tron with the re-draw feature?

Yeah it can do that without throttle by doubling the frame output I guess so it becomes 60hz instead of 30, of course only works in cases where you are able to double the mame refresh rate to match the monitor refresh rate. 

It's basically setting up an available modeline for mame to target and use which best matches the game and works with the capabilities of the monitor, and tweaking mame command line settings to make that combo of mame/resolution/monitor to run as original as possible.

Here's an example of what switchres does to run Tron on a CGA vs. d9800 with nothrottle and perfect vsync/refresh rate and no tearing w/original resolution(on d9800 only) for horizontal monitor playing it instead of vertical.  So in the CGA case of course there's a bit of virtualization to get the redraw and 60Hz capable modeline and run it at the original refresh, on the d9800 it can match the original resolution and run on the monitor refresh rate with redraw.

CGA:

Code: [Select]

Mame version 0.141 with [cleanstretch][froggerfix][redraw][changeres][] hacks enabled
[] "tron" vertical 512x480@30.000 (1.067) --> 856x512@30.000 (1.666)

MonitorLimits 15250.00-15700.00,49.50-65.00,2.000,4.700,8.000,0.064,0.192,1.024,0,0,288.0,448
Setup monitor limits min=184x108 max=0x608
Increased vertical frequency to 60.000
Using interlace
Starting with Horizontal freq of 16.638 and Vertical refresh of 60.00
Horizontal frequency too high 16.638 vfreq 60.000
Virtualized to 856x480@60.00 15.6000Khz
Original Vref 30.000000 != 60.000000
# 15.250Khz -> 15.700Khz: ( | Interlace | Virtualize | )
# tron [9] 856x480@60.00 15.6300Khz
     "856x480x60.00" 17.255520 856 888 968 1104 480 482 488 521 -HSync -VSync interlace

Opening  modes file for mode 856x480x32@60.00
Running Emulator: mame tron -resolution 856x480x32@60.00 -resolution0 856x480x32@60.00 -video opengl -nocleanstretch -unevenstretch -nochangeres -keepaspect -redraw auto -nothrottle -nomt -waitvsync


D9800:

Code: [Select]

Mame version 0.141 with [cleanstretch][froggerfix][redraw][changeres][] hacks enabled
[d9800] "tron" vertical 512x480@30.000 (1.067) --> 856x512@30.000 (1.666)

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
Setup monitor limits min=184x84 max=0x864
Increased vertical frequency to 60.000
Using interlace
Starting with Horizontal freq of 16.767 and Vertical refresh of 60.00
Original Vref 30.000000 != 60.000000
# 15.250Khz -> 18.000Khz: ( | Interlace | )
# tron [3] 856x512@60.00 16.7700Khz
     "856x512x60.00" 18.648240 856 896 984 1112 512 518 524 559 -HSync -VSync interlace

MonitorLimits 18001.00-18900.00,40.00-80.00,2.187,4.688,6.719,0.140,0.191,0.950,0,0,288.0,448
Setup monitor limits min=184x104 max=0x912
Increased vertical frequency to 60.000
Using interlace
Starting with Horizontal freq of 16.639 and Vertical refresh of 60.00
Increased horizontal frequency from 16.639 to 18.001
Original Vref 30.000000 != 60.000000
Using 42 lines padding
# 18.001Khz -> 18.900Khz: ( | Hfreq Change | Interlace | Vpad +42 lines | )
# tron [10] 856x512@60.00 18.0300Khz
     "856x512x60.00" 20.482080 856 904 1000 1136 512 538 545 601 -HSync -VSync interlace

MonitorLimits 20001.00-29000.00,40.00-80.00,2.910,3.000,4.440,0.451,0.164,1.048,0,0,480.0,768
Setup monitor limits min=184x104 max=0x1360
Increased vertical frequency to 60.000
Virtualized to 1152x864@60.00 28.8000Khz
Starting with Horizontal freq of 28.793 and Vertical refresh of 60.00
Original Vref 30.000000 != 60.000000
# 20.001Khz -> 29.000Khz: ( | Interlace | Virtualize | )
# tron [9] 1152x864@60.00 28.8300Khz
     "1152x864x60.00" 46.589280 1152 1280 1416 1616 864 890 899 961 -HSync -VSync interlace
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
Setup monitor limits min=184x160 max=0x1520
Increased vertical frequency to 60.000
Starting with Horizontal freq of 33.603 and Vertical refresh of 60.00
Horizontal frequency too high 33.603 vfreq 60.000
Lowered horizontal frequency to  32000.000 from 33.603
Vertical frequency changed to 57.348 from 60.000
Original Vref 30.000000 != 57.347670
# 29.001Khz -> 32.000Khz: ( | Hfreq Change | Vref Change | )
# tron [11] 856x512@57.35 32.0000Khz
     "856x512x57.35" 34.048000 856 872 1000 1064 512 522 524 558 -HSync -VSync

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
Setup monitor limits min=184x188 max=0x1664
Increased vertical frequency to 60.000
Starting with Horizontal freq of 32.133 and Vertical refresh of 60.00
Original Vref 30.000000 != 60.000000
# 32.001Khz -> 34.000Khz: ( Perfect Resolution )
# tron [0] 856x512@60.00 32.1600Khz
     "856x512x60.00" 34.218240 856 872 1000 1064 512 513 516 536 -HSync -VSync

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
Setup monitor limits min=184x200 max=0x1856
Increased vertical frequency to 60.000
Starting with Horizontal freq of 32.133 and Vertical refresh of 60.00
Increased horizontal frequency from 32.133 to 34.001
Original Vref 30.000000 != 60.000000
Using 30 lines padding
# 34.001Khz -> 38.000Khz: ( | Hfreq Change | Vpad +30 lines | )
# tron [5] 856x512@60.00 34.0200Khz
     "856x512x60.00" 36.741600 856 888 1000 1080 512 528 532 567 -HSync -VSync

Opening  modes file for mode 856x512x32@60.00
Running Emulator: mame tron -resolution 856x512x32@60.00 -resolution0 856x512x32@60.00 -video opengl -cleanstretch -redraw auto -nothrottle -nomt -waitvsync


[bitbytebit]

I built a 32bit 141 version of mame with the cabmame patches and hiscore/nonag ones, also I am turning off the changeres option by default now since that seems to contradict anything that needs stretching.  http://mario.groovy.org/GroovyArcade/MameWindows/

If anyone wants the patches, changed slightly but not too much, they are here...
http://groovyarcade.git.sourceforge.net/git/gitweb.cgi?p=groovyarcade/groovyarcade;a=blob_plain;f=overlays/games-emulation/mame/files/groovyarcade-0141.patch;hb=HEAD

(fix for using hi/ directory to store hiscore.dat) http://groovyarcade.git.sourceforge.net/git/gitweb.cgi?p=groovyarcade/groovyarcade;a=blob_plain;f=overlays/games-emulation/mame/files/hilocfix-0141.patch;hb=HEAD

(fix for SDL/Linux compile) http://groovyarcade.git.sourceforge.net/git/gitweb.cgi?p=groovyarcade/groovyarcade;a=blob_plain;f=overlays/games-emulation/mame/files/sdlfix-0141.patch;hb=HEAD

[Calamity]

I'm testing your new Mame v0.141 binary with CabMame hacks, it seems you've also added the soundsync functionallity (it's set by default, no command line option), it's working great for me, it also creates the proper default options when doing mame -createconfig, very convenient. I'm going to use this one as my default Mame binary for now on.

[southpaw13]

Did you put the soundsync hack in it?

thanks.....

[bitbytebit]

Did you put the soundsync hack in it?

thanks.....

Yep, every cabmame patch is in there now, for both Mess and Mame 0141. 

[southpaw13]

Awesome....

thanks again....

[EvilDindon]

Thanks a lot man, that's what i needed ! The two most important features of cabmame or the soundsync and the frogger/galaxian driver hack.

Question : I have tested an earlier cabmame veriosn (139), on my vertical monitor cab, but i couldn't run the double monitor nintendo games such as punch out! or arm wrestling.

Since I use the hardware stretch and 512X480 resolution for those games (to display the two monitors with an interlaced res), maybe I should turn off the changeres option ?

Cheers,

Mike from France

[bitbytebit]

Thanks a lot man, that's what i needed ! The two most important features of cabmame or the soundsync and the frogger/galaxian driver hack.

Question : I have tested an earlier cabmame veriosn (139), on my vertical monitor cab, but i couldn't run the double monitor nintendo games such as punch out! or arm wrestling.

Since I use the hardware stretch and 512X480 resolution for those games (to display the two monitors with an interlaced res), maybe I should turn off the changeres option ?

Cheers,

Mike from France

Yep, I'm guessing that most likely is the issue, changeres seems to force a 1 to 1 scaling ratio from what I can tell.

[EvilDindon]

Hey !

Just tested your build on my cab ; everything is OK even the double monitor nintendo games), BUT there's an issue (nothing is perfect at the first try :5  ) ;

Actually, the frogger hack works great on all the games (galaxian, scramble, moon cresta and clones) EXCEPT FROGGER !!!!  


Frogger has still a resolution issue, it seems that the frogger hack that is supposed to set a 256X224 res for this game and all the galxian driver based games instead of the 768 x 224 false and official mame res, doesn't work.  

Do you experience the same ?

I tried to workaround by setting in the frogger.ini 640X480 and hwstretch 1, but it' doesn't work neither, the screen isn't full.

[bitbytebit]

Hey !

Just tested your build on my cab ; everything is OK even the double monitor nintendo games), BUT there's an issue (nothing is perfect at the first try :5  ) ;

Actually, the frogger hack works great on all the games (galaxian, scramble, moon cresta and clones) EXCEPT FROGGER !!!!  


Frogger has still a resolution issue, it seems that the frogger hack that is supposed to set a 256X224 res for this game and all the galxian driver based games instead of the 768 x 224 false and official mame res, doesn't work.  

Do you experience the same ?

I tried to workaround by setting in the frogger.ini 640X480 and hwstretch 1, but it' doesn't work neither, the screen isn't full.

It works here, but I'm not sure what is going on since frogger really should look just like galaxian so very strange.  So only frogger has the issue, what exactly does it look like?  What does the output of mame with -verbose show?

[EvilDindon]

Yeah, in theory, frogger should be OK like galaxian, but it's not !

Well the image is stretched vertically and covers only a small part of the screen orizontally, just like if mame runs it on a 768X576 interlaced resolution. I'm pretty sure that this game is considered by mame to have this weird official resolution (768x224)

How can i use the verbose option ?

[bitbytebit]

Yeah, in theory, frogger should be OK like galaxian, but it's not !

Well the image is stretched vertically and covers only a small part of the screen orizontally, just like if mame runs it on a 768X576 interlaced resolution. I'm pretty sure that this game is considered by mame to have this weird official resolution (768x224)

How can i use the verbose option ?

Just add -verbose to the command line of mame.  I did confirm that an oddity in 0141 is similar to that with gorf, but frogger works here.  I compared gorf in 0140u2 to 0141 and it did that, so sounds similar.  Do you have a version of 139 cabmame to compare it to?  Try it and see if it's the same results, also output of the -verbose option of frogger and galaxian may be helpful.

[EvilDindon]

Ok thanks a lot dude for your help.

I remember that frogger worked well with cabmame 139.


So I launch frogger via the command prompt, with -verbose ? And after ? it will generate a log file, that's it ?

[bitbytebit]

Ok thanks a lot dude for your help.

I remember that frogger worked well with cabmame 139.


So I launch frogger via the command prompt, with -verbose ? And after ? it will generate a log file, that's it ?

It will output text to the console, but you can add > logfile.txt to the end of the mame command after the -verbose argument, and it'll put it into a file for you that you should be able to zip up and post here.

[EvilDindon]

Ok will see that, thanks, i'll see that.

[EvilDindon]

OK here we are. It seems that mame picks a weird resolution lol :


Parsing mame.ini
Parsing mame.ini
Video: Monitor 00010001 = "\\.\DISPLAY1" (primary)
DirectDraw: Using DirectDraw 7
DirectDraw: Configuring device RADEON 7000 / RADEON VE
Target refresh = 60.606061
DirectDraw: Selecting video mode...
   240x 240@ 60Hz -> 622.642556
   256x 240@ 60Hz -> 622.642574
   256x 256@ 60Hz -> 622.642593
   256x 264@ 60Hz -> 622.642603
   288x 240@ 60Hz -> 622.642612
   296x 240@ 60Hz -> 622.642622
   304x 240@ 60Hz -> 622.642632
   321x 240@ 60Hz -> 622.642655
   321x 256@ 60Hz -> 622.642676
   336x 240@ 60Hz -> 622.642675
   352x 256@ 60Hz -> 622.642720
   352x 264@ 60Hz -> 622.642732
   352x 288@ 60Hz -> 622.642770
   368x 240@ 60Hz -> 622.642720
   384x 288@ 60Hz -> 622.642823
   392x 240@ 60Hz -> 622.642757
   401x 256@ 60Hz -> 622.642797
   448x 240@ 60Hz -> 622.642852
   512x 240@ 60Hz -> 622.642979
   512x 288@ 60Hz -> 622.643091
   512x 448@ 60Hz -> 622.643631
   512x 512@ 60Hz -> 622.643561
   632x 264@ 60Hz -> 622.643376
   640x 240@ 60Hz -> 622.643322
   640x 288@ 60Hz -> 622.643496
   640x 480@ 60Hz -> 622.644571
   640x 480@ 72Hz -> 80.687662
   640x 480@ 75Hz -> 64.963696
   640x 480@ 85Hz -> 39.382541
   640x 480@ 90Hz -> 32.904362
   640x 480@100Hz -> 24.759257
   640x 480@120Hz -> 16.561020
   640x 480@160Hz -> 9.963828
   640x 480@200Hz -> 7.125882
   648x 288@ 60Hz -> 622.643528
   720x 480@ 60Hz -> 622.645569
   800x 600@ 47Hz -> 68.468230
   800x 600@ 56Hz -> 178.381870
   800x 600@ 60Hz -> 622.645000
   800x 600@ 70Hz -> 96.213410
   800x 600@ 72Hz -> 80.688091
   800x 600@ 75Hz -> 64.964125
   800x 600@ 85Hz -> 39.382970
   800x 600@ 90Hz -> 32.904791
   800x 600@100Hz -> 24.759686
   800x 600@120Hz -> 16.561449
   800x 600@160Hz -> 9.964257
   800x 600@200Hz -> 7.126311
  1024x 768@ 43Hz -> 56.493182
  1024x 768@ 60Hz -> 625.388757
  1024x 768@ 70Hz -> 98.957166
  1024x 768@ 72Hz -> 83.431848
  1024x 768@ 75Hz -> 67.707882
  1024x 768@ 85Hz -> 42.126727
  1024x 768@ 90Hz -> 35.648547
  1024x 768@100Hz -> 27.503442
  1024x 768@120Hz -> 19.305205
  1024x 768@150Hz -> 13.809941
  1024x 768@160Hz -> 12.708013
  1024x 768@200Hz -> 9.870067
DirectDraw: Mode selected = 1024x 768@ 60Hz
DirectDraw: primary surface created: 1024x768x32 (R=00FF0000 G=0000FF00 B=000000FF)
DirectDraw: New blit size = 957x472
DirectDraw: blit surface created: 957x472x32 (R=00FF0000 G=0000FF00 B=000000FF)
DirectSound: Primary buffer: 48000 Hz, 16 bits, 2 channels
RawInput: APIs detected
Input: Adding Mouse #1: Souris HID
Input: Adding Gun #1: Souris HID
Input: Adding Mouse #2: Souris HID
Input: Adding Gun #2: Souris HID
Input: Adding Kbd #1: Clavier standard 101/102 touches ou clavier Microsoft Natural Keyboard PS/2
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
Input: Changing default joystick map = s8.4s8.44s8.4445
  s8888888s
  4s88888s6
  44s888s66
  444555666
  444555666
  444555666
  44s222s66
  4s22222s6
  s2222222s
Resolution change from 2752944x2752752 to 957x472
Starting Driver Device 'root'
  (missing dependencies; rescheduling)
Starting Z80 'maincpu'
Starting Video Screen 'screen'
Starting Timer 'stars'
Starting Speaker 'mono'
  (missing dependencies; rescheduling)
Starting Intel PPI8255 'ppi8255_0'
Starting Intel PPI8255 'ppi8255_1'
Starting Z80 'audiocpu'
Starting AY-3-8910A '8910.0'
Starting Discrete 'konami'
Starting Driver Device 'root'
  (missing dependencies; rescheduling)
Starting Speaker 'mono'
Starting Driver Device 'root'
Sound: buffer overflows=1 underflows=0

[EvilDindon]

Just tested gorf and it has the same issue than frogger.

Edit : moon cresta too

[bitbytebit]

Just tested gorf and it has the same issue than frogger.

Edit : moon cresta too

Double check the non-patched mame 0141, I suspect this might be more to do with 0141 perhaps, not sure why it's choosing such a wrong resolution.

[EvilDindon]

Hey man I forgot to mention that I'm running mame using an arcadeVGA, not soft15.

That maybe explain the difference in ou results for frogger ?

[bitbytebit]

Hey man I forgot to mention that I'm running mame using an arcadeVGA, not soft15.

That maybe explain the difference in ou results for frogger ?

Well actually I'm running it in Linux where it can create any modeline on the fly at runtime, and have a d9800.  I think with this, the Soft15KHz and arcadeVGA should be about the same.  Although again it could be something in the drivers or the arcade vga card, but I don't think it is.  If gorf does the exact same thing, it seems like it's possible my thought about mame 0141 having a bug with these certain games may be correct.  It may be in Linux I'm slightly overcoming the frogger issue, but in gorf it's different and for it even without changing resolutions just running it stretched it's all way too skinny now and an exact patched version of mame 0140u2 doesn't do that for me.

[EvilDindon]

So if I understand well, you encounter a similar problem as me with gorf, but not with frogger ?

Damn, frogger was one of the most played game on my cab 

[bitbytebit]

So if I understand well, you encounter a similar problem as me with gorf, but not with frogger ?

Damn, frogger was one of the most played game on my cab 

Yeah, I'm blaming mame for now, will see if it changes in the next release patch at all.  Seems to be centered around the version, from what I can tell 0140u2 was fine with both games.  Since they are both different drivers, from what I can tell offhand at least, looks like that might be able to explain why with actual resolution usage I'm doing frogger works correctly while gorf breaks still.  I really can't explain though why both break similar, from what I can tell they should be totally separate, but seeming the similar type of break in both and the difference of the frogger patch vs. gorf patch seems to say it's outside anything we are doing in the cabmame hacks at all.

[EvilDindon]

Hey,

I tried to compile mame on my own with the 141 sources, the hi score diff and the cabmame diffs

When I tried to apply the frogger patch, it returned an error.

Have you noticed it yourself ?

[bitbytebit]

Hey,

I tried to compile mame on my own with the 141 sources, the hi score diff and the cabmame diffs

When I tried to apply the frogger patch, it returned an error.

Have you noticed it yourself ?

Try these patches, they are against 141u1, this should apply clean.  Also I've got a 32 bit build up of 0141u1 too.

http://groovyarcade.git.sourceforge.net/git/gitweb.cgi?p=groovyarcade/groovyarcade;a=blob_plain;f=overlays/games-emulation/mame/files/hiscore_0141u1.diff;hb=HEAD
http://groovyarcade.git.sourceforge.net/git/gitweb.cgi?p=groovyarcade/groovyarcade;a=blob_plain;f=overlays/games-emulation/mame/files/groovyarcade_0141u1.diff;hb=HEAD

Basically the groovyarcade_0141u1.diff file is the complete cabmame patches and a few other tweaks.  Note too that the hiscore.dat file must be in the \hi\ directory, that way it can stay in one place and isn't ambiguous where it should be.

[EvilDindon]

Wow man, thanks this is awesome, will try it out now.

Hope that frogger gorf and moon cresta will be ok in 141u1

But, tell me, the 141u1 cabmame patches aren't out, have you modified them to work on 141u1 ?

[bitbytebit]

Wow man, thanks this is awesome, will try it out now.

Hope that frogger gorf and moon cresta will be ok in 141u1

But, tell me, the 141u1 patches aren't out, have you modified them to work on 141u1 ?

On my system Gorf wasn't right until I forced it into CGA mode, using a d9800 and seems it doesn't like the EGA resolution around 23khz and when pushing it back into normal 15khz mode it worked.  I'm still not sure what is going on there, I'm wondering if your seeing the same deal with frogger, but yet there still seems to be something odd going on and I need to test but seems like it'd be in mame itself and not the patches.  Since I could run with my 0140u2 with the same patches, and gorf is fine there.  I'll try a clean build of 0141u1 here and make sure, have you tried a clean build of 0141 and seen any difference in gorf and/or frogger there?

The original 0141 hiscore patch works fine with a little bit of fixing for the config options to apply. 

[EvilDindon]

Hey,

I got an error when applying the hiscore patch.

Anyway i think i'll download your win32 build

Thanks again man.

[EvilDindon]

Just tried your latest build on my cab, and I have the same issues for frogger/gorf/moon cresta.

Can you link me to your 140u2 build to test those games ?

I'd prefer 141 (or above)  for the new shoot'em ups, but I even prefer classics frogger and moon cresta over those shmups, so if 140u2 works fine for them, i'll keep it

[bitbytebit]

Just tried your latest build on my cab, and I have the same issues for frogger/gorf/moon cresta.

Can you link me to your 140u2 build to test those games ?

I'd prefer 141 (or above)  for the new shoot'em ups, but I even prefer classics frogger and moon cresta over those shmups, so if 140u2 works fine for them, i'll keep it

Try it with -nocleanstretch, see if that fixes it at all.  I'm suspecting it might be centered around that.  Also if that doesn't work, then instead try adding -changeres and see if that helps.

[EvilDindon]

Thanks for those tips, will try it

[EvilDindon]

Well I tried :

1/
cleanstretch 0
changeres0

2/
cleanstretch 1
changeres 1

3/
cleanstretch 0
changeres 1

4/
cleanstretch 1
changeres 0

And the result is that I get a very (very) small picture of the game (maybe 4x6 cm on the screen), but with the good proportions.   

[bitbytebit]

Well I tried :

1/
cleanstretch 0
changeres0

2/
cleanstretch 1
changeres 1

3/
cleanstretch 0
changeres 1

4/
cleanstretch 1
changeres 0

And the result is that I get a very (very) small picture of the game (maybe 4x6 cm on the screen), but with the good proportions.   

Try to add -hwstretch to those, that should allow it to expand to full screen.

[EvilDindon]

I enabled hwstretch with no success ; when cleanstretch and changeres are disabled, the game picture fits appr. the quarter of the screen : when one of those parameters are enabled, the game screen is ridiculously small.

Also, the game runs very slow with the hwstretch enabled.

I really think it's a mame problem. Obviously, the cabmame frogger hack doesn't work well on this version.

In theory, with an arcadevga, you never need to enable hwstretch, cause what you want is to run the games at their native res.

Could you post an earlier build you made (140u2 or u3) to see if it's a mame.141 and above problem ?

[bitbytebit]

I enabled hwstretch with no success ; when cleanstretch and changeres are disabled, the game picture fits appr. the quarter of the screen : when one of those parameters are enabled, the game screen is ridiculously small.

Also, the game runs very slow with the hwstretch enabled.

I really think it's a mame problem. Obviously, the cabmame frogger hack doesn't work well on this version.

In theory, with an arcadevga, you never need to enable hwstretch, cause what you want is to run the games at their native res.

Could you post an earlier build you made (140u2 or u3) to see if it's a mame.141 and above problem ?

I've uploaded 140u3 and 140u2 should be uploaded in a minute, definitely will be interesting to see.  I know that now gorf looks good for me with -nocleanstretch added (and always use -nochangeres and it's the default to be off). 

yeah I figured that, but odd that it's small, have you tried forcing the resolution to the right one with -resolution HxW@R args to mame?  Seems that it's doing it right there but not forcing mame to switch resolutions.  I really can't explain the gorf thing, somehow the cleanstretch patch now does something wrong for it although ok for me on all other games.  I see this on an arcade monitor and a normal LCD monitor too, same behavior with gorf.  Actually frogger works fine for me on the arcade monitor but when I use it on my LCD monitor it is really skinny vertical and wide horizontal and picks the 720x240 resolution or something ridiculous like that.  It's almost as if they have the logic for resolution choosing slightly altered now and it's making bad decisions, but that still doesn't explain what gorf is doing for me but does possibly explain the frogger issue.

[EvilDindon]

Hey I tried downloading several times 140u2 and u3 with no success : the download starts and stops 1 second after.

Anyways, I already tried forcing the resolution in the ini of the game, but it doesn't solve the problem.

[bitbytebit]

Hey I tried downloading several times 140u2 and u3 with no success : the download starts and stops 1 second after.

Anyways, I already tried forcing the resolution in the ini of the game, but it doesn't solve the problem.

Ah I'll reupload those, somehow the file transfer bricked the files, weird.  I should have new ones up shortly, just removed the old ones so when you seen them up again there should be working versions hopefully to test.  

Update:  The sourceforge site is broken for my uploads, I opened a trouble ticket with them so hopefully they fix it soon :/.  I should have figured the free service would have some issues like this, right now all my uploads there within the last day are doing the same thing.

[EvilDindon]

Man, just tried out a .139 build of cabmame and it does the same.

Although I swear an earlier cabmame version was working good for frogger and others.

Mayber it was 0.138. Will try it.

[bitbytebit]

Man, just tried out a .139 build of cabmame and it does the same.

Although I swear an earlier cabmame version was working good for frogger and others.

Mayber it was 0.138. Will try it.

Ah that figures, then there's something else at play but I'm not sure.  At least know it's nothing in my port of the patches, but also now sure why it's treating the games really oddly different for you, and somewhat for me too, yet I don't have the full ability to compare my Linux setup to my Windows one which now in Linux I've not seen the gorf issue since avoiding cleanstretch.

I also now have changed the location of these builds to a new site, http://mario.groovy.org/GroovyArcade/MameWindows/ so the old one no longer is there.  This one should be much more reliable in the future.

[EvilDindon]

Some good news. I found a solution to make all these games working well even with your 141u1 build. Even with gorf and frogger, but there's still something annoying with frogger.

Actually I had to play with three kind of parameters :

1/ In mame.ini, I set those parameters :

throttle 1
refreshspeed 0
redraw 0
cleanstretch 0
changeres 0
froggerhack 1
syncrefresh 0
waitvsync 0
video ddraw
hwstretch 0
triplebuffer 1
switchres 1

2/ In each game.ini :

In frogger.ini, bombjack.in, mooncrst.ini, gorf.ini, I specified the appropriate resolution :

resolution 256X240
except for gorf : resolution 336X240 (it feet perfectly the full screen)

3/ In the tab menu (OSD in game) :

For bombjack, frogger, gorf, karate champ, gun smoke and moon cresta, I had to go in the video options, and set "Standard (4:3)"or even "Debug". Then the games displayed correctly.

But still, for frogger, I have to do this each time I launch the game : if i don't fo this, the game displays like if the froggerhack is not working (only the half of the screen is visible and is stretched in the full screen). I verified in the frogger.cfg file, and the parameter is saved, but it still doesn't apply automatically, i have to do it manually every two launches of the game.

Dunno if there's a way to workaround this annoying frogger bug. I'll maybe use an interlaced 640X480 res, with hwstretch on and froggerhack off, even if i would have prefered to play in the native res.


But all in all, I'm quite happy with all these improvements  

Edit : actually, a lot of games needs this to work : moon cresta, karate champ, gun smoke, frogger, gorf, etc.    

I think I'll go back to mame 0.110 which worked like a charm on my cab.