groovymame latest build + cave-sh3

[Endprodukt]

Is it possible to reimplement the driver? Is it considered? I'd love to play those games with groovymame. Can someone help out?

[dgame]

You have to compile your own GroovyMAME.

1. Get MAME compiler and sourcecode. http://mamedev.org/tools/ and http://mamedev.org/release.html or http://mamedev.org/oldrel.html
2. Apply [patch] the MAME 'u1, u2, etc.) update diffs. http://mamedev.org/updates/  How?  http://mamedev.org/updates.html
3. Apply the hiscore patch diff. http://forum.arcadecontrols.com/index.php/topic,64298.0.html
4. Apply GroovyMAME patch diff. http://code.google.com/p/groovyarcade/downloads/list
5. Apply cavesh3_147u3.diff http://www.gooogle.com?
6. Compile

[Endprodukt]

thanks, very nice. problem is: I can't seem to find u1, u2 diff files on that site

[dgame]

http://mamedev.org/updates/

scroll down to:

0147u1_diff.zip     07-Oct-2012 23:53    2.4M

[Calamity]

Hi current hiscore patch in MKChamp's thread won't work, use this one instead:

http://forum.arcadecontrols.com/index.php/topic,128907.msg1326612.html#msg1326612

[Endprodukt]

Thanks guys!!!

[MonkeyJug]

Is it possible to somehow get the cave games running on the linux iso?

[dgame]

I don't know how to get it into the Linux iso, but it seems to work for Linux.

Google: cavesh3_for_mame0148_by_vivanno.diff

 Translate this page

[ckong]

I tried to compile with Headsoft's Mame compiler. I first pached 0147u1.diff, u2.diff and u3.diff. Then I patched the hi_147.txt, 0147u3_groovymame_014.diff and the cavesh3_147u3.diff. This went all OK, at least, I didn't get any error messages, just the message 'finished' each time. And I see for instance the cavesh3.c driver in the source mame driver folder.

But then, when i click 'GO', the compiler will not compile, see the attched picture fo the error message. Why will it not compile?

Edit: I tried it in the 'old-fashioned' but proven way, using command line, and it compiled fine. I also did an upgrade, so now I'm running my own Grooymame version 0.148 with high scores and SH3 games. Great. 

I probably did something wrong in the MameCompiler program.

[lettuce]

EDIT: OK i found it

[planexcvs]

I don't know how to get it into the Linux iso, but it seems to work for Linux.

Google: cavesh3_for_mame0148_by_vivanno.diff

 Translate this page

That patches fine with groovymame's 0148u1 build? Because I've been looking for a groovymame 0.148 release which was skipped over for u1.

[dgame]

I stopped at 148 and waiting for 149 to update again.

The  "cavesh3_147u3.diff" works with 148. It will probably work with the u1, u2, etc. updates as well.

I think  cavesh3_for_mame0148_by_vivanno.diff may be for Linux only as it crashes the patch command on Windows.

EDIT: ckong wrote that cavesh3_for_mame0148_by_vivanno.diff works with Windows.

[dgame]

The  "cavesh3_147u3.diff" works with 148u2.

[Jonny G]

Thanks for confirming that dgame. I might have a go at compiling later.

Just wondering what to expect in relation to my romsets and clrmamepro though.

As support for the cave games was removed a few versions ago, does that mean that CMP will only scan for the cave roms with a correctly compiled mame.exe? Or are the cave roms still listed with a standard 0.148u2 exe, just unplayable?

[dgame]

The Cave SH3 stuff is completely gone from MAME. The diff patch puts them back in.

If you use the patch the Cave SH3 ROMS will be playable if you have them and missing if you don't.

[lettuce]

Shame the Cave SH3 drivers cant be added to GroovyArcade live-CD 2013-02-24!!. Maybe ves will add it to an update?

[ckong]

........I think  cavesh3_for_mame0148_by_vivanno.diff may be for Linux only as it crashes the patch command on Windows.

the vivanno diff  does work with windows. I used it to compile a 0148 groovymame version last week , which works just fine. 

[dgame]

Thanks, I edited my post above. Still does not work for me though.

