GroovyArcade2015 + ArcadeVGA 5000 - 50% speed, unable to launch from shell

[MarbleTyrant]

I'm starting to wonder if learning...

wiring/soldering
how arcade monitors work
how to use Linux

...might have been better as separate projects  .  I'm running a WG k7000 monitor and have managed to get my front-end loader / roms in order.  Several games, however, emulate at 50% exactly.  I don't think it's a performance issue, as I can use frame-skip to run everything very fast.  Frame skip 6/10 actually runs everything ABOUT 100%, but oscillates between 96% and 106%, making for a poor playing experience.

I've tried setting -video ddraw and -video d3d in mame.ini, but it doesn't seem to affect anything.  I'd like to post a log, but therein lies my second problem:

I'm unable to run GroovyMame or the frontend (AdvMenu) from the archLinux shell.  When I try, I receive this error:

Can't open display.
Can't open display.
Can't open display.
Segmentation fault (core dumped)

I'm able to run AdvMenu (and GroovyMame, subsequently) from the GroovyArcade setup utility, or if I let it boot up automatically.

Is this because GroovyArcade / GroovyMAME doesn't support my silly aVGA card?  All advice much appreciated!

[MarbleTyrant]

Fixed it!  I needed to change the UME.ini file rather than the MAME.ini file.  Or maybe I needed to change both?  Either way, running nice and smooth at 100% without any glitches!  I think it was forcing DirectDraw via -video ddraw that fixed the problem.

I'm not sure if MESS was integrated into MAME back when this GroovyArcade version was released.  If it was, then I wonder why there are two separate .ini files...?  Anyways, hope this helps some one else.

[Calamity]

Hi MarbleTyrant,

You can't use -video ddraw from GroovyArcade, that's a Windows only option. Use -video opengl instead.

I'm not sure if MESS was integrated into MAME back when this GroovyArcade version was released.  If it was, then I wonder why there are two separate .ini files...?  Anyways, hope this helps some one else.

At the time, MESS was integrated in the GroovyUME build already. So only the UME binary was included in the iso to save space. This was good. However, in order to mantain compatibility with old scripts, a symbolic link was created named groovymame that actually calls groovyume. A mame.ini file also exists which is not used because GroovyUME only reads ume.ini. I warned Ves this was a terrible idea because it would confuse users, as has been the case.

[jtslade]

You got to do it all and want to go to challenge yourself every day it's the only way....... it's it's definitely for us


Sent from my iPhone using Tapatalk

[MarbleTyrant]

Oh, and I also figured out why I couldn't run GroovyMame from the command line.  Xorg isn't active when trying to run things from the arch linux shell.  If you use LXDE and run the terminal, then Xorg will be active and GroovyMame will run.DNK