GroovyMame for arcade monitors version 0.146u4_013f

[ves]

Thanks ansa89, but the patch worked, had you got any problem? it may be option -p1, right?

[ves]

Hello ufoufo512 ,

Configure wifi on startup, edit /etc/rc.conf and change ethX for wlanX.

If you have problems with video editing grub in the boot and delete splash.

If you have problems advmenu, kills processes pkill advmenu and pkill X , configures the video and try again.

I have the same hardware configuration and it works fine.

Reports log xorg.log etc..

[Ansa89]

had you got any problem?

I succesfully compiled groovymame64-0.145u8 and mame64-0.145u8, but I didn't try it yet.

it may be option -p1, right?

Code: [Select]

$ mkdir mame
$ cd mame
$ unzip /path/to/mame.zip
/* now apply patches from 0145u1 to 0145u8, then */
$ patch -p1 -i /path/to/WiimoteGroovy145u8.diff
$ make

[ves]

Hello, new versions groovymame 146.

http://code.google.com/p/groovyarcade/downloads/list

[androtaz08]

Can't wait for the windows versions of 146!

[c0dehunter]

Can anyone possibly post Calaimity's CRT Emudrivers for Windows7 x64? (is there such version available that is, or is it just for WinXP?)

Thanks.

[Calamity]

Can anyone possibly post Calaimity's CRT Emudrivers for Windows7 x64? (is there such version available that is, or is it just for WinXP?)

Hi c0dehunter,

There's no Win7 version available I'm afraid. According to users' experience, the Win7 OS has some severe problems when dealing with low-resolution CRT monitors, compared to WinXP. That's why I recommend WinXP for accurate video emulation on CRT devices. This might change in the future as new developments happen, but my own priorities are more on the direction of supporting newer AMD chipsets than newer Windows generations.

[Calamity]

GroovyMAME 0.146 for Windows 32bit/64bit:

http://code.google.com/p/groovyarcade/downloads/list

Enjoy!

[androtaz08]

Your the man! installed 146 this morning using switchers and its just not quite the same. 

[c0dehunter]

Wow! Thanks! I really appreciate it!

[Ansa89]

Talking about this switchres it's a bit outdated:

Code: [Select]

