Steamworks with the new input system

[Arcalise]

Hey there!

I’m using steamworks.NET with the new input system and having a little difficulty.

The mouse and keyboard work just fine.

Not sure if this intended or not. But upon initializing steamworks. My xbox one controller is no longer recognized within unity. No inputs will reach it until i close steam. I can get the game working by building it, opening the overlay and going to controller configurations then selecting to apply the generic gamepad. It will then work as intended. But within the editor nothing i do seems to work.

Any potential work arounds would be amazing. I really would just like to turn of steaminput all together as i believe unitys controller solutions work just fine!

[Hysparions]

Same problem here, it seems that steam input rebinds the controller, especially when connected by Bluetooth. This create a complete mess and unity Don’t recognize input properly

[timke]

Hey,

I’ve been investigation this issue and have an answer: this behavior is caused by using the default input configuration, which only supports Keyboard/Mouse.

Here’s the response from Valve:

The problem is that when you initialize the Steamworks API, Steam probably doesn’t know what kind of input you need. If you don’t have an appID, it’s giving you the desktop configuration, which defaults to disabling controller input or mapping it to keyboard and mouse. If you’re using steam_appid.txt to specify your appID and have 480 in there, you’re telling Steam that your application is SpaceWar, which actually has Steam Input mappings and controller input is redirected to Steam Input instead of XInput.

If you have a real Steam game, then you should make sure you’re specifying that appID in steam_appid.txt, and then go to the Steam Input settings on the partner page for your app and select the “Generic Gamepad” template.

If you’re just doing prototyping and don’t have a Steam appID yet, you can put 1456390 in steam_appid.txt, which is an appID set up for game controller testing.

For more detailed information, please see this Steamworks discussion thread.
There’s also a (resolved) Unity bug covering this issue.

[Hysparions]

Hey,
Thanks tim for the answer. This didn’t solve the issue, (I tried steam appID 1456390). In fact the dualshock doesn’t work even if steam and steam works ared disabled whenusing bluetooth.

[timke]

I’m sorry to hear that.

I’d recommend following up either on the Steamworks Github or maybe the Valve development forums. Basically, from my investigation, Steam literally hijacks XInput, and there’s really nothing Unity can do about it.

[Hysparions]

Yes that’s that, I have to use Rewired instead…

[ODINKONG]

I managed to get this working.
If you go to steam works and click your app Id then go to application > steam input and change the settings like this.

Then the PS4 controller uses unity’s input system.

[Sebastien_Morris]

@ODINKONG

I managed to get this working.
If you go to steam works and click your app Id then go to application > steam input and change the settings like this.

Then the PS4 controller uses unity’s input system.

How do you access that page

[jukibom]

@Sebastien_Morris

How do you access that page

https://partner.steamgames.com/apps/controller/[APPID]

where APPID is your unique numerical app id.

Alternatively, dashboard > “edit steamworks settings” or “app admin” > application tab > steam input

[kayusoft]

@ODINKONG

I managed to get this working.
If you go to steam works and click your app Id then go to application > steam input and change the settings like this.

Then the PS4 controller uses unity’s input system.

Hi ODINKONG.
These are already default settings on my steamworks account. I don’t understand which one i should change.
I have tried a few different settings and published. But it is still not working correctly for me.
When i try to use mouse, controller scheme changes to Gamepad instantly.
Is there any solution?

[SharpAccent]

So what if we are getting this error in the editor?