
Taleweaver
Published
Installed and played just over 2 hours. Haven't compared it, but seems 100% identical to the windows counterpart, based on video's.
Upon (attempting to) start, it wants to install Adobe air. That fails because it doesn't accept an administrator password for clearance...
To properly use the community layout, pick "advanced controls" in game (which is honestly how it should be played...it's not 'advanced' at all)
First time, it installs directx. But upon starting the game, it immediately quits itself without warning, info or anything.
Text for items is hard to read. Doable and hardly obligated to play, but noticeable
Runs and plays (seemingly) exactly as on windows. Sounds, music, levels...it's all there (I fear the bugs steam reviewers mentioned as well, but haven't seen any yet). The only thing missing is controllers: these are simply not found, no matter what I do.
Needs commands "PROTON_NO_D3D11=1 %command% PROTON_NO_ESYNC=1 %command%" (without parentheses) to work, and even then I found it sometimes crashing on me when quitting the game. Once ingame, though, all seems perfectly fine (also tested online connection).
Works perfectly out of the proverbial box
Game is currently in early access...but it most likely won't break anything in future builds...
Works perfectly (note: need to set fullscreen from options). Possibly aside the gamepad, but I've read that this is often a problem on windows as well.
Requires PROTON_USE_WINED3D11=1 %command% to run on my end. Seems to play fine, but haven't played it on windows.
Played it roughly 3-4 times...and then after that the mouse buttons simply refused to register, even after rebinding. Had to switch to "mouse only".
Not exactly 'significant', but the game hangs upon quitting.
Upon starting, you get two options: 'normal' and 'directX 9'. On normal, the characters are invisible. On DirectX 9, everything's okay.
I honestly didn't notice anything out of the ordinary. It immediately ran and showed no lags or (noticeable?) slowdowns whatsoever. Gamepad is also found and applied correctly. Played on proton 3.7.8.
Installed the app on mobile, connected to the (linux/server) PC. Everything seemed to work exactly as it should without slowdowns, though I'm not familiar with the game on windows.
Seemingly works fine. There might be a few texture glitches, but it might just be a weird art choice (I haven't played this on windows).
The line "PROTON_USE_WINED3D11=1 %command%" makes it start, but the game crashes even before loading a level.
Had to set the "PROTON_USE_WINED3D11=1 %command% option to make characters appear. The 3.16.3-beta version had equally invisible parts.
Your character can get pretty small on the screen when camera zooms out, but hardly worth noting. Overall great experience.
Crashes unless you put "PROTON_USE_WINED3D11=1 %command%" in the game's launch options. With it, everything seems fine (haven't extensively tested).
Plays mostly perfectly. Haven't encountered any sound or visual issues (note: version 3.2) 2 minor crashes in roughly 3 hours of playtime.
Had to use "PROTON_NO_D3D11=1 %command%", but works fine after that.
Works very decent: framerates are okay, everything looks as crisp as on windows and as far as I can tell everything works...with one exception: Music and all the voice-work (leaving only sound effects as audio). While this game certainly doesn't rely on it too much, it is certainly a miss compared to the windows version.
Works exactly as it should. In fact, I had to check whether or not this was native (then again: this isn't a graphically demanding game).
Since mentioned in other reviews, I checked both fullscreen and windowed: all seems fine now.
Starting shows a white screen, then after 2 seconds a black screen. Audio on the background, but nothing on screen.
No idea why valve marked this as unsupported: everything just worked perfectly as far as I can tell (about 2-3 hours on the deck now)
Haven't played much yet, but works perfectly thus far. No idea why it's labeled as unsupported...
Crashed upon starting (log:"err: D3D11CreateDevice: Failed to create a DXGI factory"). When adding "PROTON_USE_WINED3D11=1 %command" to the tweaks, all seemed perfect: PS4 controller, cloud save, gameplay. Setting up the controls is a bit fiddly, but is exactly the same in windows.
The 'no text' can be fixed by adding "PROTON_NO_D3D11=1 %command%" (no parentheses) to the game's launch options. I'm not sure if there are other issues (steam reviews mention it being worse than mobile, but haven't played this on windows).
The game starts, but has far more slowdowns than the original (or rather: on windows...this is a DOS-game). The ingame audio is often garbled as a result of this, but it's often that the game seemingly freezes for up to a minute at a time. The cutscenes (that I've seen) are fine, though. Just extremely low-resolution for current standards. :P
The initial ingame settings weren't great, but once mouse sensitivity and details were tuned down, it played perfectly. Very important: on proton 3.7-8, the game was very choppy and slow. All in all, a game that shows proton is making progress. :-)
I get the same mentioning that the video card drivers can't be found, and it is resorting to default (note: there's an ingame link to apparently fix it for linux, but it's leading nowhere). The game works, and can even continue cloud-saves. However: while it's not a quick reflexes game, mouse controls are severely slowed down compared to windows play.
I've tried all the tricks mentioned underneath, but I just can't get the sound working with just that. The rest seemingly works fine, though.
First time playing (after years and another, windows, computer), the cloud save didn't work. But after starting from scratch, everything was okay.
This game is a gem and is perfect for shorter gaming sessions.
Works exactly like on windows. Whether that's really a good thing is...a different matter. :P
Okay, I lie: I've played the native version. I'm not sure why it isn't checked in steam, but it downloaded and installed a linux-client on my end. Which worked flawlessly (okay: apart from an annoying bug of an upgrade mentioning that you can't get rid of).
Both of previous rapports are correct. If you start the game with a gamepad enabled, you'll get the "getDeviceState()" message that blocks everything. If you start it without it plugged in (so just play with keyboard), it works perfectly as it should.
Runs perfectly. Well...with the same caveat as on windows (as mentioned a bit below).
Game works and is certainly playable (controllers as well). However, some text is missing. This is most notable in the options menu, but character bios are invisible as well. The game also hangs upon trying to exit.
Black screen with current standard proton version, perfect with proton experimental (and FPS set at 60/unlimited). Played <1 hour.
I have 40 FPS by default, but this seems to slow the game down slightly. 60 is much smoother.
As mentioned by buckysrevenge: the game continually crashes when launched. To solve this, rename settings/settings.exe to something else, then create a "settings/settings.exe" shortcut that points to game.exe directly. This works flawlessly (played through the entire game)
After the workaround, everything works fine.
As mentioned below: you have to select the game's properties, go to 'betas' tab and opt into the 'public beta - legacy engine' program. Can't confirm whether or not this is linux/proton related.
Still: after choosing game or editor, it immediately quits.
Plays perfectly (including controller). Cloud-saves also OK.
Requires PROTON_NO_D3D11=1 %command% to work (on my end)
Everything works as well as on windows. Or lack thereof: I had enormous issues with the controls and the gamepad...which is exactly what every steam review complains about. :P
Has text boxes over (almost) all text. The actual game works fine, but it's pretty hard navigating to anything playable. :-\
As mentioned: add "-changedir" to the settings or the game will complain that you haven't done that. After that, everything's perfectly playable.