GPD Win controls problem

[monoculo_jim]

So I tried to play this on the Win, a machine that's exceptionally suited for this kind of game and it runs really well but it doesn't seem to recognize the xinput gamepad present of the device.

I realize this could be hard to address by the devs as the Win isn't very widely known or available (it's a Win10 atom based portable made by GPD) but I'm curious if someone in my situation has found a workaround (that doesn't involve joy2key or similar).

[Adeon]

Unity should support xinput by default. My Logitech F310 works in xinput mode. Have you checked the control tab of the unity launcher? Scroll down to the xinput binds and try rebinding. I did not need to do this, but maybe the unusual nature of your controller did not find it properly.

[FOX n FORESTS]

@Adeon - Thank you for this, we could not have answered it any better, very much appreciated!

[monoculo_jim]

Yeah, tried rebinding, didn't work. Guess F'nF will remain the one title in my library that's unable to recognize the controller of my Win :(

Also since we're talking about the Input tab... bit of a mess actually. More than a hundred useless entries with descriptions like 'Joystick x analog y' before you get to 'Jump', 'pause', etc and no way that I can see to revert to defaults.

[ReddestDream]

What's funny I actually have both GPD Win models (Both 1 + 2) and an F310. I can confirm the F310 actually works on both GPD Win devices to control this game, but the built-in controls do not no matter what I do. Not sure what's up with this game. It detects that a controller is present (the intro says "Press A"), but none of the buttons do anything. When switched to Xinput mode, GPD Win controller is standard Xinput, no funny business. The only other game I've ever heard having similar issues with the GPD Wins' built-in controller is Wizards of Legend, but that game also has more broad controller issues.

Originally posted by monoculo_jim:

Also since we're talking about the Input tab... bit of a mess actually. More than a hundred useless entries with descriptions like 'Joystick x analog y' before you get to 'Jump', 'pause', etc and no way that I can see to revert to defaults.

That might actually be a hint. Maybe the game is picking up the controller fine, but for some reason it's assigning the wrong buttons or something.

[monoculo_jim]

Originally posted by ReddestDream:

That might actually be a hint. Maybe the game is picking up the controller fine, but for some reason it's assigning the wrong buttons or something.

I thought that too, but then it's the exact same mess in my desktop where I have a standard xbone controller (which thankfully works). Between this and the fact that the devs didn't even remember to add a 'Quit' option to the main menu I can't help but think the pc version wasn't very high in their priorities list...

[ReddestDream]

So, I managed to get the controls working on my GPD Win 2 by using Steam Big Picture Mode, configuring the GPD Win 2 as an Xbox controller, and enabling all overrides/force controller. Now it works.

[monoculo_jim]

Yeah, I managed that too, forgot to report here cause performance now seems pretty bad on the Win, scrolling isn't smooth at all, and I don't know if it's due to the Steam Big Picture layer or what. Guess I'll wait for such time as I get a Win 2 myself ;)

[Boreout [Aut]]

Originally posted by monoculo_jim:

Yeah, I managed that too, forgot to report here cause performance now seems pretty bad on the Win, scrolling isn't smooth at all, and I don't know if it's due to the Steam Big Picture layer or what. Guess I'll wait for such time as I get a Win 2 myself ;)

I don't own the game but bigPicMode is resourcehungry.
The gpdwin might have problems with that overlay running in the background.

Settings->ingame->use big pic overlay when using.....

i would uncheck that and steam will use the standard overlay old school overlay.
Your controllerconfigs should be still working.