Recent Posts

Probably. My ring config is p1->p2->p3->p4...->p8->p1. No alternating in any weird order or anything.

It's getting built in the room. Everything was designed to be disassembled. The panels are all sitting in it's final resting place right now, just setting up a paint booth outside and they'll be sprayed and moved back in before assembly. It'll be setup right next to my DrumMania setup I built last year

Nice 

It would seem the DE10 Nano is overkill for this use. But we're not aware of any other smaller/cheaper board that doesn't lack something fundamental.

There's a project now to release a clone that uses the same cyclone chip for $99.

I am planning to move over to GroovyMister with one of these if they pan out

Beautiful

Thank you! Then it is probably just a misconfiguration, will look into it.

Mame 0265 build failed on bookworm as well, same output as posted above more or less

Code: [Select]

/usr/bin/ld: BFD (GNU Binutils for Raspbian) 2.40 assertion fail ../../bfd/elf32-arm.c:9885
/usr/bin/ld: BFD (GNU Binutils for Raspbian) 2.40 assertion fail ../../bfd/elf32-arm.c:9885
/usr/bin/ld: BFD (GNU Binutils for Raspbian) 2.40 assertion fail ../../bfd/elf32-arm.c:9885
/usr/bin/ld: BFD (GNU Binutils for Raspbian) 2.40 assertion fail ../../bfd/elf32-arm.c:9885
collect2: error: ld returned 1 exit status
make[2]: *** [mame.make:269: ../../../../../mame] Error 1
make[1]: *** [Makefile:1120: mame] Error 2
make: *** [makefile:1300: linux] Error 2
Build time took: 8h 48m 25s.
-----------------------------------------------------------------------------------
Build FAILED.
-----------------------------------------------------------------------------------


Have you tried playing games with those 4 buttons for directional control?

It does not seem like it will function like a D pad. A D pad is small enough to just roll your thumb over.

Vanguard has a button layout like that for shooting. It totally sucks.

I hope it works okay for you.

Hey bud, sorry for the late reply. I've been using the tool called SketchUp for the plans. It has a bit of a learning curve.
https://www.sketchup.com/en/plans-and-pricing/sketchup-free

They have a free online version that runs in your browser which I've linked above. You need to create an account through. However, they're last Windows version that was free is "Sketchup Make 2016" which is actually what I use. You'd have to find a download for it through. It might just be the 2016 pro version without a license code.

The cabinet is complete except for custom software that I've been slowly coding. I was hoping to have it done, but I'll work on posting pictures.

Building myself had saved me $1-2k versus buying one, and I have far better components inside as well as better material. I actually have a doc that has all of my costs which I can post as well. I'll work on getting final shots and posting here this weekend.

Morning everyone,

Hopefully somebody can help?

I have a mame cabinet running MameWah. I haven't used it for a while and when I turned it on it was complaining that the MB board time was not set and wouldn't boot into windows (running XP).

I tracked it down to the CMOS battery being dead, so I replaced that and set the time in the BIOS.

Historically it would always boot into my frontend (MameWah) and then off I go. Since the battery change it boots into MameWah for about 3 seconds and then black screen with nothing happening.

If I CTRL+ESC and run windows explorer I just get a blank desktop.

I'm not really sure what else to do. Any ideas are greatly appreciated.

Thanks for reading

Yes, I'm just telling you how to make groovymame synchronize properly in that specific case (also add "autosync 0" to mame.ini, btw).

Didn't tell you how to make groovymame pick that video mode since I thought you already knew how to do that.

Your OS will be reporting your custom resolution by 3 integer values, e.g. 640x480@110. So you have to force that mode through the resolution option, e.g. -resolution 640x480@110

That assumes the option -switchres is enabled. But enabling switchres requires you to define a monitor preset that is compatible with the mode you expect to set. This is by design to block unwanted frequencies. So it's not that simple. I'd need more information about the resolution you created.

Since you just mentioned "my graphics card" without a label I'm assuming it's not a supported AMD card, correct? If this is the case, you could just run baseline mame without the switchres complication.