Dimitris Panokostas

@tonioni I'd be happy to help document the development environment, once I get everything working. Would you prefer a pull request about this?

@tonioni It should work with something like this: ``` { _T("KS ROM v3.2 (Walker)"), 3, 2, 43, 1, _T("Walker\0"), 524288, 248, 2, 1, ROMTYPE_KICK, 0, 0, NULL, 0x3EE21790, 0xE50DE168, 0xC4A9148F,...

I can confirm that with the above checksums, the ROM is detected and works.

@Realinferno The JIT implementation is different for 32-bit and 64-bit targets. So it's possible that there is a bug there somewhere, if it behaves differently between those two versions. However,...

I guess this is related to #620 , if we're talking about JIT compatibility.

Closing this as a duplicate

AutoCrop in a Custom event is a one-time trigger - meaning it will AutoCrop once, when you press the button, and no more. This is useful if the full auto-crop...

Just tested both events: - AutoCrop, mapped to R. Shoulder button on my PS4 controller = works fine - Quit, mapped to L. Shoulder button on my PS4 controller =...

@giantclambake I haven't really used DiskSwapper much, but the code is identical to that of WinUAE in the events being triggered. By looking at the code, it seems that it's...

Your assumption about the events is correct. You need to use the Previous/Next slot in combination with Insert current slot into drive DF0 (or any other drive). I just did...