hap

more info here, when it was 1st brough up by Dwedit: https://forums.libretro.com/t/input-lag-compensation-to-compensate-for-games-internal-lag/15075

> That was the only driver to use green() in that way, looking at palette.h it is obvious that "green", "amber" and "white" are supposed to be the 3 major...

If it is as you say and 90% of the file is yours (refactors don't count), then yes source code style choice is yours. Also, good time to include yourself...

You mean this?: mame.exe leonardo -exp analyst -> Tab -> BIOS Selection -> works Oh, or it's only working for slot devices in that case.

This would make the emulated screen upside-down. If cocktail mode emulation is currently correct, then fixing it is simply a matter of setting m_flip_screen in zaxxon_v.cpp to bool(state);

@987123879113 OT if you already saw the notification then nevermind, I left a note here about an array out of bounds issue in one of your devices: https://github.com/mamedev/mame/pull/11558#issuecomment-2027037394

I won't say it's something that is enjoyed by everyone, but what you describe sounds as a feature.

> @galibert Stop that habit please. If you did this once per month, ok, but you do it too often At the least, say something when you post an @

I don't think swlists should be different from MAME romsets. Parent shortname + a/b/c for other revisions, or for example j/u for Japan/USA. Best avoid underscores, it makes it harder...

This is getting off-topic, but I haven't heard anyone say to avoid MAME for MSX specifically because of lack of TSX (on msx.org for example). openMSX is the go-to MSX...