Get this error:

patching file src/mame/drivers/cavesh3.c
Assertion failed: hunk, file patch-2.5.4/patch.c, line 343

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Not a big deal as the other one works fine for me.

I ran them through diff and besides minor formatting differences the cavesh3_147u3.diff adds “ $(MAMESRC)/drivers/csh3blit.c “ to the mame.mak file and cavesh3_mame0148_by_vivanno.diff does not. I don’t know if this makes a difference when compiling or running. It may be redundant as both create the csh3blit.c file and it gets called a lot.

[lettuce]

I have been trying to compile mame using Mr Do's guide (http://mrdo.mameworld.info/compile.php). But i get an error at the end of trying to apply the first diff, if you look at the bottom of the compile you can see the error. Any ideas???............

C:\mamesrc>patchmame 0148u1

C:\mamesrc>set path=c:\mingw\mingw64-w64\bin

C:\mamesrc>patch -p0 -E  0<0148u1.diff
patching file hash/32x.xml
patching file hash/3do_m2.xml
patching file hash/a2600.xml
patching file hash/a2600_cass.xml
patching file hash/a5200.xml
patching file hash/a7800.xml
patching file hash/a800.xml
patching file hash/adam_cart.xml
patching file hash/alice32.xml
patching file hash/alice90.xml
patching file hash/amiga_flop.xml
patching file hash/amigaaga_flop.xml
patching file hash/amigaecs_flop.xml
patching file hash/amigaocs_flop.xml
patching file hash/apfm1000.xml
patching file hash/apogee.xml
patching file hash/apple1.xml
patching file hash/apple2gs.xml
patching file hash/aquarius.xml
patching file hash/arcadia.xml
patching file hash/atom.xml
patching file hash/b2m.xml
patching file hash/bbca_cass.xml
patching file hash/bbcb_cass.xml
patching file hash/bbcm_cart.xml
patching file hash/bbcm_cass.xml
patching file hash/bk0010.xml
patching file hash/c128_flop.xml
patching file hash/c64_cart.xml
patching file hash/c64_cass.xml
patching file hash/c64_flop.xml
patching file hash/cbm2_flop.xml
patching file hash/cbm8096_flop.xml
patching file hash/cbm8296_flop.xml
patching file hash/cd32.xml
patching file hash/cdi.xml
patching file hash/cdtv.xml
patching file hash/coco_cart.xml
patching file hash/coleco.xml
patching file hash/cpc_cass.xml
patching file hash/cpc_flop.xml
patching file hash/crvision.xml
patching file hash/einstein.xml
patching file hash/electron_cart.xml
patching file hash/ep64.xml
patching file hash/famicom_flop.xml
patching file hash/fm77av.xml
patching file hash/fm7_cass.xml
patching file hash/fm7_disk.xml
patching file hash/g7400.xml
patching file hash/galaxy.xml
patching file hash/gameboy.xml
patching file hash/gamegear.xml
patching file hash/gba.xml
patching file hash/gbcolor.xml
patching file hash/genius.xml
patching file hash/ibm5140.xml
patching file hash/ibm5150.xml
patching file hash/ibm5150_cass.xml
patching file hash/ibm5170.xml
patching file hash/ibmpcjr_flop.xml
patching file hash/interact.xml
patching file hash/intv.xml
patching file hash/iq151_flop.xml
patching file hash/juicebox.xml
patching file hash/kayproii.xml
patching file hash/kc_cass.xml
patching file hash/kc_flop.xml
patching file hash/korvet_flop.xml
patching file hash/lviv.xml
patching file hash/m20.xml
patching file hash/m5.xml
patching file hash/mac_hdd.xml
patching file hash/megacd.xml
patching file hash/megacdj.xml
patching file hash/megadriv.xml
patching file hash/megapc.xml
patching file hash/megatech.xml
patching file hash/microvision.xml
patching file hash/mikrosha.xml
patching file hash/mo5_cart.xml
patching file hash/mpz80.xml
patching file hash/msx1_cart.xml
patching file hash/msx1_cass.xml
patching file hash/msx2_cart.xml
patching file hash/mz2000_cass.xml
patching file hash/mz2000_flop.xml
patching file hash/mz700_cass.xml
patching file hash/mz800_cass.xml
patching file hash/n64.xml
patching file hash/neocd.xml
patching file hash/neogeo.xml
patching file hash/nes.xml
patching file hash/ngp.xml
patching file hash/ngpc.xml
patching file hash/odyssey2.xml
patching file hash/ondra.xml
patching file hash/orao.xml
patching file hash/orion_cart.xml
patching file hash/orion_cass.xml
patching file hash/orion_flop.xml
patching file hash/orionpro_flop.xml
patching file hash/osborne1.xml
patching file hash/p500_flop.xml
patching file hash/partner_cass.xml
patching file hash/partner_flop.xml
patching file hash/pb2000c.xml
patching file hash/pc8801_cass.xml
patching file hash/pc8801_flop.xml
patching file hash/pc88va.xml
patching file hash/pcecd.xml
patching file hash/pcw.xml
patching file hash/pecom_cass.xml
patching file hash/pentagon_cass.xml
patching file hash/pet_cass.xml
patching file hash/pet_flop.xml
patching file hash/pet_rom.xml
patching file hash/pico.xml
patching file hash/pippin.xml
patching file hash/plus4_cart.xml
patching file hash/plus4_cass.xml
patching file hash/plus4_flop.xml
patching file hash/prof180.xml
patching file hash/prof80.xml
patching file hash/psion.xml
patching file hash/psx.xml
patching file hash/pv1000.xml
patching file hash/pv2000.xml
patching file hash/pyl601.xml
patching file hash/radio86.xml
patching file hash/samcoupe_cass.xml
patching file hash/samcoupe_flop.xml
patching file hash/sat_cart.xml
patching file hash/saturn.xml
patching file hash/scv.xml
patching file hash/segacd.xml
patching file hash/sg1000.xml
patching file hash/smc777.xml
patching file hash/sms.xml
patching file hash/snes.xml
patching file hash/socrates.xml
patching file hash/softwarelist.dtd
patching file hash/sorcerer_cass.xml
patching file hash/sorcerer_flop.xml
patching file hash/special_cass.xml
patching file hash/special_flop.xml
patching file hash/spectrum.xml
patching file hash/spectrum_cass.xml
patching file hash/spectrum_flop.xml
patching file hash/studio2.xml
patching file hash/stv.xml
patching file hash/superpet_flop.xml
patching file hash/svi318_cart.xml
patching file hash/svi318_cass.xml
patching file hash/svi318_flop.xml
patching file hash/svision.xml
patching file hash/tek4052_cart.xml
patching file hash/ti99_cart.xml
patching file hash/to770_cart.xml
patching file hash/to7_cart.xml
patching file hash/ut88.xml
patching file hash/uzebox.xml
patching file hash/vboy.xml
patching file hash/vectrex.xml
patching file hash/vic1001_cart.xml
patching file hash/vic1001_cass.xml
patching file hash/vidbrain.xml
patching file hash/vip.xml
patching file hash/wswan.xml
patching file hash/x07_card.xml
patching file hash/x1_cass.xml
patching file hash/x1_flop.xml
patching file hash/x68k_flop.xml
patching file hash/xegs.xml
patching file hlsl/bloom.fx
patching file hlsl/downsample.fx
patching file hlsl/focus.fx
patching file hlsl/phosphor.fx
patching file hlsl/post.fx
patching file hlsl/primary.fx
patching file hlsl/vector.fx
can't find file to patch at input line 279569
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- makefile-old       2013-01-09 20:46:18.000000000 +0100
|+++ makefile   2013-02-09 17:32:21.000000000 +0100
--------------------------
File to patch:

