-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Controlling 32XCD games doesn't really work #161
Comments
I only have Corpse Killer so I can't say for the other games but changing |
Aha, "none" input works, because otherwise waiting for lightgun command. Ok, I'll check this, thanks. |
Can you give more details please? |
Setting input device 2 to none fixes nothing for me in Corpse Killer. What a pitty. |
I disabled a controller hack for MCD and 32X. Could you try this again with a core having at least revision 688c90d please? |
Corpse killer doesn't work at all if any controller is used in port 2. Disable port 2 to be able use the pad in port 1. Do this early enough in the Sega CD BIOS screen, since it's not working after the game has detected what looks like a lightgun to it in port 2. |
@20Phoenix if you are still around could you please check if above tips are helping? |
This workaround works for me. Though I can change it in real time while inside the game, no issues. Supreme Warrior inputs also work normally. The only issue that I had is that CD32X games could randomly stop working (between sessions) and crash dump the emulator when you try to load a game (CHD). Both tested using Picodrive Wii, nightly build October-23, and October-25. |
If it crashes, is it reproducible with that save file, i.e. is it always happening? |
@niuus is this still an issue with the latest nightly? |
[RA+cores up-to-date]
Hello.
I know there exist only six 32XCD games and they're not really good.
But hey, there're childhood memories 😁
Sadly the in-game controls don't seem to work.
Corpse Killer is not reacting to any command at all. Skipping intro or selecting menu is impossible.
Supreme Warrior is reacting, but somewhere between never and much too later, so it's unplayable.
Would be awesome to have that fixed one time.
The text was updated successfully, but these errors were encountered: