[Resolved] Steam Controller in Assassin's creed origins on uplay. Help needed

[JonathonWatkins]

I received AC Origins when I bought a CPU and it's unfortunately on uplay. I also have a Steam Controller, which I've not used before. I've read the instructions, but am lost what I need to do to get the controller working well. I've added acroigins.exe and uplay, exe as non Steam games. By default, in Origins I can move about, fire a bow or swing a sword with the controller, but that seems to be it. I can't map any controller keys in Origins and don't know what keys I need to map to what in the Steam Big Picture setup. There doesn't seem to be a set of binding for the game. I haven't used a controller before, so don't know what the usual controls are.

Any suggestions on what I need to do to get the Steam controller working with the game? Much appreciated.

[Vepar]

If the overlay works then just apply a standard gamepad profile to the configuration and next time you start the game it should recognize it as an xinput device and no further configuration needed.

[JonathonWatkins]

I'm not familiar with using a controller, so don't know how it's meant to operate. There's a lot of actions shown on the xbox controller layout that I can't do using the steam controller. I'm pressing the buttons & switches, but not much is happening.

[Vepar]

Press the guide button when in game on the steam controller (the one with the steam logo on it). This should bring up the overlay. If it does it's ok, then it should work. Open up controller configuration. This will bring up the layout of what bindings it has. If you see stuff like "F" "Mouse" and stuff it's the keyboard layout and you don't want that.

When in configuration, look at the bottom of the screen, it should say "X" browse configurations or something like that. Press X on your steam controller and you'll open up a menu with recommended, templates, commmunity and personal configurations. Browse through templates and choose a controller template. This should then map all the normal xbox buttons to the steam controller. Press "X" on your controller again to apply the configuration.

Then, if the game doesn't immediately recognize it as a controller, restart the game and it should work.

Be sure the steam overlay is working (that you can bring it up with the guide button), otherwise the controller won't work.

[s1gns]

close origin or uplay, start ac over steam so that origins/uplay automatically start with the game. origins/uplay will have steam overlay.

[cammelspit]

https://steamcommunity.com/app/353370/discussions/0/1483235412199559556/

Already have a proper working fix for the game. In case you are curious, I will post an excerpt. Also, literally 2 posts down, this is why God made the search box and google, for future reference.

There is a 99% chance you are just using the basic desktop config for the SC instead of the Xinput controller config. The below fix should, in theory, fix that much for you.

They way ACO works it actually virtualizes itself in a custom formatted virtual machine for one of the two DRM schemes. My assumption is that, like every other AC game since the dawn of time, it initializes Xinput only in the first few seconds of the game loading and never again. The virtualization probably lengthens the initial setup process and loads the input devices, like the SC or other controllers, before the game itself can run because the VM needs that information to start with all that working. Steam uses the detection of the overlay, a rendered viewport from your video cards such as D3d, OpenGL, Vulkan, or whatever. So, if that delay between initializing input and enabling the renderer is fast enough Steam detects, enables the Xinput just in time for that VM so see it. Problem is, this VM scheme they are using causes delays and performance issues with even the beefiest 16 core monster PCs. So my thought was if the delay was too long, the game would have already detected and seen no Xinput device BEFORE Steam detected the renderer and enabled that. So as you might imagine, since AC games never redetect ever, that would have the effect of the overlay and Steam thinking Xinput is on normally but the game, having never detected Xinput, would just not be using Xinput mode. Seeing as my suggestion worked, that pretty much confirms my theory as correct.

In the overlay, select controller options. At the top, there is a box named something like 'allow desktop mode' UNCHECK that. This forces Steam to use the focus based game detection instead of the overlay hook. Though, I have never had any problems with any of my Uplay games, that all just work without any tinkering at all. The Uplay Overlay is designed to play well with Steam because they sell Uplay games on Steam so they need to get along. Anyways, this forces the config to switch, even if the hook, for one reason or another, is taking too long making the game miss the fact that a Xinput device is attached. I have to do this on some emulators and such so that is the whole reason they have it there.

[YogaPretzel]

Originally posted by Vepar:

Press the guide button when in game on the steam controller (the one with the steam logo on it). This should bring up the overlay. If it does it's ok, then it should work. Open up controller configuration. This will bring up the layout of what bindings it has. If you see stuff like "F" "Mouse" and stuff it's the keyboard layout and you don't want that.

When in configuration, look at the bottom of the screen, it should say "X" browse configurations or something like that. Press X on your steam controller and you'll open up a menu with recommended, templates, commmunity and personal configurations. Browse through templates and choose a controller template. This should then map all the normal xbox buttons to the steam controller. Press "X" on your controller again to apply the configuration.

Then, if the game doesn't immediately recognize it as a controller, restart the game and it should work.

Be sure the steam overlay is working (that you can bring it up with the guide button), otherwise the controller won't work.

Vepar...you saved my game! I spent hours and hours figuring it out. I used a community config that wasn't recognized in-game. Standard template is recognized. This fix together with GloSC enables me to go on this adventure!

[Vepar]

Originally posted by YogaPretzel:

Originally posted by Vepar:

Press the guide button when in game on the steam controller (the one with the steam logo on it). This should bring up the overlay. If it does it's ok, then it should work. Open up controller configuration. This will bring up the layout of what bindings it has. If you see stuff like "F" "Mouse" and stuff it's the keyboard layout and you don't want that.

When in configuration, look at the bottom of the screen, it should say "X" browse configurations or something like that. Press X on your steam controller and you'll open up a menu with recommended, templates, commmunity and personal configurations. Browse through templates and choose a controller template. This should then map all the normal xbox buttons to the steam controller. Press "X" on your controller again to apply the configuration.

Then, if the game doesn't immediately recognize it as a controller, restart the game and it should work.

Be sure the steam overlay is working (that you can bring it up with the guide button), otherwise the controller won't work.

Vepar...you saved my game! I spent hours and hours figuring it out. I used a community config that wasn't recognized in-game. Standard template is recognized. This fix together with GloSC enables me to go on this adventure!

Nice! Glad i could help.

[Torttelini]

Originally posted by Vepar:

Originally posted by YogaPretzel:

Vepar...you saved my game! I spent hours and hours figuring it out. I used a community config that wasn't recognized in-game. Standard template is recognized. This fix together with GloSC enables me to go on this adventure!

Nice! Glad i could help.

Could someone tell me what do you refer with GLoSC? I've already enabled a community configuration for the controller and works initially. I can see the "Press A button to start" instead of "Press an key". Sadly, when I try to press on the Continue Game button, the Steam Controller turns off... :(

[Vepar]

Originally posted by Torttelini:

Originally posted by Vepar:

Nice! Glad i could help.

Could someone tell me what do you refer with GLoSC? I've already enabled a community configuration for the controller and works initially. I can see the "Press A button to start" instead of "Press an key". Sadly, when I try to press on the Continue Game button, the Steam Controller turns off... :(

This: https://alia5.github.io/GloSC/

EDIT: As for SC turning off, maybe it's the batteries. Try using it wired. And if it still turns off, try switching between Steam beta and Steam stable clients. Then try either adding the game to library and configuring that way, or GloSC.