[Jonny G]

Does anyone know if the cavesh3 diff will enable support on a build of GM for linux?

[Calamity]

Does anyone know if the cavesh3 diff will enable support on a build of GM for linux?

Well there's no reason why it shouldn't, the emulator layer is system independent.

[Jonny G]

Does anyone know if the cavesh3 diff will enable support on a build of GM for linux?

Well there's no reason why it shouldn't, the emulator layer is system independent.

OK. Thanks. So to build GM for Linux, i proceed As normal using the regular windows cli sources and diffs. Just using the Linux GM diff at the end instead?

[Jonny G]

Ah. Hit a problem. Is there such as thing as a groovymame linux diff as opposed to the standard windows diff?

[machyavel]

Hello Jonny G,

If you want to compile GM for linux you need to do the process under linux. However, I don't know if it's just me but I faced some issues, anyway let me describe the whole thing:

- boot from your GM LiveCD or your persistent install
- launch LXDE
- retrieve the mame source and the needed u diffs, the HI diff, the GM diff and SH3 diff
- apply patch in order described by dgame at the beginning of the thread (type "patch -p0 -E --binary < yourpatch")
- 1st issue was with the SH3 patch, there is one error in version.c but it doesn't matter at all
- compile (type "make")
- 2nd issue was related to python version, you just need to change "python" to "python2" in the file "makefile" from mamesrc and in the src/emu/cpu/m6502/m6502make.py script
so "PYTHON = @python" becomes "PYTHON = @python2" and "#!/usr/bin/python" becomes "#!/usr/bin/python2"
- compile again
- 3rd issue happened right after, related to some Werror, I think it doesn't matter because it's a tandy driver that causes the problem
anyway, just remove the "Werror" from this line "CCOMFLAGS += -Werror" in the file "makefile", it then becomes "CCOMFLAGS +="
- compile again wait a bit and normally you're done...

