GeeEl
Published
Runs out of the box, but not playable due to only ~4 FPS in game and some menus. Tried Proton 7.0-1 and Proton GE 7.2
4 FPS in game and some menus
Worked fine with 5.13-6 and Vive headset. Played full demo and slightly beyond the demo content in the paid game.
DLC "Archangel" solo game worked fine (intro story and brief combat), as did a single-player 'co-op" game.
On second run SteamVR glitched and I had to restart Steam to launch anything. Probably not a game issue.
Both sessions in combat were short - only a few minutes each. I'm a unskilled mech pilot. So few players online I couldn't find teammates in brief tests.
No display when I tried 720p or 828p. Brief black screen when starting benchmarking in 1080p, but display returned after a couple of seconds.
After trying installs with Proton 9, 5 and GE 8-24 I wiped the compatadata folder and GE 9-4 installed out of the box. About a 20 minute install after pressing "Play" on the first run. Without the ability to change resolution some text was unreadably small on lounge TV setup.
My regular MangoHUD was not displaying, so I don't think it was using the regular DXVK/Vulkan layer. May be using WineD3D. Performance seemed adequate though. It's a game from ten years ago.
My Dualsense controller (via Steam Input) worked, but had to be selected from the stock control configurations in settings (X360).
7.0-3 ran launcher but errored when starting the main game.
Specified Proton version 5.13.6, by default is Steam Play uses 3.7-8
Base game works out of the box with the default Proton of 3.7-8. Mods can be installed natively with Beataroni, but they don't seem to connect to the internet. Mod internet access worked directing SteamPlay to use Proton 5.13-6 (latest at the time).
Complete play through with Steam Controller. Played flawlessly
Sometimes would not terminate properly on exit
Worked well on 5.0-10 (my default), no extra settings. Played tutorial, a couple of matches against bots and an online game.
One slight stutter when doing an online game.
Played about an hour.
With stock Protons or older GE the game hangs after an introductory scene but choosing Skip Intro at game creation doesn't miss anything important. Introduction scenes play through properly with GE 8-4. Can run in DX12 with -dx12 launch option.
Although not necessary I ran it with gamescope for a touch of FSR:
gamemoderun gamescope -H 1080 -U -b -- %command%
Sometimes hangs at start when using a Steam Controller outside of Big Picture mode. Seemed fine from BPM or turning on controller afterwards.
Black screen on launch, but does have atmospheric music
Tried MF install, MF CAB install and Proton Experimental
Proton 5.13, 5.0, 4.11, 3.16 show a black screen with mouse pointer for a few seconds before the program closes.
Proton Experimental version as of 2020-01-20
Test pattern instead of a background at launch, but fine once playing tutorial
Very demanding on graphics card but mainly 60FPS with low-med graphic settings. Rare brief pauses.
Keyboard/mouse controls are as bad as in windows. Use a controller or try a input mod.
Even on Windows the optional multiplayer connectivity is rare without Wulf's Connectivity helper. That won't run on Linux.
DSFix seems to work fine without the DINPUT DLL override. Ran at 60FPS in 1080p. Used enhanced textures and unpacked for modding. D3D9.dll mods (DS PvP Watchdog and SweetFX) caused dips to ~12FPS but aren't required.
%command% -dx12
Cannot return to game after switching windows.
Just worked with Proton 9. Didn't get to multiplayer but it did browse user created tracks fine.
Worked well without tinkering.
Very low audio by default, probably not Proton related. Fine when audio was set to full volume in the game options.
Occasional momentary flickering, a couple of times in half an hour of play.
Runs with performance similar to on WIndows 10. Occasional drop in frame rate when moving into new areas. Mouse movement was restricted - switching to Windowed display and back to Fullscreen gave full mouse movement until changing windows. Crashed once in several hours of play.
Old game which ran fine at highest settings. Played about an hour.
Worked fine with default Proton, slight screen tearing (don't know if it happens under Windows).
Used Golle's suggestions. Worked with Proton Experimental has a test pattern instead of launch videos. GE7-26 plays videos without sound.
WINEDLLOVERRIDES="mscoree=n" %command%
Launched game for installation. Then used winetricks (via Lutris with a GE7 runner) to uninstal mono and install dotnet40. Protontricks should work as well.
Pre game company slash videos and title cinematic are missing audio.
Stock Proton 7 launches but gets stuck on the intro videos. GE and Experimental (with mono/dotnet40 tinkering) get into the game for play. I've played the first few maps over a few hours without issues, runs well with low CPU/GPU usage. I used GE7-26 as it's the last version that's working with my vkBasalt, but latest should work fine.
Once set up it works well. Make sure game is set to use a gamepad friendly option before starting VR (eg. Default Context).
Installed custom version of mono from https://github.com/redmcg/wine-mono/wiki#with-protontricks
After using VR mode resolution in non-VR mode is reset to windowed mode.
Most of the launcher doesn't work (glorified web page), but the important launch game options at the bottom do. Launcher usually does not close fully, needing "killall EDLanch.exe"
Played with PS4 and Steam controllers. Some VR mode with HTC Vive and non-VR fullscreen.
I did manual install of the custom mono version using Proton's wine. Use your own paths with the commands below (be very careful with the "rm -rf" or move/remove the Framework folders manually):
WINEPREFIX=path_to_Steam/steamapps/compatdata/359320/pfx path_to_Steam/steamapps/common/Proton\ 5.13/dist/bin/wine64 uninstaller
rm -rf path_to_Steam/steamapps/compatdata/359320/pfx/drive_c/windows/Microsoft.NET/Framework*
WINEPREFIX=path_to_Steam/steamapps/compatdata/359320/pfx path_to_Steam/steamapps/common/Proton\ 5.13/dist/bin/wine64 msiexec /i path_to/wine-mono-5.1.1.2_ED-x86.msi
Using PS5 Dualsense controller buttons were mismatched. I needed to switch to Legacy runtime 1.0 and enable Steam input and the Native version then worked perfectly.
Played through the tutorial and its "boss". Game ran very well.
Works well with stock Proton 9.0-2.
Had very poor performance and incorrect resolution when testing lower resolution fullscreen (eg. 720p) even when using FSR. Worked perfectly at 1080p.
Graphics surprisingly acceptable for a 2014 release.
Tried several stock and GE Proton versions, only GE Proton 7-37 launched. Denuvo DRM locks out the game for 24 hours after a few launch failures so testing is annoying. Ran a little slow - enabled FSR 1.0 on Balanced setting for consistent 1080p 60 FPS.
Steam install runs great out of the box with 7.0-4. ArenaNet client has worked well with Proton for years.
Steam install and old ArenaNet versions work. To play with an ArenaNet account from Steam requires a "-Provider Portal" setting, but that's non-standard and not specific to Proton.
Runs well "out of the box". Note: all command line options listed by people are optional.
Very occasional crashes after the last expansion, but a friend on Windows reports them too - possibly Australian internet connectivity.
By default Steam version is for Steam based accounts only. For an "old school" ArenaNet account Launch Options "%command% -provider Portal " is needed to use e-mail/password login.
Sound plays in intro dialogues with mf-install needed for the visuals.
Occasional noticeable low framerate, don't know if it's better on Windows.
Worked fine on 5.13.6, no extra settings required. Played the full Arcade mode game a couple of times - about 20 minutes.
Worked on 5.13-6 without additional tinkering. Played tutorial in VR mode (about 20 minutes) and then desktop mode (10 minutes).
Played with HTC Vive and Steam controller.
Worked out of the box in 1080p. Browsed menu, saw intro movie and played first two levels (7 minutes).
Native had some missing controller icons and mismatched buttons with PS5 controller. Proton 7.0-3 corrected the issues.
Played on Vive. Minor issues starting or changing "locations" in game a couple of times (requiring restart), but generally fun and relaxing.
Once in a few startups seemed to display only on monitor. Probably a SteamVR issue.
Current Proton Experimental launches okay with a brief test pattern instead of Curve company logo. Default (5.0-10) requires mf-install to avoid hanging on a black screen.
Doesn't seem to capture mouse in Windowed mode, stay in full screen.
Intro video won't skip (may be normal). WFC servers don't exist but it saves and resumes campaign fine.
PROTON_USE_WINED3D=1 %command%
Starts in low resolution and at full HD menus are unusable.
Slow motion animation at 10fps using 640x480 resolution
GE-Proton7-41 was the only version I could peruade the EA Desktop launcher to run with, which really constrains tinkering with the Unravel game itself. The game was unplayably slow with WineD3D and crashed with DXVK.
Worked well with default settings.
Changing fullscreen resolutions in graphics settings would switch to a borderless window (of selected resolution). Restarting seemed to use the new resolution. The default Borderless Fullscreen worked properly.
Worked well with stock 9 Proton and with FSR and GE9-4. Online leaderboard servers are offline, so it will complain about that. Steam forums comment that multiplayer is still working. Game looks gorgeous.
Proton 7.0.5. Worked fine with minor issues returning to game (common in fullscreen games without borderless window support).
When switching windows need to select the game again with alt-tab. Clicking the game preview in gnome doesn't work. Brief glitch where window went away and returned.
Native would not detect controller - probably still a good option if you're using keyboard.
