VerifiedShow Details
Playable
Overlays like the expanded view of a card when hovering often flicker or disappear
Fullscreen assumed the dimensions of the primary monitor and therefore parts of the interface are missing when playing on a second, smaller monitor
I could not wrap my head around the default gamepad controls. Switched to the "Intuitive Root" controls which let me use the left control stick for panning and the touchscreen for interacting. Your mileage may vary.
Crashes, or no window appearing.
PROTON_USE_WINED3D=1 %command%
Tried with and without PROTON_USE_WINED3D option set. Without nothing appeared on screen, with the option the game loaded into the main menu but crashed before I could start a game.
Had the same experience when using proton experimental.
Using Proton 6.3-8 works, and resolved my issues with 7.0-3 in a previous report
Game will stop proceeding when an ambush card is available to play during combat, forcing you to end the game before completion. This will most likely happen in every game, making it unplayable.
The game has no apparent issues at the start of gameplay, however I was unable to complete a single game due to the crashing issue described above. This is most likely a Linux/Proton problem as I was able to play a game successfully on a Windows machine.
Works fantastic right out of the gate! Bear in mind this is a mouse support only game so you will be using the touchpad which it defaults to automatically.
My previous report was wrong, the issues were because of the faulty cooling system! Great board game.
As I described below, fullsreen sometimes gets extremely sluggish in the menu until I press Alt+Tab
When Root is started in fullscreen mode sometimes it gets extremely slow in the menu. I don't even try to start the game. But after pressing Alt+Tab and seeing the list of applications started without even switching to any, Root suddenly returns to his senses and goes on as it should
Constant crashes with every available version of Proton
The game crushes randomly in three ways: it freezes by itself and its window can be closed from the OS; it freezes the OS interface but the logout-logon is possible; and it freezes completely all the system so that the only remaining solution is a hard reset. The third way is the most frequent. I added the PROTON_LOG=1 %command% string to the options but no log file appears at the presumed location after the crashes.
Hangs without loading with Proton 5.13-4. Works flawlessly on 5.0-10, at least in the tutorial games, but I haven't tried multiplayer yet.
I only had to enter "PROTON_USE_WINED3D=1 %command%" in Startup Options.