[jumbosinbad361]

Hello Jonny G,

If you want to compile GM for linux you need to do the process under linux. However, I don't know if it's just me but I faced some issues, anyway let me describe the whole thing:

- boot from your GM LiveCD or your persistent install
- launch LXDE
- retrieve the mame source and the needed u diffs, the HI diff, the GM diff and SH3 diff
- apply patch in order described by dgame at the beginning of the thread (type "patch -p0 -E --binary < yourpatch")
- 1st issue was with the SH3 patch, there is one error in version.c but it doesn't matter at all
- compile (type "make")
- 2nd issue was related to python version, you just need to change "python" to "python2" in the file "makefile" from mamesrc and in the src/emu/cpu/m6502/m6502make.py script
so "PYTHON = @python" becomes "PYTHON = @python2" and "#!/usr/bin/python" becomes "#!/usr/bin/python2"
- compile again
- 3rd issue happened right after, related to some Werror, I think it doesn't matter because it's a tandy driver that causes the problem
anyway, just remove the "Werror" from this line "CCOMFLAGS += -Werror" in the file "makefile", it then becomes "CCOMFLAGS +="
- compile again wait a bit and normally you're done...

Would love a compiled version if you have one please....

[jumbosinbad361]

Machyavel, thank you...your a genius.

[wolfsoft]

I am currenty trying to add highscore and cave support to gmame0148u5
After the "usual" diffs
I tried:

Code: [Select]

C:\MiniGW\source\mame0148u5high>patch -p0 -E < cavesh3_147u3.diff
patching file src/mame/drivers/cavesh3.c
patching file src/mame/drivers/csh3blit.c
patching file src/mame/mame.lst
Hunk #1 succeeded at 39 with fuzz 2.
patching file src/mame/mame.mak
Hunk #1 succeeded at 1776 (offset 36 lines).
Hunk #2 FAILED at 2415.
1 out of 2 hunks FAILED -- saving rejects to file src/mame/mame.mak.rej

Does it works?  I am not a programmer :-( Or do I need  a newer cavesh3 driver?
cheers

mame.make.rej shows:

Code: [Select]

***************
*** 2414,2417 ****
  $(VIDEO)/n64.o: $(MAMESRC)/video/rdpfiltr.c
  $(DRIVERS)/bfm_sc4.o: $(MAMESRC)/includes/bfm_sc45.h
  $(DRIVERS)/bfm_sc5.o: $(MAMESRC)/includes/bfm_sc45.h
 
--- 2415,2419 ----
  $(VIDEO)/n64.o: $(MAMESRC)/video/rdpfiltr.c
  $(DRIVERS)/bfm_sc4.o: $(MAMESRC)/includes/bfm_sc45.h
  $(DRIVERS)/bfm_sc5.o: $(MAMESRC)/includes/bfm_sc45.h
+ $(DRIVERS)/cavesh3.o: $(MAMESRC)/drivers/csh3blit.c
 



[wolfsoft]

I compiled the mame and it workes great ;-)

