SDL_GameControllerDB VS mame

Already planned to be in next update. As long as your controller is recognized by SDL2 and has controller mappings available (or you make your own), it will work.

Godot uses the SDL2 game controller database

Input fixes GameMaker's bugs. In addition to keyboard and mouse fixes, Input uses the engine-agnostic SDL2 remapping system for gamepads. Because SDL2 integrates community contributions made over many years, it's rare to find a device that Input doesn't cover.

The triggers are detected as buttons by default in some software (using d-input mode). Anything using the SDL2 community database shouldn't have this problem. I don't remember if RetroPie uses SDL2 or not. If not you might just need to edit a config file to rebind them to axes instead of buttons. I had to do this with Moonlight and linux Steam before the SDL database was updated.

# taken from line 1451 of https://github.com/gabomdq/SDL_GameControllerDB/blob/master/gamecontrollerdb.txt

I tried setting the SDL_GAMECONTROLLERCONFIG= from SDL game controller DB. Also tried remapping with jscal. Neither worked... and given that other games are recognizing it properly, I am puzzled.

Yes, there are many challenges in reverse engineering these classic games. This is a good example.

https://www.youtube.com/watch?v=objL2hGAEgU

Living in L.A. in the 90's, I remember Pack Mann in Pasadena had this one.

http://www.arcaderestoration.com/games/3330/Gals+Panic+II.as...

The ROM dump's been done but people seem to be stuck on the RLE encoding. It's hard to say what kind of wizardry is needed in this case.

https://github.com/mamedev/mame/issues/5816

There's a good start at it in the tree ( https://github.com/mamedev/mame/blob/master/src/mame/yamaha/... ) but it's missing the sound generation which is kind of the important part :-)

> As requested by users, you can finally use delta CHD files for clone systems and software items. This allows for major disk space savings in some cases when you have multiple versions of a system or software item.

FWIW, this is commit https://github.com/mamedev/mame/commit/d1172bf710f2a7b1777ed...

The GitHub Actions workflow bgfxshaders.yml will rebuild the shaders and then zip them up as an artefact. If you push your shader changes to GitHub and let the workflow run, you can grab the rebuilt shades from there.

Note that the process of getting the MSYS64/MinGW build environment set up is simple enough that we have automated CI builds for it on GitHub Actions without needing any custom actions of our own.

I assume they’re free vend because they’re MAME based?