Game stuck on Controller layout?

[Reduxion]

Hey all, my game is stuck on the controller layout by default and I couldn't find it in the options to display keyboard layout. Does anyone know how to change that?

[SpaceRangerStarr]

I'm having this issue too. It automatticaly shows the controls for controller and doesnt show me how to do anything on keyboard. Also, my controller doesn't actually work with it....despite the fact that the game s labelled as having "full controller support". I get this occasionally because my bluetooth controller works with the switch, and some games don't bother making it compatible with it. I get it, it's not something that would matter enough to them cause I'm a huge minority here, but I also don't want to go spend money on a whole seperate controller just for one or two games, because usually if I can't play with controller I can play with keyboard....except this game makes it almost impossible.

[AtomikWrangler]

I'm having a related but reversed issue. I'm playing on a controller butt can only see keyboard options. The controller works, but I cant remap jump and interact on the controller cause I can only access keyboard options.

[tccoxon]

The game shows xbox controls if it detects that there is a controller attached. Please double-check any wired/wireless controllers that might be attached.

If you still have the issue, please locate and attach your logs (C:\Users\you\AppData\Roaming\CassetteBeasts\logs). When the game detects a controller it logs its name. So we should be able to find out what peripherals you have that are causing this.

[Cubiccube]

It detects my keyboard as a controller? It looks like maybe my controllers are detected but it won't let me use them.

Godot Engine v3.5.1.stable.custom_build.b54cb7426 - https://godotengine.org
OpenGL ES 3.0 Renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2
Async. shader compilation: OFF

CassetteBeasts (Godot 3.5.1 stable)
Type help to get more information about usage
Device 0 connected: XInput Gamepad __XINPUT_DEVICE__
Device 1 connected: XInput Gamepad __XINPUT_DEVICE__
Device 2 connected: Joystick (Razer Huntsman V2 Analog) 03000000321500006602000000000000
CassetteBeasts version 1.1.2
Compiled 1322 shader versions. Cache size: 1314
Compiled 17 shader versions. Cache size: 1322
Device 1 disconnected
Device 1 connected: XInput Gamepad __XINPUT_DEVICE__
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
at: ObjectDB::cleanup (core\object.cpp:2070) - ObjectDB instances leaked at exit (run with --verbose for details).
ERROR: Resources still in use at exit (run with --verbose for details).
at: ResourceCache::clear (core\resource.cpp:417) - Resources still in use at exit (run with --verbose for details).

[RaijinInu]

Having the same problem here, even when my controller isn't connected...
If only I could get everything back to keyboard input, that would fix the problem kind of for now, it just weird to me that when the game states it having "full controller Support" that the controller is the main factor messing up the possibility of having a normal experience...

Because of all the re-connecting, re-mapping and everything I've had to put in a lot of work.
Now, don't get me wrong I really want to play this game, but it appears something is making it impossible to do so.

If you'd ask me its because the local multiplayer has no on/off switch. because the keyboard & mouse will always be seen as the main "controller". Would be better if there was a way in the settings to turn this on/off. just so the game won't make it impossible to play, or maybe something similar to nintendo, where the console first asks the player what kind of controller to connect, something similar could be done by asking what to connect.

Again, would really love to play this game, but for some reason this problem is becoming annoyingly common, locking out those who wish to play the game.

[Weidengeist]

Unfortunately, I can confirm this issue. I want to play the game with the keyboard and the log says that it detects my mouse as a controller. It took some time to figure out the right controls to at least enter the settings menu during the game, turn the page to the controls section, and check the settings there. It displays the keyboard keys correctly, but the HUD only shows the controller bindings. It’s pretty sad and felt like a showstopper to me. :-/ I quit the game after only 20 minutes, because I simply don’t want to guess keys all the time while roaming the world. However, I won’t refund. I am sure that issue will be solved in the near future.

[Kuro]

Open up Device Manager, find "Human Interface Devices". Either disable or uninstall any joysticks you have there! hope these can answer u guys,spread love not war!!!

[Weidengeist]

So there has been a content update since the first reports of this issue (two months ago!) and it still hasn’t been fixed. It’s totally fine if it’s too complicated to figure out which peripherals trigger the controller layout, but please provide at least a menu option for the players to be able to change the displayed buttons on purpose. Why do you prioritise developing new content instead of fixing such basal bugs?

By the way, this is not a Steam issue. The game shows the same behaviour when being started from the installation directory and both on Windows and Linux.

[sklurb]

Also having an issue when I try to use a an official Xbox wireless controller, it still expects a keyboard input.

I've tried just launching Big Picture mode with my controller, but even though the game displays controller button prompts, it won't register any of my button presses. I've reset the controler layout to the game's official layout, I've shutdown and restarted Big Picture, turned off the controller and back (which created another issue of not recognizing that my controller was now on and kept prompting me to reconnect my controller).

How the hell do I play this game with a controller? :P

EDIT: When I started up for the first time with a controller, I could move the mouse pointer with the right thumbstick and select options by pressing down on the right thumbstick (as button A normally would in most default configs, and no other buttons/controls do anything). Changing the controller layout to both the game's official layout or a generic controller config hasn't affected this at all.

[Pook and Pie]

I had a similar issue with this game. I have an ASUS ROG Chakram X mouse that Cassette Beasts (and other games, like Doomblade, River City Girls 2, etc.) all think is the controller in port 1, and it only takes input from that controller, despite it not being the controller I want to use.

Even when that "controller" isn't connected to the system. On my PC, in order to play the game with a regular Xbox controller, I had to completely uninstall everything for my ASUS mouse.

Some other device on our systems are likely being picked up as the controller, and the developers didn't include a "choose your controller" option to specify which device you'd like to use, which is becoming more of an issue as more and more peripherals for PCs are interpreted by software as controllers.

I wound up just installing the game on my Steam Deck, though, because installing/uninstalling mouse software is kiiiiind of a pain in the ass.

[Messbot]

My vJoy virtual joystick was the problem for me - but I have to agree that the game shouldn't assume how I will be playing.

[Flan]

Hello, I just installed the game and got the same issue.
The problem is, I even don't got any controller!

Here's the log:
Godot Engine v3.5.1.stable.custom_build.bb8bd433c - https://godotengine.org
OpenGL ES 3.0 Renderer: Radeon RX 580 Series
Async. shader compilation: OFF

CassetteBeasts (Godot 3.5.1 stable)
Type help to get more information about usage
Device 0 connected: OBINS
AnnePro2 03000000d904000093a2000000000000
CassetteBeasts version 1.2.0
Compiled 1328 shader versions. Cache size: 1320
Compiled 17 shader versions. Cache size: 1328
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
at: ObjectDB::cleanup (core\object.cpp:2070) - ObjectDB instances leaked at exit (run with --verbose for details).
ERROR: Resources still in use at exit (run with --verbose for details).
at: ResourceCache::clear (core\resource.cpp:417) - Resources still in use at exit (run with --verbose for details).

Did somebody found a way to fix this?

[Weidengeist]

I have finally found the source of this issue and even a fix, the latter only for Linux, as it is my only available OS, but if you know why the controls layout is incorrect, you might be able to find a solution for Windows, in case that is your OS.

I use a mouse that registers – aside from its default mouse device – a joystick device in the system. The trick is blacklisting the devices initialized by plugging in the mouse except from those that actually control the mouse behaviour. If anybody is interested in details, I can provide step-by-step instructions (Linux only).