[wolfsoft]

I didn't get highscore saving from mkchamp to work...
I tried:
patch -p0 -E <0148u1.diff
patch -p0 -E <0148u2.diff
patch -p0 -E <0148u3.diff
patch -p0 -E <0148u4.diff
patch -p0 -E <0148u5.diff
patch -p0 -E <hi_148u5.diff
patch -p0 -E <0148u5_groovymame_014b.diff
patch -p0 -E <cavesh3_147u3.diff

nonag and loadingpacht is working, but no highscore saving :-(

after this I tried it with mame 0149s and its working... with highscore saving :-(

patch -p0 -E <hi_149.diff
patch -p0 -E <cavesh3_147u3.diff

any hints ?

[dgame]

Try putting hiscore.dat inside the "hi" folder.

[wolfsoft]

thanks copying highscore.dat into the hi folder works great :-)

[Tzakiel]

I'm trying to compile mame 149 + hiscore (from here) + groovymame 149 (from groovymame code site) + cave 149 diff (from http://www.systempixel.fr/extra/) in that order... I'm using the mingw compiler from the mame site.

The hiscore and groovymame diffs patch perfectly... here is my result from the cave diff:

C:\mame149>patch -p0 -E <cavesh3_0149u1.diff
patching file src/mame/drivers/cavesh3.c
patching file src/mame/mame.lst
Hunk #1 succeeded at 2711 (offset -28 lines).
patching file src/mame/mame.mak
Hunk #1 FAILED at 2034.
Hunk #2 succeeded at 2643 (offset -47 lines).
1 out of 2 hunks FAILED -- saving rejects to file src/mame/mame.mak.rej
patching file src/mame/video/csh3blit.inc

Is there some way I can get this to work?

[dgame]

It looks like only the mame.mak file patch didn't work.

Post the contents of  file src/mame/mame.mak.rej as that will give clues on how to fix it.

[jdubs]

I'm up and running.  Thanks folks!!!

-Jim

[blontic]

New cave 151 file available  http://www.systempixel.fr/extra/

[Tzakiel]

Just a question.. what is the difference between compiling mame 151 with cave 150 vs cave 151?  I did it with cave 150 and it seems to work OK. Would 151 be an improvement to match my mame source?

[cools]

More games in 151.

[Monkee]

May someone share with me the groovymame 151 64bits compiled with the Cave SH3, nonag, Neogeo OC and hiscore diffs ? 

I never succeeded in compiling it... 

[planexcvs]

May someone share with me the groovymame 151 64bits compiled with the Cave SH3, nonag, Neogeo OC and hiscore diffs ? 

I never succeeded in compiling it... 

I also tried with Neogeo OC with no luck. I've had success with compiling it without the Neogeo OC bios, which I don't think is that necessary since you can manually overclock.

[Monkee]

Can you maybe share with me the one without the OC? 

[blontic]

Can you maybe share with me the one without the OC? 

Pretty sure there is nothing wrong with posting these anymore. Never used Mega before so good chance these are encrypted or something stupid. But here are Win64 compiled versions with Hiscore151/Cave(new)151/Groovymame151

Mame64 https://mega.co.nz/#!4h0mBALC!K3mKc0QpnidkM7OFpx5lsx5dOW0GruFjQZPLSKh3_Ck
Ume64 https://mega.co.nz/#!skExTYZC!Hw9uA1V3SyPrpOwhhPJS-0k3RtYFj_08iDgHhu1IQyc

[Monkee]

Thanks a lot. 
I have no idea if it's fine to let the links here, i hope so... 

[blontic]

Thanks a lot. 
I have no idea if it's fine to let the links here, i hope so... 

Can't see why not. Even David Haywood said that it's now been over 2 years since Cave asked for the driver to be removed.

[joeblade2]

Hi blontic, sorry to ask a noob question but I take it I still need to put a hiscore.dat into a hi folder for this to work?

[blontic]

Hi blontic, sorry to ask a noob question but I take it I still need to put a hiscore.dat into a hi folder for this to work?

That is correct. Download the latest one http://www.mameworld.info/highscore/download.htm

[cools]

Here's a 64bit Windows Groovy build based on the 152ex1 sources Haze posted.

https://drive.google.com/file/d/0BxaCVgxhLwHFU01YdHo1STN0d2c/edit?usp=sharing

Cave runs well (core2duo 3ghz) but the sound goes nasty whenever there's slowdown - not sure why.

[lettuce]

Here's a 64bit Windows Groovy build based on the 152ex1 sources Haze posted.

https://drive.google.com/file/d/0BxaCVgxhLwHFU01YdHo1STN0d2c/edit?usp=sharing

Cave runs well (core2duo 3ghz) but the sound goes nasty whenever there's slowdown - not sure why.

What's ex1 all about then?

[Monkee]

It's like the "u" releases in the past editions of Mame but unofficial this time.

[Bimmy]

Any chance I can get this in 32-bit?

[Monkee]

Any chance I can get this in 32-bit?

+1 

[cools]

Not from me I'm afraid, I have no 32bit compiler set up here.

[Monkee]

I'm wondering though if it's a good idea to use the "Ex" releases due to the fact that it's not official, it could be a pain to update/find the right roms...

[cools]

All of the ones you're interested in are available publicly.

[Monkee]

I'm not sure to understand what you mean cools, what I meant is that the [romsite name redacted] (if you see what I mean ) as no rom for the "Ex" releases and due to the fact that it is one of (or the) the best place to get the update of your romset, it's a bit annoying.

[lettuce]

So what errrr unofficial in these EX complies then?

[Monkee]

It's not supported by the "Mame team".

[dgame]

Well, well, well. With 152ex1 we finally get the new cavesh3 driver "cv1k.c" that should perform better than the old "cavesh3.c" driver. Now you can set the Blitter Delay in the Slider Controls.  Nice. 

Source: http://mamedev.emulab.it/haze/2014/01/01/ume0152ex1/

[cools]

I'm not sure to understand what you mean cools, what I meant is that [romsite name redacted] (if you see what I mean ) as no rom for the "Ex" releases and due to the fact that it is one of (or the) the best place to get the update of your romset, it's a bit annoying.

Learn how to use clrmame to build a set including only the games you want, and keep it separate from your archive folder.

If the games you want aren't in the dome, find them elsewhere and merge them in to this non dome set. Then when that needs update, merge from in use to archive before updating.

In short, learn clrmame.

[Monkee]

Ok I'll do that then! 

[Sledge]

so these Cavesh3 games are part of mame? or what's the story?
If the games are added to the correct folder do they automatically show in hyperspin etc? or is there a fair amount of fiddling needed?

[brad808]

so these Cavesh3 games are part of mame? or what's the story?
If the games are added to the correct folder do they automatically show in hyperspin etc? or is there a fair amount of fiddling needed?

They always showed in hyperspin assuming you had the latest database (after they had been originally added of course).

[blontic]

Newer 0.152 cave diff is available. Builds fine with groovy and hiscore patches http://www.systempixel.fr/extra/

[Sledge]

Is Cave-sh3 only 23 or so games? (some of which are just clones as well?)
doesn't seem very worthwhile...

[cools]

Depends if you like them or not. If you do it's a huge deal having them emulated, considering the price of the PCBs.

[Monkee]

Of course it's a big deal!
It's Cave! 

[MonkeyJug]

i posted in the linux cd thread, but i'll repeat it here as it's probably more appropriate:

any chance somebody (ves?) could knock up a 0.152 64-bit linux compile with the new & improved cave driver?

[Sledge]

So, yeah the games seem ok
A few good ones in there..

But is there a site that explains how to play them?
It's all in Japanese, so i can't see what buttons do what.. and i don't know how i SHOULD be playing them...

[MonkeyJug]

So, yeah the games seem ok
A few good ones in there..

But is there a site that explains how to play them?
It's all in Japanese, so i can't see what buttons do what.. and i don't know how i SHOULD be playing them...

have a read around on this:

http://shmups.system11.org/

ask for some help there and i'm sure you'll get it...

caution though, some of those guys are anti-mame! :p

[blontic]

i posted in the linux cd thread, but i'll repeat it here as it's probably more appropriate:

any chance somebody (ves?) could knock up a 0.152 64-bit linux compile with the new & improved cave driver?

Just run the groovyarcade updater and get the latest groovy ex1 version. It contains the cave drivers.

[Tzakiel]

Im looking for a 32 bit version of groovymame that can run Dai-fukkatsu.  Anyone able to help me out? 

EDIT: nevermind I got compiling to work for once.   Let me know if anyone needs a 32 bit 152 groovymame with SH3

[Monkee]

Me!  I'm looking for a 32bit version since quite a while. That would be great if you can share it.

Just two question (but no matter the answer, I'm taking it ):
Did you compiled it with the new cavesh3 driver "cv1k.c" that seems to perform better than the old "cavesh3.c" driver?
Did you compiled it with the Hiscore?

Thanks a lot mate.

P.S.: If you have the 64bit version of the v152 with cave drivers, I could also be interested for a friend of mine.

[Tzakiel]

I used the 152 diff from the French site. I don't think that is the one you are talking about. Does it really run better? I have been getting 100% no problem and everything seems good.

It has hiscore, cave 152 and groovymame compiled. Let me know if you still want a link.

[Monkee]

Yes for sure i'd love a link. 

I don't know if the other driver works better, I just know that you can set the blitter delay wich is pretty cool but there's maybe some problem with the sound on the other hand so... 

P.S.: Really cool Cabinet man. You have a PM

[Tzakiel]

mame 152, 32bit, cave, hiscore, groovymame

https://mega.co.nz/#!w1NSTRII!foR1g2Vx2z5kPM5JyLl3V3r4fUt5_2sjFBJIxcZ41Ig

[Monkee]

Thanks man.
If someone has the 64bit version of the v152 with cave drivers, I could also be interested for a friend of mine.

[Sledge]

Thanks man.
If someone has the 64bit version of the v152 with cave drivers, I could also be interested for a friend of mine.

for windows? scroll up

[Monkee]

Thanks Sledge.
Yes for Windows but I see only the 152ex1 & the 151...

[Sledge]

Thanks Sledge.
Yes for Windows but I see only the 152ex1 & the 151...

yup.. so use the 152ex1
probably exactly the same... no issue here at least..

[Paradise]

The 152ex1 does not have the nonag hiscore

[Tzakiel]

Hm, so now that I am getting more serious about SHMUPs, I am wondering how much better the new CAVE driver might be. The existing one works well in that it runs games at 100% for me, but I am starting to realize that they run a bit "too" fast - the Arcade originals have slowdown when there is a lot of bullets on screen. So I am wondering if I should compile MAME .152 with the new cv1k.c driver diff or if it's best to just wait for .153 and hope they put it back in the official release (and hopefully address sound, etc)  I saw Haze post somewhere saying that basically the new cv1k.c driver is has some speed issues because it's back on the path of accuracy rather than hacks. Hopefully it will now get refined into a good, accurate driver.

[blontic]

The 152ex1 does not have the nonag hiscore

It does you just need to set it in the mame.ini file to turn off the nagscreen. Like this :

disable_hiscore_patch   0 
disable_nagscreen_patch 0
disable_loading_patch   0

[Tzakiel]

Is it actually neccesary to apply the hiscore patch if you are patching the groovymame diff in anyway, as the front of this thread details, or does patching in groovymame automatically add hiscore support?

[cools]

Yes, no.

[Tzakiel]

Thanks, cools, I sent a PM. Having trouble finding how to compile mame.exe rather than UME based on haze's sources.

[Monkee]

Tzakiel, I can see that you're experimenting to find the best, please let us know of your returns, I'm super interested! 

[Tzakiel]

Tzakiel, I can see that you're experimenting to find the best, please let us know of your returns, I'm super interested! 

Will do. All I'm trying to do is play the latest cave games in groovymame with something closer to PCB bullet slowdown (tho its still not going to be the same, I realize)

[dgame]

Thanks, cools, I sent a PM. Having trouble finding how to compile mame.exe rather than UME based on haze's sources.

> make TARGET=mame

[Tzakiel]

Thanks, cools, I sent a PM. Having trouble finding how to compile mame.exe rather than UME based on haze's sources.

> make TARGET=mame

Aha.  thanks.

[blontic]

Is it actually neccesary to apply the hiscore patch if you are patching the groovymame diff in anyway, as the front of this thread details, or does patching in groovymame automatically add hiscore support?

If you have trouble let me know what you want and I can compile and post it for you

[Tzakiel]

I'm set now, just testing everything. Not sure if I see much difference so far. Are blitter delay settings on by default? My bullets still come fast and furious even at high blitter delay settings but it could just be me not being sensitive to the difference.

[Monkee]

You have to press Tab, then select "Slider controls", then "Blitter Delay" and try 63%, it's a good base to start from.

[Tzakiel]

Yep I have been playing with sliders but not sure if there was also a way to globally enable it or disable. I will see if I can compare to the videos online. For instance:

[blontic]

Would be great to get a list of games and the settings we should be using. I guess this will change as the driver keeps getting updated though

[Monkee]

I was trying to make a list from what I've found on schmups.system11 and here is the result but please be aware that I didn't try it myself so it's possibly better to check, share feedbacks and then ameliorate this list:

With Slowpoke Mame:
In general: 63%
Futari: around 62-66%
Futari BL: unplayable
Deathsmiles: 63% (equal to the 360 port, apparently)
ESPgaluda 2 needs more slowdowns, and IBARA/PINKSWEETS/MMP work "fine".

With the driver cv1k.c:
Mushi Futari BL: 59%
DDP DFK: 50%
DS / DS MBL: 63%

P.S.:Can you guys post a compiled version of GM v152(ex1 or not) with the cv1k.c driver and 32bits if it's what you're using, I'm interested. 

[Tzakiel]

I found in addition to the slider you must go to game configuration and turn blitter delay on. Requires restart of mame.

I like the idea of making a list. The problem is knowing what is "right" to compare to. I don't have the pcbs and I doubt many people do. Videos is probably about all we can do.

[Tzakiel]

So futari black label isn't showing in the new mame I compiled 152ex2. Everything else seems to show up, but not that one. Only 1.0 and 1.5.

[Tzakiel]

Here is 152 ex2 32 bit with grovymame, hiscore (cave is now in the regular source)

https://mega.co.nz/#!8pN3BIJC!zM3PV3Z8wgv35GzoAK39necoVm7yz5lEMdXOaSD_6EE

Now that I turned blitter delay on and played with it, it definitely has an effect. To me it's more playable. I'm pretty happy with this build and hope to see it improve in 153 and beyond.

[Monkee]

Awesome! Thanks a lot Tzakiel, you didn't encounter sound problems when there is slowdowns (the ones that Cools talked about before)?

[Tzakiel]

No. I have a fast CPU so maybe that's why, or maybe it got fixed.

[Monkee]

Hi guys, just to let you know, there is new versions of the cv1k on System Pixel. Enjoy! 

[Dalba]

Here is 152 ex2 32 bit with grovymame, hiscore (cave is now in the regular source)

https://mega.co.nz/#!8pN3BIJC!zM3PV3Z8wgv35GzoAK39necoVm7yz5lEMdXOaSD_6EE

Now that I turned blitter delay on and played with it, it definitely has an effect. To me it's more playable. I'm pretty happy with this build and hope to see it improve in 153 and beyond.

Hello,
sorry to bother you, but would it be possible for you to upload the 64bits version of 152ex2 with groovymame and hiscore ?

[Monkee]

Sorry for that, but I have a lot of problems with trying to compile my own Mames.
Can someone guide me somewhere or give me a link where I can get ShmupMame 4.2 '32bit with nonag?

Thanks