
Gallium
Published
A couple times the game blackscreened while using Cookie Monster, your mileage may vary
The launcher has an option to use Gamepad controls and button prompts, but the option is greyed out, so I had to bind the buttons to corresponding keyboard inputs.
If you don't mind taking a little extra time to get the controls working, then this game plays absolutely fine with no other issues.
The camera gets placed within Chell's model such that you can still see it from inside, portals don't render their destination properly, and raytracing does not work properly.
Menus were navigable with the d-pad, but upon getting in-game, the entire gamepad ceased functioning until I set the Template to Keyboard and Mouse.
Just play the classic Portal.
When waking from sleep, all in-game audio no longer plays until the game is restarted.
Online works flawlessly, aside from needing to bind a button to Enter to utilize chat
Buggy mouse input, may be able to be worked around with a custom config.
Something is up with the mouse input. With the "Gamepad with Mouse Trackpad" preset, the cursor doesn't move unless the trackpad is clicked, and with the "Touchscreen Mouse Emulation" preset, the cursor doesn't move unless the trigger is pressed.
Game appears to work 100% perfect with the official controller configuration, SteamOS updates have fixed my earlier issues
To use the devs' official controller configuration, go to the v2.3 patch notes, click the "Official Configuration" link, then click "Apply Configuration" at the bottom.
All cutscenes do not display properly, instead displaying a color test pattern on both Proton 7.0-2 and Experimental.
Selecting the win8
setting in protontricks was required to fix a bug where the game gets stuck on the first loading screen
40 Hz refresh rate/frame limit, 10w TDP
I did encounter the same issue as most reporters where the in-game cursor will remain on screen during non-free roam segments, but it's a very minor issue.