VerifiedShow Details
Unknown
Rodando sem problemas. Testado utilizando o Proton estável (9.0-2). Depois de ajustar para meu PC, a performance ficou ótima.
All levels except the TF2 level perform well so long as you use the launch options provided in this report.
-force-d3d11 -screen-width 1920 -screen-height 1080
Launch options required.
Launch options do not pass along to the game to set the resolution.
Frame times in the Team Fortress 2 level are tolerable with Vsync off, horrendous with Vsync on.
Unavoidable crash on exit. You must use the Steam interface to quit the game.
Crashes sometimes with Vsync off after changing a lot of graphical settings.
The launch options are mandatory as we enter an era of high resolution monitors. The game simply will not boot if the options are missing on a high resolution monitor.
Game crashes when closing.
Unplayable with the vast majority of controllers, which is kind of a requirement for this game
Any controllers other than genuine Xbox controllers are guaranteed to drop inputs constantly, making them pretty much unusable (I used a Switch Pro Controller). Considering the fact that controller is recommended by the game and that the keyboard controls are vastly inferior in every single way, this is a pretty big issue in my opinion.
If you have a genuine Xbox controller, or simply prefer the keyboard controls, you won't have any issues with this game. The issue is, most people do not fall into that camp. Therefore, not recommended.
Game freezes and locks cursor activity until reboot
Even after killing the game and steam, cursor does not work on monitor game was on until a reboot.
Works at first, quickly crashes regardless of settings and tweaks
The game reliably freezes/crashes after about two minutes or so. While I can move my cursor and provide keyboard input, I am unable to click or properly interact using my mouse. If I kill the 'I Am Bread' process, the game disappears yet my cursor's appearance and functionality does not return to normal. It is only when I kill Steam entirely that these issues are fixed.
Works fine if you have a supported controller, which judging from other reviews is only official xbox controllers
Overall unplayable input drops/delays with both my logitech (both x-input and directinput options) and my off-brand 360 controller. Keyboard works fine, but even with rebinding some stuff keyboard is massively inferior to controller for this game
...as long as you use a genuine Xbox 360 Wired controller. Non-Xinput controllers cannot guarantee that it will not drop inputs.
4K displays will instantly crash the graphics driver. Launch with "-force-d3d11 -screen-width 1920 -screen-height 1080" in launch options to solve.
Any non-Xinput controller will drop input, and for this game consistent input is required on the bumper buttons. Dualshock 3 drops input on buttons, and I believe the same would happen with a Dualshock 4. The Xbox 360 Wired controller had zero issues.
Crashes on exit.
This is the only game that heavily favors Xinput over other input methods in my Library. No other game has more problems with non-Xinput controllers than this game.
Unknown(< 15 minutes with Proton)Dualshock 3 is still borked as of the new 4.11-3 controller configuration change. Requires Alt+F4 to sometimes exit the game without crashing. Best method to exit is still to kill the process in System Monitor/KSysGuard/etc...
Unknown(< 15 minutes with Proton)Unknown(< 15 minutes with Proton)Dualshock 3 controller support is better, but still borked. Game still crashes on exit.
Unknown(< 15 minutes with Proton)
The game itself runs very well, but there are some gamepad problems at the menu.
Unknown(< 15 minutes with Proton)Game launches with previous arguments, but using a PS3 Dualshock 3 regressed dramatically in controller usability. Game now also crashes on exit, both with Esync on and off. Yet to re-test with the Xbox 360 wired controller, but the Dualshock 3 is borked with this game.
Unknown(< 15 minutes with Proton)Unknown(< 15 minutes with Proton)Xbox 360 controller has no latency penalty, upgrading to Proton 4.2 with "-force-d3d11 -screen-width 1920 -screen-height 1080" had no regressions.
Unknown(< 15 minutes with Proton)
Game runs perfectly using launch options "-force-d3d11 -screen-width 1920 -screen-height 1080". Steam controller feels a tiny bit laggy but not an issue. I played through the tutorial with no problem.
Unknown(< 15 minutes with Proton)Proton prefix upgrade could cause issues with this game. "-force-d3d11" works again on Proton 3.16-7, however, launching the game 2 times in the same system session after setting the resolution in-game will cause GPU hangs if the "launch" resolution is too high. To solve this, make sure your launch options are: "-force-d3d11 -screen-width 1920 -screen-height 1080" (feel free to use a lower resolution for the launch options if you have a lower resolution monitor)
Unknown(< 15 minutes with Proton)Unknown(an hour with Proton)Controller Freaks out in the pause menu. Other than that the game runs fine.
Unknown(an hour with Proton)Unknown(< 15 minutes with Proton)Launching with no arguments gets the dreaded "GetThreadContext failed" error. Launching with Force DX9 works on the latest Protons and the FreeSync enabled NVIDIA beta driver. Controller axis are screwed up.
Unknown(< 15 minutes with Proton)
minor issues with using Xbox one controller in the menus
x360 controller does not works for me. Game works best in DX11 mode (use -force-d3d11 flag and select 1st option when launching in Steam). Does not works in openGL mode.
UnknownNo issues observed
UnknownUnknownWorks with Steam Controller. Doesn't run in OpenGL mode, otherwise it's running smoothly in DirectX mode. Menu navigation is sometimes messed up when using gamepad as I was unable to select certain buttons, but no problem with gameplay itself.
UnknownUnknownUnable to launch, gives generic crash dialog upon startup
Unknown
