Steam Deck Discussion

To follow up with my prior post here's the exact error

It says valves testing indicates this title is playable with a yellow colour not green on steam deck. This game is functional on steam deck, but might require extra effort to interact with or configure.
It’s all green check marks but 1 yellow saying entering some text requires manually invoking the on-screen keyboard.
I also checked the steam store page but it’s not listed as 100% compatible.
Does Aurora only work with 100% compatible steam deck games then?

I should note I have seen people playing it on steam deck on videos

[Edited by Tacotuesday, 8/10/2023 1:09:04 PM]

Steamdeck hardware is extremely limited. It could be that trianer activation simply takes much longer on Steamdeck. The "verified for Steamdeck" just means if you can launch it and whether it has full controller support. Has nothing to do with Aurora.

Reddit and Steam forum are full of posts saying that this game runs awful on Steamdeck. Anyway have you tried using "-d3d12" launch option as the internet recommends? Link

Run the game fully without STL first, after you can get a successful boot then try STL. I have ran Remnant 2 with Aurora, its possible but that was when it first came out, I haven't tried since then since the fps isn't great on it.

[Edited by Jaz10, 8/10/2023 5:31:44 PM]

Got this running in Ubuntu 22.04 on several boxes.

Step 1 - install steam and run a game as normal
Step 2 - Download and unzip Aurora somewhere
Step 3 - Install pacstall (github.com/pacstall/pacstall) - copy the first command there :: sudo bash -c ...
Step 4 - Install Steam Tinker Launch (github.com/sonic2kk/steamtinkerlaunch/wiki/Installation) - scroll down to where it has the pacstall instructions (pacstall -I ...)
Step 5 - Follow the steam deck video until you get to the main STL screen (don't click game manu yet) - click download custom Proton (select GE-Proton-8.11).
Step 6 - continue the instructions in the video (set custom command/forks) don't worry about the wined3d setting (aurora won't work), set Proton to the GE-8.11 you set up from before.
Step 7 - after logging into aurora be sure to change settings (HW acceleration, process watching).
Step 8 - close everything down and relaunch the game as before

OPEN ISSUE:
* Works with a handful of games I tried it with. Search trainer, activate trainer (takes much longer than I'm used to). Eventually aurora can interact again, turn the options on an off.
* Baulders Gate 3 (and other trainers) - will crash aurora completely when you try to open them (not even getting to the activate trainer step). Wonder if tehr are any logs anywhere I can find to see why that hardcrashed on those, while others are working.

So, tracking down the Aurora bug with BG on ubuntu.

It's not proton and it's not Aurora. Opening up any other game, and selecting the BG trainer things work fine (aside from actually running the game).
I did notice that, no matter what I choose in Aurora when BG is running, it will crash (even just the notifications) {same settings, same proton - just with the BG client running, things die out).

I wonder if it has anything to do with DX vs VULCAN as the rendering engine. I'll see if I can find another VULCAN game in my steam library and see if the same behavior persists (e.g. divinity 2 or something) - or, let me see if I can force BG to run in DX on that proton instance....

So, after a bunch of back and forth - setting dx11, vulcan, everything not working (but knowing I can open the trainer in other instances). I started down the path of downloading older versions of proton - all to no avail.

Finally, through sheer luck I stumbled on the solution. When the steam tinker menu opens up, on the main menu there is an option to "Run command once". Select that, select the version of proton you want, and then select the Aurora executable.

Once there, make sure you do the (turn off HW acceleration and prempt bits), search out the trainer you want to run, and set it as favorite. Close Aurora, and for good measure Run command once one last time.

Next time you open steam tinker launcher let it do its thing, and this time when Aurora opens with the game, it shouldn't crash (e.g. doing this allows Aurora to run and do whatever backend it needs to before the game runs).

I did run into the same issue for divinity 2 (hence the whole vulcan vs dx11 things), as well as some of the games I initially reported not working. However, what I did discover, doing the run once bit, enabled Aurora to run with them after the fact (so if you have any previous trainers that didn't seem to run the suggestion is try the Run command once trick here - do the settings and whatnot - and let it do it's thing on the back side).

Happy LINUX (and Steam Deck) Cheating EVERYONE! (( And yay - no more Windows, and no BG3 crashing like Windows was giving me))