search

rsn8887 / uae4all2

A fast and optimized Amiga Emulator for Vita and Switch
GNU General Public License v2.0
83 stars 10 forks source link

Case: Keyboard input is not recognized (Switch). #14

Closed ghost closed 5 years ago

rsn8887 commented 5 years ago

There's no debug version of the emulator.

Have you tried Google? I simply googled "winuae celtic legends" and the first result is the forum thread here, where Andreas said the following: "Moreover, this game appears to rely heavily on cycle-exact mode, as I had various odd issues without it."

So, I consider this a bug, but if it really needs cycle-exact, then it is probably in the "will-not-fix" category.

UAE4All2 doesn't have a cycle-exact mode and never will have. So the few games requiring cycle-exact will simply not work. It looks like Celtic Legends is one of them. Nebulus 2 is another one for example.

There might be some workaround if this is the only problematic screen in the game. You might get past the problematic screen in a different emulator, save state there, and then load the state into UAE4All2. The Amiga save state format (.asf) should be compatible between emulators. I have never tried this, but it might be interesting to see if it works.

rsn8887 commented 5 years ago

Thanks for the detailed report. I will look into it.

I just had success getting Virocop AGA to work (bitfield instruction fix).

Maybe this game can also be fixed.

rsn8887 commented 5 years ago

I tried loading a savestate from WinUAE 0.8.22 and UAE4Arm, but in both cases I just got gfx glitches, then a crash. Although the glitches did show some of the game screen. I had to manually rename the savestate from xxx.uss to xxx.adf.asf, where xxx is my Celtic Legends Disk 1 name.

I think the savestates from WinUAE and UAE4Arm, even very old versions, are not compatible with UAE4All2. There are a bunch of changes by TomB to the savestate code in UAE4All2.

rsn8887 commented 5 years ago

I found the problem with Celtic Legends and have a fixed version here. Thanks @Tonioni for all the help at eab.abime.net forums.

So this should be fixed in next release.