--- a/monitor.c 2011-01-20 22:50:20.000000000 +0100
+++ b/monitor.c 2011-05-14 23:03:23.873489220 +0200
@@ -44,7 +44,23 @@
 }
 
 int SetMonitorMode(char *type, MonitorMode monitor[MAX_MODES]) {
- if (!strcmp(type, "d9800") || !strcmp(type, "d9400")) {
+        if (!strcmp(type, "m2929")) {
+                monitor[0].HfreqMin = 30000;
+                monitor[0].HfreqMax = 40000;
+                monitor[0].VfreqMin = 47;
+                monitor[0].VfreqMax = 90;
+                monitor[4].HfrontPorch = 0.636;
+                monitor[4].HsyncPulse  = 3.813;
+                monitor[4].HbackPorch  = 1.906;
+                monitor[4].VfrontPorch = 0.020;
+                monitor[4].VsyncPulse  = 0.106;
+                monitor[4].VbackPorch  = 0.607;
+                monitor[4].HsyncPolarity = 1;
+                monitor[4].VsyncPolarity = 1;
+                monitor[4].ActiveLinesLimit = 576;
+                monitor[4].VirtualLinesLimit = 768;
+ return 1;
+ } else if (!strcmp(type, "d9800") || !strcmp(type, "d9400")) {
  /* CGA */
  monitor[0].HfreqMin = 15250;
  monitor[0].HfreqMax = 18000;
@@ -136,7 +152,7 @@
  monitor[5].ActiveLinesLimit = 600;
  monitor[5].VirtualLinesLimit = 768;
  return 6;
- } else if (!strcmp(type, "d9200")) {
+ } else if (!strcmp(type, "d9200") || !strcmp(type, "m3192")) {
  /* CGA */
  monitor[0].HfreqMin = 15250;
  monitor[0].HfreqMax = 16500;
@@ -148,8 +164,13 @@
  monitor[0].VfrontPorch = 0.190;
  monitor[0].VsyncPulse  = 0.191;
  monitor[0].VbackPorch  = 1.018;
- monitor[0].HsyncPolarity = 0;
- monitor[0].VsyncPolarity = 0;
+ if (!strcmp(type, "d9200")) {
+ monitor[0].HsyncPolarity = 0;
+ monitor[0].VsyncPolarity = 0;
+ } else {
+ monitor[0].HsyncPolarity = 1;
+ monitor[0].VsyncPolarity = 1;
+ }
  monitor[0].ActiveLinesLimit = 288;
  monitor[0].VirtualLinesLimit = 448;
  /* EGA */
@@ -163,8 +184,13 @@
  monitor[1].VfrontPorch = 0.451;
  monitor[1].VsyncPulse  = 0.164;
  monitor[1].VbackPorch  = 1.048;
- monitor[1].HsyncPolarity = 0;
- monitor[1].VsyncPolarity = 0;
+ if (!strcmp(type, "d9200")) {
+ monitor[1].HsyncPolarity = 0;
+ monitor[1].VsyncPolarity = 0;
+ } else {
+ monitor[1].HsyncPolarity = 1;
+ monitor[1].VsyncPolarity = 1;
+ }
  monitor[1].ActiveLinesLimit = 384;
  monitor[1].VirtualLinesLimit = 768;
  /* VGA */
@@ -178,26 +204,34 @@
  monitor[2].VfrontPorch = 0.318;
  monitor[2].VsyncPulse  = 0.064;
  monitor[2].VbackPorch  = 1.048;
- monitor[2].HsyncPolarity = 0;
- monitor[2].VsyncPolarity = 0;
+ if (!strcmp(type, "d9200")) {
+ monitor[2].HsyncPolarity = 0;
+ monitor[2].VsyncPolarity = 0;
+ } else {
+ monitor[2].HsyncPolarity = 1;
+ monitor[2].VsyncPolarity = 1;
+ }
  monitor[2].ActiveLinesLimit = 576;
  monitor[2].VirtualLinesLimit = 768;
- /* SVGA */
- monitor[3].HfreqMin = 37000;
- monitor[3].HfreqMax = 38000;
- monitor[3].VfreqMin = 40;
- monitor[3].VfreqMax = 80;
- monitor[3].HfrontPorch = 1.000;
- monitor[3].HsyncPulse  = 3.200;
- monitor[3].HbackPorch  = 2.200;
- monitor[3].VfrontPorch = 0.020;
- monitor[3].VsyncPulse  = 0.106;
- monitor[3].VbackPorch  = 0.607;
- monitor[3].HsyncPolarity = 0;
- monitor[3].VsyncPolarity = 0;
- monitor[3].ActiveLinesLimit = 600;
- monitor[3].VirtualLinesLimit = 768;
- return 4;
+ if (!strcmp(type, "d9200")) {
+ /* SVGA */
+ monitor[3].HfreqMin = 37000;
+ monitor[3].HfreqMax = 38000;
+ monitor[3].VfreqMin = 40;
+ monitor[3].VfreqMax = 80;
+ monitor[3].HfrontPorch = 1.000;
+ monitor[3].HsyncPulse  = 3.200;
+ monitor[3].HbackPorch  = 2.200;
+ monitor[3].VfrontPorch = 0.020;
+ monitor[3].VsyncPulse  = 0.106;
+ monitor[3].VbackPorch  = 0.607;
+ monitor[3].HsyncPolarity = 0;
+ monitor[3].VsyncPolarity = 0;
+ monitor[3].ActiveLinesLimit = 600;
+ monitor[3].VirtualLinesLimit = 768;
+ return 4;
+ } else
+ return 3;
  } else if (!strcmp(type, "ega")) {
  monitor[0].HfreqMin = 24960;
  monitor[0].HfreqMax = 24960;
@@ -231,10 +265,10 @@
  monitor[0].VirtualLinesLimit = 768;
  return 1;
  } else if (!strcmp(type, "multi")) {
- monitor[0].HfreqMin = 31500;
- monitor[0].HfreqMax = 60000;
- monitor[0].VfreqMin = 50;
- monitor[0].VfreqMax = 80;
+ monitor[0].HfreqMin = 54200;
+ monitor[0].HfreqMax = 83800;
+ monitor[0].VfreqMin = 49;
+ monitor[0].VfreqMax = 75;
  monitor[0].HfrontPorch = 1.000;
  monitor[0].HsyncPulse  = 3.200;
  monitor[0].HbackPorch  = 2.200;
--- a/switchres.h 2011-02-08 19:36:48.000000000 +0100
+++ b/switchres.h 2011-05-14 23:03:23.874489195 +0200
@@ -27,7 +27,7 @@
 
 #define MAX_MODES 10
 #define MAX_MODELINES 512
-#define MONITOR_TYPES "[cga ega vga multi ntsc pal h9110 d9200 d9800]"
+#define MONITOR_TYPES "[cga ega vga multi ntsc pal h9110 d9200 d9800 m3192 m2929]"
 
 #define RESULT_RES_INC      0x00000001
 #define RESULT_RES_DEC      0x00000002
--- a/version.h 2011-02-10 00:12:21.000000000 +0100
+++ b/version.h 2011-05-14 09:38:11.113242300 +0200
@@ -1,6 +1,6 @@
-#define VERSION "1.443-ced8096"
-#define NUMBER_VERSION "1.443-ced8096"
+#define VERSION "1.565M-774c0a9"
+#define NUMBER_VERSION "1.565M-774c0a9"
 #define SYSTEM_VERSION "Linux mcp 2.6.38-rc3+ #1 SMP Thu Feb 3 19:23:12 CST 2011 x86_64 Intel(R) Xeon(TM) CPU 3.40GHz GenuineIntel GNU/Linux"
 #define BUILD_DATE "Wed Feb  9 17:12:21 CST 2011"
 #define MACHINE "x86_64"
 #define OS "Linux"

[Calamity]

Hi Ansa, so you mean there was a newer version of Switchres than the one we have in the site? Did you obtain this diff out of it?
Thanks!

[Ansa89]

Yes, I got the diff from my local cloned branch of (deprecated) groovyarcade git repo.

[Justin Z]

Hey Calamity,

The link to the ATI Drivers file in the first post is still to mame.groovy.org -- is that file available elsewhere?

Thanks.

[krick]

The link to the ATI Drivers file in the first post is still to mame.groovy.org -- is that file available elsewhere?

I've got a mirror here...

http://mame.3feetunder.com/windows-ati-crt-emudriver/

[Justin Z]

Thanks, sir!  May be worth updating the original post if possible with that link.

[Calamity]

Thanks, sir!  May be worth updating the original post if possible with that link.

Done!

[Calamity]

GroovyMAME 0.146u1 32/64-bit binaries:

http://code.google.com/p/groovyarcade/downloads/list

[dgame]

Diff Changes to Makefile?


When I apply the Groovy MAME diffs from here:

http://code.google.com/p/groovyarcade/downloads/list

Only the 0142_groovymame.diff modifies the Makefile and produces the groovymame64.exe binary.

The others make no mention of the makefile and thus only generate regular mame64.exe binaries.

Tried:

0145_groovymame_013e.diff
0145u8_groovymame_013f.diff
0146_groovymame_013f.diff
0146u1_groovymame_013f.diff

None of these change the makefile or build groovymame64.exe.


How are these supposed to work?

Do they work for everyone else?

Thanks!

[Calamity]

Hi dgame,

Don't worry about the exe being created as "mame", it's actually GroovyMAME, I just rename it manually. I don't include the makefile change in my diffs any more because it's outside of the src folder and I just use this folder to create the diffs.

[dgame]

Thanks! The name and the game info screens being on by default threw me off.

I'm using the 146 diffs.

Has anyone experienced slowdowns in things like sfa2 intro?

Run sfa2 and hit F11.

Before I get to the warning screen, and during the intro, the speed with quickly drop to 94% and then jump back to 100%.

This produces a warble in the sound. I don't get speed drop this with stock MAME (v146) or CabMAME (v145.)

I was testing using the AVGA3000 and an LCD screen on the DVI port so that may be affecting the timing.

Any ideas? Settings  I should try?

The fan died on my AVGA so I didn't get a chance to hook it to the 15k monitor. Will test later.


Thanks again!

[dgame]

It works! I had some CPU / Temperature monitor programs running in the background.
Turned them off and now the game speed is steady after the initial quick slowdown.
Will start a new thread if I have further issues.

THANKS!!!

[Calamity]

Good to hear that, dgame.

[lettuce]

Calamity, have noticed with the 64bit version that the games run way too fast i have to press the F10 key to get them to run at normal speeds and enable throttle in the mame.ini file, is this how it should be??

For my setup, LCD 1080p display, Nvidia card and powerstrip is everything set correctly for this type of configuration in the attached mame.ini (txt file)??

[Calamity]

Hi lettuce,

Do you mean GroovyUME or GroovyMAME?

Anyway, by default -syncrefresh should be enabled. If enabling -syncrefresh results in games running too fast, it means DirectX is not properly reporting the vertical syncs. This can be a problem with the drivers, hardware acceleration, etc. You shouldn't need to press F10 or anything.

GroovyUME/GroovyMAME absolutely need proper vsync support, running it with plain cpu based throttle just results in the usual video artifacts we're trying to avoid.

However, recent versions of the patch require -throttle to be enabled, otherwise -syncrefresh is not considered, probably this was your case if you were using an old mame.ini file.

[lettuce]

Yeah im the Groovymame build you kindly sent me last week, i dont think that has MESS implemented??

I was using the ini file that was created for 0.144 so it is fairly old. Do i need to have both throttle and -syncrefresh enabled then or just syncrefresh?

I think i had to have disable syncrefresh and enable throttle in version 0.144 of GroovyMAME to lock the game speed as it was going too fast on games like MK (106%) so i believe you suggested me to enable throttling to lock the game at 100% and disable syncrefresh, does that wring any bells??

So now it will be ok to have both enabled?

[Calamity]

I just moved this topic here to leave the other thread for GroovyUME related topics only.

I was using the ini file that was created for 0.144 so it is fairly old. Do i need to have both throttle and -syncrefresh enabled then or just syncrefresh?

I think i had to have disable syncrefresh and enable throttle in version 0.144 of GroovyMAME to lock the game speed as it was going too fast on games like MK (106%) so i believe you suggested me to enable throttling to lock the game at 100% and disable syncrefresh, does that wring any bells??

So now it will be ok to have both enabled?

Normal setup for newer versions should be:

throttle 1
syncrefresh 1
triplebuffer 0

Now in your case I recommended disabling syncrefresh because your TV was not capable of running at 54 Hz, thus mk got accelerated. The best setup for your case would be:

throttle 1
syncrefresh 0
triplebuffer 1

[lettuce]

Ok thanks will do. Shame due to make having to select these options the scrolling on MK title screen is not smooth anymore  . Will there ever be a fix/work around for smooth scrolling with my kind of setup (LCD screen, Nvidia card)??

[Calamity]

Ok thanks will do. Shame due to make having to select these options the scrolling on MK title screen is not smooth anymore  . Will there ever be a fix/work around for smooth scrolling with my kind of setup (LCD screen, Nvidia card)??

I told you once that it's as impossible as squaring the circle

Unless your screen accepted 54 Hz, which is not the case, you're stuck to either accelerate the game to 60 Hz to get smooth scrolling, or running it at the original 54 Hz with 6 repeated frames so you have 60 in total, which results in crappy scrolling.

That's why me and kalars and some others have been trying to raise awareness in the community on the importance of finding flat screens that allow arbitrary refresh rates.

[lettuce]

Is there actually LCD display that can accept 54hz then?

[Ansa89]

Just wanna pointing out that groovymame 0.146u1 patch also applies to mame 0.146u2 OOTB.

[Calamity]

GroovyMAME 0.146u2 32/64-bit binaries:

http://code.google.com/p/groovyarcade/downloads/list

[krick]

I tried to compile my own GroovyMAME following the instructions in the first post in this thread and the patching failed.

Are the compile instructions still valid?

Are there newer files I should be using than "hi_142.txt" and "0142_hilinux.diff"?

What about the patch instructions?   This is what I'm doing...

patch -p0 -E <hi_142.txt
patch -p0 -E <0142_hilinux.diff
patch -p0 -E <0146u2_groovymame_013f.diff

...and I'm using the windows patch utility downloaded from this page on the MAMEDev site...
http://mamedev.org/updates.html

[Ansa89]

These are the latest valid instructions.

[Calamity]

What about the patch instructions?   This is what I'm doing...

Hi Krick, I've updated the first post in the thread with the compiling instructions. The hilinux diff is no longer necessary. Sorry for your time. I apply the patches using MAME Compiler 64.

[lettuce]

Notice that Gyruss is only running at 99% speed and dips sometimes i think the sound sometimes skips ever so slightly aswell, even with these settings:

throttle 1
syncrefresh 0
triplebuffer 1

Any ideas why its not 100%, i though having throttle locks it at 100% speed?

[Calamity]

Any ideas why its not 100%, i though having throttle locks it at 100% speed?

That game runs at 60.61 Hz, if you use -triplebuffer you need to enable -multithreading too, otherwise the game's speed will be locked the videocard's refresh. Only disable -multithreading for games that use -redraw, like spyhunt.

[lettuce]

Ok thanks!. Is there a large list of games that use redraw?

[Calamity]

Ok thanks!. Is there a large list of games that use redraw?

Most are the ones that originaly run at 30 Hz, not many.

[krick]

Information taken from MAME 0.146 (also see attached csv file).

Horizontal Games @ 30Hz:
archrivl
archrivl2
bigrun
blasted
cischeat
crater
dairesya
demoderb
demoderm
domino
dotron
dotrona
dotrone
f1gpstar
f1gpstr2
farwest
intlaser
ironhors
jwildb52
jwildb52a
jwildb52h
kothello
kroozr
maxrpm
nflfoot
pigskin
pigskina
powerdrv
rampage
rampage2
rbtapper
sarge
shangha2
shanghai
spyhunt2
spyhunt2a
stargrds
sutapper
tapper
tappera
timber
twotiger
twotigerc
wacko
wildplt
xenophob
zwackery

Vertical Games @ 30Hz:
armchmp2
armchmp2o
journey
kick
kickc
kickman
scudhamm
shollow
shollow2
solarfox
spyhunt
spyhuntp
trisport
tron
tron2
tron3
tron4
turbotag