It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
TuneLowPlaySlow: even watched a josh strife hays review and he mentions that they just worked with zero faffing around.
Probably works for him, but he glosses over a lot of the obvious flaws and pretends everything is nice and dandy, so he's not exactly a reliable source.
Hey, just want to add that my 8bitdo Ultimate 2.4G wireless AND 8bitdo Pro2 does not work with the first dino crisis. My old xbox360 PC controller does work though. Is this problem on the games code or is it in controllers? Please, dear gog devs, fix this.

EDIT: Correction, i got the 8bitdo Ultimate 2.4G to work almost "out of the box" flawlessly (just recently bought it) , i had to change B and Y button function. For some mysterious reason, 8bitdo controllers and menu button on B did not work at all. But on the wired xbox360 controller it did work. Very odd.
Post edited February 21, 2025 by knightofsidonia
avatar
knightofsidonia: Hey, just want to add that my 8bitdo Ultimate 2.4G wireless AND 8bitdo Pro2 does not work with the first dino crisis. My old xbox360 PC controller does work though. Is this problem on the games code or is it in controllers? Please, dear gog devs, fix this.

EDIT: Correction, i got the 8bitdo Ultimate 2.4G to work almost "out of the box" flawlessly (just recently bought it) , i had to change B and Y button function. For some mysterious reason, 8bitdo controllers and menu button on B did not work at all. But on the wired xbox360 controller it did work. Very odd.
Some of the 8bitdo controllers default to switch mode (as in nintendo switch) so have the A and B / X and Y buttons reversed. unless you switch to xinput mode
avatar
MattEagle_87: Xbox Elite 2

Is it just me or is the controller not working properly? You can't turn with the analog sticks while running straight ahead. So you can only either turn or walk. The D-pad works perfectly.
I have the same issue.
avatar
Wacnews: A problem I am having is that when my wireless controller goes to sleep it will not, or can not, reconnect. If I tab out of the game I can connect again but when I tab back into the game the connection immediately shuts down.
Same thing happened to me. Seem like its an issue with hot plugging the controller with the game open, as I dodged it when I turned the controller on first then started the game. Seems like it still has a predisposition to disconnecting itself though, so when that happens, you have to reset the game, as the issue persists if you don't.
Post edited June 21, 2025 by rimb_
avatar
MattEagle_87: Xbox Elite 2

Is it just me or is the controller not working properly? You can't turn with the analog sticks while running straight ahead. So you can only either turn or walk. The D-pad works perfectly.
avatar
lockhartdcs: I have the same issue.
I have the same issue in Dino Crisis 1 using a PlayStation 5 controller - left analog stick does not register the 'diagonal' direction and you can only move forward/back or turn left/right not both. The issue does not occur in Dino Crisis 2 using the same controller.

Trying Steam Input does not help and the controller doesn't work at all through that method.

Would be great to get a fix!
Post edited November 29, 2025 by hyperbola6
i have the problem, that my controllers (i tested multiple) are not reconnecting after they turn one time off while the game is running.
Try editing the "goginput.ini" file via Notepad then copy and paste the contents from here. Also make a backup file first just in case.

https://gist.github.com/ProjectXsent/20862484ccc8a3f260ecbd06e2869852
Post edited April 24, 2026 by ProjectXsent
I just had this same question today. I figured out this a while ago with some other titles where it was trickier to get the controller to activate. I'm using a PowerA XBONE controller, and it would work sometimes, and then most times not at all. The fix I have found is, use Galaxy (the client) and plug in your controller. It should glow like you hit the Tab key. It'll take a bit to kick in, but once it does, you can navigate. Go to the game, hit play, and the rest is history. I would not suggest touching the keyboard after or it will default back to that.

I do believe most default to keyboard on startup, and it's a 50/50 on whether or not the controller is recognized. Some games are different. However, this seems to work fine with DC2. I only ever use the keyboard to exit with a F9 doubletap.
Not sure if it'll work but I figured it wouldn't hurt to share.
avatar
PanzerSnake1964: I just had this same question today. I figured out this a while ago with some other titles where it was trickier to get the controller to activate. I'm using a PowerA XBONE controller, and it would work sometimes, and then most times not at all. The fix I have found is, use Galaxy (the client) and plug in your controller. It should glow like you hit the Tab key. It'll take a bit to kick in, but once it does, you can navigate. Go to the game, hit play, and the rest is history. I would not suggest touching the keyboard after or it will default back to that.

I do believe most default to keyboard on startup, and it's a 50/50 on whether or not the controller is recognized. Some games are different. However, this seems to work fine with DC2. I only ever use the keyboard to exit with a F9 doubletap.
Not sure if it'll work but I figured it wouldn't hurt to share.
Try to find your controller's "guid" and check if there's an entry that matches in the "goginput.ini". Something like the "XXXXXXXX-0000-0000-0000-504944564944"
avatar
PanzerSnake1964: I'm using a PowerA XBONE controller
I only found 3 PowerA GUIDs, not sure which one is yours but try adding these in the "goginput.ini" file

[powera_xbox_controller_a]
guid = 592A24C6-0000-0000-0000-504944564944
pad_zaxisplus = pad_button6
pad_zaxisminus = pad_button7
pad_button6 = pad_button8
pad_button7 = pad_button9
pad_button8 = pad_button10
pad_button9 = pad_button11

[powera_xbox_controller_b]
guid = 543A24C6-0000-0000-0000-504944564944
pad_zaxisplus = pad_button6
pad_zaxisminus = pad_button7
pad_button6 = pad_button8
pad_button7 = pad_button9
pad_button8 = pad_button10
pad_button9 = pad_button11

[powera_xbox_controller_c]
guid = 581A24C6-0000-0000-0000-504944564944
pad_zaxisplus = pad_button6
pad_zaxisminus = pad_button7
pad_button6 = pad_button8
pad_button7 = pad_button9
pad_button8 = pad_button10
pad_button9 = pad_button11
Post edited April 27, 2026 by ProjectXsent
Found a better option. Xidi SDL3 works for different kinds of controllers.