Journey (638230)

[flibitijibibo]

Whitelist Request

• Name of the game to be whitelisted: Journey
• Steam AppID of the game: 638230

System Information

• GPU: RX 580
• Driver/LLVM version: Mesa 20.2.0-0.3.20200610.15.dc8bffe, LLVM 10
• Distro version: Fedora 32
• Link to full system information report as Gist
• Proton version: 5.0-9

I confirm:

• that pressing the Play button in the Steam client is sufficient.
• that runtime config options are necessary to run the game.
• that no workarounds other than PROTON_* env variables are necessary.

Issues

• I haven't experienced any issues.
• There are no issues left open for this game.
• Although I consider the gaming experience equal to Windows there are remaining issues:

Completed a full playthrough on a single instance with no issues. Online companions worked as well! Settings were maxed with FXAA disabled and MSAA at 4x.

[sebastian-de]

Journey works fine for me in general, but I can't get my Steam controller to work with it.
While navigating the menu works fine with the controller, ingame the analog stick seems to be mapped to the camera, so I'm not able to move.

I tried several other different controller configurations and also tried to switch the Steam overlay on or of. None of this seems to make any difference.

I don't have a Windows installation anymore, so I can't test, if the Steam controller works with Journey under Windows.
On my installation the Steam controller works fine with other Proton games ("The Witness" for example).

[sebastian-de]

I tried Journey again after the last game update and the Steam controller works now. So, I can confirm a flawless Linux experience.

[KeyofBlueS]

The Dualsense controller is not functioning with this game, it is not detected at all, despite being listed as supported in the game info. I've attempted to use it both wired and via Bluetooth, with both Steam Input enabled and disabled, but to no avail. Interestingly, this same Dualsense controller works flawlessly with other games, whether they have native support or with Steam Input enabled.

Please advise on where I can offer assistance in further tracking down this issue. Thank you.

[KeyofBlueS]

After my previous attempts on Linux, I decided to give Windows a try this time. Surprisingly, on Windows, the only way the Dualsense controller seems to work is with Steam Input enabled. This discovery leads me to believe that there might be an issue with Steam Input specifically on Linux when it comes to Journey.

Could you please provide guidance on how I can assist further in pinpointing and resolving this issue within Journey on Linux? Any suggestions or steps you recommend would be greatly appreciated.

Thank you for your attention to this matter and best regards.

[KeyofBlueS]

It suddenly started working with Steam Input on Linux. It's weird because I didn't do anything different, it just started working out of the blue.
After collecting Steam System Information and Steam Runtime System Information, I ran the game with PROTON_LOG=1 %command%, then the controller worked as expected. Seems like things sorted themselves out.

Anyway, I've linked and attached the logs I collected during the troubleshooting process. Even though the controller's working fine now, maybe these could still come in handy for something down the line.

Steam System Information
Steam Runtime System Information
steam-638230.log