Skip to content
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

Open
20Phoenix opened this issue Jun 10, 2021 · 10 comments
Open

Controlling 32XCD games doesn't really work #161

20Phoenix opened this issue Jun 10, 2021 · 10 comments

Comments

@20Phoenix
Copy link

20Phoenix commented Jun 10, 2021

[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.

@bslenul
Copy link

bslenul commented Jun 11, 2021

I only have Corpse Killer so I can't say for the other games but changing Quick Menu > Options > Input device 2 to "None" fixed the issue. I'm guessing this is because if you have both ports used, it thinks you have a light gun plugged in port 1?

@20Phoenix
Copy link
Author

20Phoenix commented Jun 11, 2021

Aha, "none" input works, because otherwise waiting for lightgun command. Ok, I'll check this, thanks.
Anyway, in Supreme Warrior the reaction to pressing buttons is awefull and makes the game unplayable.
This was one of the really funny games seeing it as a kind of reaction test with nice fighting sequences.

@irixxxx
Copy link
Collaborator

irixxxx commented Jun 12, 2021

Can you give more details please?
Is the lag always the same? How much is it?
If you can compile a standalone linux build (or use one of the standalone builds from my releases) is it there as well, or is this happening only with libretro?

@20Phoenix
Copy link
Author

Setting input device 2 to none fixes nothing for me in Corpse Killer. What a pitty.
In Supreme Warrior it mostly doesn't react at all. Only sometimes randomly.
I tried it with RA on Win10 + XBOX. [I can't compile.]

@irixxxx
Copy link
Collaborator

irixxxx commented Dec 29, 2021

I disabled a controller hack for MCD and 32X. Could you try this again with a core having at least revision 688c90d please?

@irixxxx
Copy link
Collaborator

irixxxx commented Oct 12, 2022

Both games Supreme Warrior has a peculiar behaviour when used with 3 button controllers.
They use the Start button to switch the ABC buttons to secondary functions, and that's apparently true even in the menu. So, depending on how often you have hit the Start button before the game starts the ABC buttons are possibly set to the secondary functions which may look as if it's not working. Just hit Start once more to regain controls.
Or use a 6 button controller ;-)

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.

@irixxxx
Copy link
Collaborator

irixxxx commented Oct 15, 2022

@20Phoenix if you are still around could you please check if above tips are helping?

@niuus
Copy link

niuus commented Oct 25, 2022

I only have Corpse Killer so I can't say for the other games but changing Quick Menu > Options > Input device 2 to "None" fixed the issue. I'm guessing this is because if you have both ports used, it thinks you have a light gun plugged in port 1?

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.

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.

@irixxxx
Copy link
Collaborator

irixxxx commented Oct 25, 2022

If it crashes, is it reproducible with that save file, i.e. is it always happening?
Or do you mean same save file, crashes on and off when loading?

@irixxxx
Copy link
Collaborator

irixxxx commented Mar 26, 2024

@niuus is this still an issue with the latest nightly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants