GroovyMame for arcade monitors version 0.146u4_013f

[Calamity]

groovymame32_0143u8.013d.rar now uploading...

Sorry guys for the delay, even u9 has been released so this one is a bit outdated already
Anyway I'll definitely wait for v0.144 to see if it's more stable on the hlsl part.

[lettuce]

Calamity, are you still going to be implementing Wiimote support in GroovyMAME??...i would love to play some lightgun games in mame but cant seem to get it to work with MAME

[Calamity]

Calamity, are you still going to be implementing Wiimote support in GroovyMAME??...i would love to play some lightgun games in mame but cant seem to get it to work with MAME

It was VeS the one who implemented it for the Linux side actually, I'll write to him to see if it's easy to add.

[lettuce]

Cool, thanks

[Calamity]

Version 0.144 is uploaded:

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

groovymame32_0144.013d.rar
groovymame64_0144.013d.rar
0144_groovymame_013d.diff

Compiling notes:
---------------

Apply patches in this order:

1) hi_144.txt (http://mamestuff.lowtrucks.net/MKChamp/)
2) 0144_groovymame_013d.diff (http://mario.groovy.org/GroovyMame/WindowsATIDrivers/)

I've merged the hi_linux and groovymame patches into one single diff so the process of applying patches is somewhat simpler.

[ves]

Hello, if you include the hiscore patch in the patches of groovy is a problem, normal hiscore is not supported linux,patches can not be applied, anyway I tried to apply your patch groovyarcade to suck from linux and there are problems, the patch is only for windows?

Since gentoo patches can be applied without problems, so the error is in ubuntu patch, anyone know why ubuntu does not work and if done with gentoo? that the difference between gentoo and ubuntu patch?

I compiled the same version that uses gentoo patch 2.5.9 and can now apply patches without problems, someone knows why the version of ubuntu patch 2.6.1 does not work?

Here you have the wiimote144mame patch is only for linux.

http://www.megaupload.com/?d=OI1TZEXF
http://www.retrovicio.org/foro/showthread.php?16228-Pistola-Wiimote-Linux

For windows you have to use BlueSoleil and Wiinremote, and also patch mame in:

/src/osd/windows/INPUT.C

#define FORCE_DIRECTIPUT 0
change
#define FORCE_DIRECTIPUT 1

http://www.retrovicio.org/foro/showthread.php?12209-Pistola-MAME-con-WiiMote!!

Thank you.

[Calamity]

Hi Ves,

Thanks a lot for the patches, I'll check if it's easy to port it to the Windows side.

Hello, if you include the hiscore patch in the patches of groovy is a problem, normal hiscore is not supported linux,patches can not be applied, anyway I tried to apply your patch groovyarcade to suck from linux and there are problems, the patch is only for windows?

Try by applying the hi_144.txt patch over MAME source code using MAME Compiler for Windows, it works for me that way, then build your Linux binary as usual.

Thanks again!

[lettuce]

Here you have the wiimote144mame patch is only for linux.

http://www.megaupload.com/?d=OI1TZEXF
http://www.retrovicio.org/foro/showthread.php?16228-Pistola-Wiimote-Linux

For windows you have to use BlueSoleil and Wiinremote, and also patch mame in:

/src/osd/windows/INPUT.C

#define FORCE_DIRECTIPUT 0
change
#define FORCE_DIRECTIPUT 1

http://www.retrovicio.org/foro/showthread.php?12209-Pistola-MAME-con-WiiMote!!

Thank you.

So you do have to use BlueSoleil and Wiinremote with MAME theres no other way around it??. I can just use a prog like Pinnacle Game Profiler which has Wii support. I have tried setting up my Wiimote to act as a lightgun in Mame but have never got it to work . Calamity if you could get this working with the Windows version of Groovymame it would be great!! 

[lettuce]

Calamity, i know im being a pain but can you please compile a 64-Bit version of GroovyMame 0.143u9 please?

[ves]

GroovyMame x32 Linux and Wiimote support gentoo.

http://www.megaupload.com/?d=4Y5TPGUX

Update GroovyArcade,replace groovymame.

/usr/games/bin/groovymame


Thanks.

[lettuce]

So will there be a windows release of GroovyMAME with Wiimote support that doesnt require other software to get it to work?

[lettuce]

Yeah this would defo be a really nice addition to GroovyMame Calamity, having Wiimote support build into the windows version! Would this be possible?

[Calamity]

Yeah this would defo be a really nice addition to GroovyMame Calamity, having Wiimote support build into the windows version! Would this be possible?

I made some research the other day and, as Ves pointed, under Windows the Wiimote support is all performed through third party software Bluesoleil and Wiinremote. So the only mod that MAME needs is the FORCE_DIRECTINPUT thing. That's definitely something I won't do for GroovyMAME's binary as I've read here and there that it adds some degree of input lag compared to usual raw input. However, I may add it as an option that the user can enable/disable through mame.ini, probably in next release.

[lettuce]

Ah ok, thats a shame that a 3rd party software is needed, i cant get Bluesoleil and Wiinremote to work correctly together at all on my system, must of spent a good few hours trying to get it to work. Either Bluesoleil doesnt detect and pair with my wiimote, or if it does pair up ok then Wiinremote wont detect my wiimote and on the odd occasion i do get them both to connect to my wiimote anything i press on the wiimote isnt detected . Its a right royal pain in the arse there has to be an easier way

[Calamity]

You probably have seen this thread: http://forum.arcadecontrols.com/index.php?topic=89378.0

They recommend GlovePie instead of Wiinremote. However they say not every bluetooth device is compatible with Wiimote, so that could be your case.

[caskad]

Hello,

For having test wiiremote with bluesoleil and glovepie script, definitively not working fine :s

problem with aiming but good accuracy with crosshair, no digging so far!

But pretty strange, having setup lightgun config with wingun: thougt Mame was using directinput !

EG: Nuvve plugin psx2 does work with direct input no raw, and model 2 too (raw enable -> diseable).

off topic sorry

[Calamity]

Version 0.144u1 is uploaded:

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

groovymame32_0144u1.013d.rar
groovymame64_0144u1.013d.rar
0144u1_groovymame_013d.diff

Compiling notes:
---------------

Apply patches in this order:

1) 0144u1_diff (http://mamedev.org/updates.html)
2) hi_144.txt (http://mamestuff.lowtrucks.net/MKChamp/)
3) 0144u1_groovymame_013d.diff (http://mario.groovy.org/GroovyMame/WindowsATIDrivers/)

Stability notes:
---------------

Hopefully stability issues caused by HLSL integration have been finally fixed with this update:

Fixed HLSL memory leak and crash on exit on 32-bit targets.
[Ryan Holtz, Bat Country Entertainment]

However, I'm seeing a new crash on exit but this only happens with GroovyMAME build. I'll work to fix it as soon as possible, until then, remind to use it with care.

The crash was in official MAME too. I think I've fixed it, need more testing. I've submitted it to mamedevs.
New binaries uploaded.

[jimmy2x2x]

Now that's what I call service!

Thanks Calamity very much appreciated here, these Namco Classics are the main reason I mamed this cocktail cab - my dream is almost complete

I will donate again this weekend when I get paid 

[Calamity]

Version 0.144u2 is uploaded:

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

groovymame32_0144u2.013d.rar
groovymame64_0144u2.013d.rar
0144u2_groovymame_013d.diff

Compiling notes:
---------------

Apply patches in this order:

1) 0144u1_diff -> 0144u2_diff (http://mamedev.org/updates.html)
2) hi_144.txt (http://mamestuff.lowtrucks.net/MKChamp/)
3) 0144u2_groovymame_013d.diff (http://mario.groovy.org/GroovyMame/WindowsATIDrivers/)

Stability notes:
---------------

They've included my fix 

- 04538: [Crash/Freeze] Many sets: Crash on exit on 32-bit Windows XP
         (-video d3d) (Antonio Giner)

No more crashes on exit for now. As a side effect, this makes possible to lauch games from the internal menu again.

[lettuce]

Nice!, thanks for this Calamity!!!! 

[Paradroid]

They've included my fix

Good job! And, thanks!

[Ansa89]

I tried groovymame 0.144, but I'm facing some serious issues: some games (such as NBA Hangtime, Metal Slug 1/2/3/X, Aero Fighters 2/3) aren't show well.
I played these games with previous version of groovymame without problems, but now there is a lot of flickering (it seems the display is out of frequency).

Now I'm asking: is a problem with groovymame patch, mame itself or with my config?
If you need some tests to be done, just tell me.

Some info:
OS: slackware 13.37 64bit
Kernel: 3.2.1 with 15KHz patch
Videocard: ATI HD5450
Display: PAL TV (without freq trimmer)
Frontend: advancemenu-2.5.0
Emulator: mame-0144u6 with hiscore-0144u5 and groovymame-0144u2 patches

Thanks for help.

[Calamity]

Emulator: mame-0144u6 with hiscore-0144u5 and groovymame-0144u2 patches

So you've compiled your own binary?
Have you tried this binary: GroovyMame32x144u2Wiimote.tar.bz2 here: http://mario.groovy.org/GroovyMame/WindowsATIDrivers/

[Ansa89]

Yes, I compiled the binary by myself.
I don't have tried that precompiled tarball, because I was thinking that the "32" means "for 32 bit" (and my system is 64 bit).

Eventually I will try to install multilib and try the precompiled binary (or compile it myself starting from mame-0144u2).

[Ansa89]

The precompiled binary is for 32 bit systems and requires some specific libraries which I haven't; so I compiled mame-0144u2 with hiscore-0144 and groovymame-0144u2 patches (as specified here), but the problems persist .

[Calamity]

Eventually I will try to install multilib and try the precompiled binary (or compile it myself starting from mame-0144u2).

Can't 64-bit Linux run 32-bit applications natively? Win-64 certainly can.

[Calamity]

The precompiled binary is for 32 bit systems and requires some specific libraries which I haven't; so I compiled mame-0144u2 with hiscore-0144 and groovymame-0144u2 patches (as specified here), but the problems persist .

Well, that's strange as I've tested the binary included in the new Live-CD (144u2) and it worked perfectly for me.

Please guys provide some logs when reporting issues (-v -md 4)

[Calamity]

BTW make sure you create a fresh mame.ini (run groovymame with the -cc param).

[Ansa89]

BTW make sure you create a fresh mame.ini (run groovymame with the -cc param).

I'm sure I've NOT created a fresh mame.ini.
Is there a way to automatically merge the new mame.ini with the old one?

Please guys provide some logs when reporting issues (-v -md 4)

Is there a way to do this from advmenu?

[Ansa89]

Ok, I tried to create a new mame.ini, but no luck.

Here is an error (probably generated by xrandr) when I try to launch NBA Hangtime:

Code: [Select]

SwitchRes v0.013: [nbahangt] (1) horizontal (399x253@54.82)->(400x256@54.82)->(400x256@29.37)
-syncrefresh specified without -waitsync. Reverting to -nosyncrefresh
SwitchRes v0.013: [nbahangt] (1) horizontal (400x254@54.82)->(400x256@54.82)->(400x256@29.37)
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  149 (RANDR)
  Minor opcode of failed request:  16 (RRCreateMode)
  Serial number of failed request:  33
  Current serial number in output stream:  33
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  149 (RANDR)
  Minor opcode of failed request:  19 (RRDeleteOutputMode)
  Serial number of failed request:  33
  Current serial number in output stream:  34
X Error of failed request:  BadAccess (attempt to access private resource denied)
  Major opcode of failed request:  149 (RANDR)
  Minor opcode of failed request:  17 (RRDestroyMode)
  Serial number of failed request:  33
  Current serial number in output stream:  34
Average speed: 100.00% (8 seconds)So initially I blamed xrandr, but then I started Metal Slug 3, the display started flickering and I switched to tty1 to see the xrandr error...

Code: [Select]

SwitchRes v0.013: [mslug3] (1) horizontal (320x224@59.19)->(320x224@59.19)->(320x224@33.39)
-syncrefresh specified without -waitsync. Reverting to -nosyncrefresh
Average speed: 100.00% (10 seconds)No errors at all and the screen continuing flickering .

Now what?

[Calamity]

I'll check that game today and report.

[Calamity]

Hi Ansa89, nbahangt is working great here with the new live-cd (144u2). So I don't know what can be happening with your system. Please attach a complete log so I can see something, you can't do it from AdvMenu, you need to go to command line for that.

[Calamity]

Code: [Select]

SwitchRes v0.013: [nbahangt] (1) horizontal (399x253@54.82)->(400x256@54.82)->(400x256@29.37)


Something is wrong here: the 29.37 value. What monitor type have you selected?

[Ansa89]

you can't do it from AdvMenu, you need to go to command line for that.

So I start X with a terminal and then "groovymame64 -v -md 4 nbahangt &> file.log", right?

Something is wrong here: the 29.37 value. What monitor type have you selected?

I selected "pal" since my diplay is a pal tv (as posted before).
I should better regenerate the switchres.conf and xorg.conf?

[Calamity]

So I start X with a terminal and then "groovymame64 -v -md 4 nbahangt &> file.log", right?

Yes, but I like to type it in this order:

groovymame romname -v -md 4 >romname.txt

I selected "pal" since my diplay is a pal tv (as posted before).
I should better regenerate the switchres.conf and xorg.conf?

Well, that's something...
Just edit mame.ini and change the monitor_specs0 value for this one:

   monitor_specs0  15625-16200,49.50-65.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288,448

[Ansa89]

Yes, but I like to type it in this order:

groovymame romname -v -md 4 >romname.txt

Ok .

Just edit mame.ini and change the monitor_specs0 value for this one:

   monitor_specs0  15625-16200,49.50-65.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288,448

It looks like a modeline...How you get it?
Do you think the problem is the tv?

[Calamity]

It's not a modeline, it's a monitor_specs line  It tells groovymame how your modelines need to be calculated.
Your TV should be fine, it's just that I probably broke the PAL monitor type with my patches.

[Ansa89]

Ok, tomorrow I will try this out .

[Ansa89]

Ok, now it seems to work.

From your patch I can see (file "src/emu/switchres/monitor.c"):

Code: [Select]

...
} else if (!strcmp(type, "pal")) {
               monitor[0].HfreqMin = 15625;
               monitor[0].HfreqMax = 15625;
               monitor[0].VfreqMin = 50;
               monitor[0].VfreqMax = 50;
               monitor[0].HfrontPorch = 1.650;
               monitor[0].HsyncPulse  = 4.700;
               monitor[0].HbackPorch  = 5.000;
               monitor[0].VfrontPorch = 0.064;
               monitor[0].VsyncPulse  = 0.192;
               monitor[0].VbackPorch  = 1.024;
               monitor[0].HsyncPolarity = 0;
               monitor[0].VsyncPolarity = 0;
               monitor[0].ActiveLinesLimit = 312.5;
               monitor[0].VirtualLinesLimit = 576;
               return 1;
...This is a little different from the monitor_spec you give me.


Next question: should I better leave the "monitor_spec0 blahblah" into mame.ini (for next releases) or I can safely remove it when upgrade groovymame?

[Ansa89]

One more thing: after setting the monitor_spec0, some vertical games (galaga, galaga88, galaxian) were displayed out of frequency.
Looking your monitor_spec0, I changed it this way:

Code: [Select]

15625-15800,49.50-60.50,2.000,4.700,8.000,0.064,0.160,1.056,0,0,288,448
As you can see, the previous vfreq and hfreq were too high, so I searched for pal specification and adjusted the values to something more comfortable.
Now everyone seem happy (me too) .