Jumbles
Published
CD key workaround did not work with Proton. Could only launch with Lutris using their install script
Used the Steam version install script from: https://lutris.net/games/assassins-creed-ii/
Enabled DXVK in runner options.
Had issues with "Steam | DXVK version" Lutris install script. Uplay installed but could not log in as no network connection detected. "Steam version" install script worked fine though:
- Installed "Steam version" install script from https://lutris.net/games/assassins-creed-ii/
- Launched game from Lutris and logged in with Steam and Uplay accounts (confirming CD key from Steam prompt)
- Game launched, then exited game for further tweaks
- Changed settings in Uplay account to remove the 'shift+f2' Uplay launcher toggle (as it did not toggle); also turned off all other unnecessary notifications and updates in Uplay
- Enabled DXVK in runner options for Lutris launcher for performance gain
- Launched again from Lutris, choosing 'remember me' in Uplay and set to launch in offline mode
- No other tweaks required, now launches straight from Lutris
Unfortunately for me the CD key workaround simply did not work on my setup, and as it was a bit of an ordeal to get working with Lutris, I could not recommend this for a typical user who just wants to click and play (with a minor tweak).
Ran "protontricks 15100 d3dcompiler_43" in terminal and launched game without PROTON_NO_D3D11=1 %command% for a decent performance gain ~10-20fps, but experienced a weird control bug and couldn't move mouse camera right on occasions. If you experience the same issue then try running with launch option PROTON_NO_D3D11=1 %command% and suffer the small performance loss while avoiding an irritating bug.
Used launch option PROTON_USE_WINED3D for best performance overall. Runs perfectly well but minor issues are: Can't Alt+Tab and play time not logged correctly in Steam (only shows as 1 minute).
Game did not launch so installed dotnet35 in wine prefix and set to WinXP in winecfg. After recommended tweaks, game still does not launch.
As others have reported, just run the below in terminal (pointing at your Steam library prefix for the game) to launch and play successfully:
WINEPREFIX=$HOME/steamapps/compatdata/35140/pfx winetricks mdx d3dx9 d3dcompiler_43 win10
Without the above (or equivalent using protontricks), the settings launcher will appear but will throw a shader compiler error on play.
If using Steam Controller, you may need to change config for right pad from Mouse Joystick to Joystick Camera. If not, the right pad control during the cryptographic sequencer challenges will just ping back to centre instead of holding where your thumb rests.
Crashed 4 or 5 times in the 13hr playthrough, forcing quit to desktop each time.
Summary
Just requires the above mentioned command running to launch the game successfully. Once done, it plays perfectly well. Didn't do all the challenges/collectables etc but completed the game without any issues aside from the odd crash.
Runs with following launch command for stability and performance: PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% -nointro
Full playthrough with no bugs or crashes encountered throughout. Minor stuttering at some doors in new areas but aside from that it runs perfectly.
Ran with launch options "PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command% -nointro", improved overall performance and stability, and fixed the issue with missing/low res textures.
Sometimes (after maybe 3-4 hours of play) the game would freeze, wouldn't Alt+F4 so I'd switch workspaces to kill BioshockHD.exe. Happened around 4 times total in a full playthrough.
Completed a full playthrough of the game c28hrs. Only a few complete freezes, but otherwise looks and runs great. From some cursory research, the texture issues of the remastered version do not seem to be platform specific and can be avoided with the given launch command listed here.
As with reports, run with launch command "PROTON_NO_ESYNC=1 %command% -nointro". Generally, good performance but frame drops/stuttering when entering new areas. No issues encountered so far.
Game did not launch on start. Had to force use of latest proton version (currently 4.11-12) in game properties in Steam:
Castle Crashers > Properties > General > Force the use of a specific Steam Play compatibility tool
Restarted Steam and then launched game successfully.
Only tested single player but seems to run perfectly so far.
Good performance, no tweaks required and no issues encountered.
Would occasionally lose screen resolution config (not playing it at my native 1080p) and drop to the lowest res. Toggling resolution in game options and reloading game resolved.
Installed on 2nd HDD with a long path to game directory; game would launch but load black screen on level start (audio only and could go back to main menu). Resolved by moving game directory to another drive with short file path (easily done through Steam via: Properties>Local Files>Move install folder). NB Not a Proton specific issue as experienced by Windows user: https://www.reddit.com/r/crashbandicoot/comments/8wrx1w/black_screen_bug_any_fixes/
Summary
Plays great. Completed CB1, started and completed some levels in both CB2 and CB3 without any issue but yet to finish either game. Quite demanding for lower spec devices but plays well with lower settings.
Gives unsupported GPU error upon launch (which can be ignored). Hangs after changing resolution in-game and requires restart but works fine after. 20-30fps on lowest settings at 720p, so not great performance considering how old the game is. Playable, but not great performance for an fps unless running above spec.
Runs well. Only renders grass in a very short radius around player though. Different drivers and in-game settings don't seem to resolve this. Otherwise, everything else appears to load and run fine so far.
Upgrading previous report. After 50+ hours I think it's safe to say DS2 essentially runs perfectly. Performance is great throughout, with rarely any big drops in fps. The only minor issue experienced is with grass-rendering, which is entirely inconsequential.
The game runs; lowest settings at 720p yields ~20-30fps with big drops every so often (although I don't meet recommended spec) and doesn't work with online mode as a result. Disabling Esync didn't do anything noticeable to improve performance. Can't Alt+Tab.
Runs perfectly but crashes on exit and have to kill process. Completed previously on wine without issue, so exit crash seems to be only present with proton.
Runs perfectly. Completed game previously on wine, looks to be same performance on proton.
Game runs ok, played through tutorial twice. Had to play lowest settings to get a close to playable frame rate with occasional stuttering. Wouldn't want to do full play through without beefier hardware well beyond min specs.
Poor performance but otherwise runs fine (resolution changes require .ini file changes in prefix)
Toggling fullscreen/windowed-fullscreen settings in-game would freeze/crash the game.
Sluggish performance given the minimum system specs. To optimise, I had to reduce pretty much all settings to low, turn anti-aliasing up to 1, and reduce resolution from 1080p (the option for which is disabled in-game). However, you can successfully change resolution in GameUserSettings.ini (along with other settings) which can be found here:
$Home/steamapps/compatdata/770390/pfx/drive_c/users/steamuser/Local Settings/Application Data/Draugen/Saved/Config/WindowsNoEditor
Just set the X and Y resolution variables in the ini accordingly, e.g.
ResolutionSizeX=1280
ResoultionSizeY=720
Black screen on launch but as others reported, just hit Escape (or B with Steam Controller) to continue as needed. Also freezes at end credits so you have to force quit.
Summary
Essentially runs out of the box (after hitting B or Escape) but any changes to resolution require tinkering with the GameUserSettings.ini as mentioned. Performance isn't particularly good unless resolution and other settings are reduced, but otherwise the game ran fine from start to finish using Steam Controller.
Plays perfectly from launch, 60fps at 1080p on High settings. No issues encountered and no tweaks required.
Disabled Esync to prevent crashes
Minor cosmetic issue, but skin mesh on characters sometimes appears cross-hatched (can't compare to Windows)
During first time setup, dotnet install fails (as installing dotnet35 on 64bit prefix). Game launches and plays fine, but this still happens on subsequent launches so adds about a minute to launch time. No real issue as plays fine.
Summary
Runs great. Completed main game and DLC without issue. Ran with following launch commands for stability and performance: PROTON_NO_ESYNC=1 gamemoderun %command% -nostartupmovies
Game does not launch. Installed dotnet45 with protontricks but Enderal Launcher fails to run.
Does not launch under any proton version. Able to run 'Enderal Launcher.exe' in terminal but no amount of changing settings (disabling ENB etc) will launch the game successfully. Looks like it needs a 32bit prefix to run; I managed this using Lutris to launch the Steam install of Enderal in a 32bit prefix and this got the 'Enderal Launcher.exe' running but still the same issue: launcher opens black window, Skyrim drums play, game crashes in <1sec.
Now launches and runs perfectly on Proton 5.0-5 without any tweaks
Performance: Almost comparable to Skyrim but I had to reduce to 720p to get a reliable framerate in open areas. No major stuttering/freezes/crashes.
Tweaks: None required. Didn't need to change bDoDepthOfField=0 in the EnderalPrefs.ini to see underwater either. (The Enderal Launcher has highly customizable settings should you wish to optimise for your hardware).
Issues: None encountered after around 4 hours play. Note that game time for Enderal is logged against Skyirm in Steam UI corresponding to the TESV.exe running (while it looks like Enderal play time will correspond to time spent in the EnderalLauncher.exe before launch)
Verdict: Near enough perfect. Play it now.
Still runs perfectly on launch after full play-through of 200+ hours
Previous report stands and have now completed a full play-through of around 200+ hours with no major problems, using both keyboard/mouse and Steam Controller.
No launch commands required and no issues with launcher (just disabled ENBoost and OneTweak for my system). Did experience crackling audio on occasion but this seemed to coincide with a high OS audio level so simply tweaked system and game levels to optimum...but based on other reports looks like the following launch command may fix 'PULSE_LATENCY_MSEC=90 %command%'
Near enough perfect, and beats Skyrim for stability, bugs (a distinct lack of), story, character development and gameplay.
Installs and launches but significant audio missing and save games broken
There appears to be no music at all (or only very occasionally). During some cut-scenes some of the dialogue and/or sound effects are missing.
Could save multiple times and overwrite previous saves, but attempting to load a save game only loads the first autosave of the game
- Upon launch, presents a warning stating system does not have enough RAM or virtual memory to run the game. Launches anyway without issue
- The opening cutscene (pre-game) throws a playback error 0x80040218 but a game can still be started
- Due to the missing audio and save game issue, the game is currently unplayable (unless you could complete in a single playthrough)
As with previous reports, did the mf-install workaround by running the following (replacing as necessary with the location of your steam folder and your proton version):
git clone https://github.com/z0z0z/mf-install.git
cd mf-install
export WINEPREFIX="/YourSteamFolder/steamapps/compatdata/683320/pfx"
export PROTON="/YourSteamFolder/steamapps/common/Proton 4.2"
./mf-install.sh -proton
Running on Ubuntu 18.04 with git installed.
Some crackling experienced during cutscenes
Proton-5.9-GE-8-ST GloriousEggroll
Default proton works fine but had some issues with stuttering and frame drops in certain areas. Using Proton Glorious Eggroll (5.9-GE-8-ST) had no issues whatsoever and runs perfectly smooth (after a few successful escape attempts over c30hrs play).
NB: At launch, selecting the Vulkan launch option crashes with "Vulkan was unable to detect a graphics device" despite a Vulkan capable GPU (though not CPU) with up to date drivers. However, selecting DirectX version (using Proton DXVK) works perfectly fine.
Recent update prevented Steam Controller input, but ran following launch options to resolve: /UseNativeGaInput=true /UseNativeGaInputNoControllers=false
Fully completed game (i.e. to end credits and beyond) using Steam Controller without issue (apart from recent update requiring controller fix above). Excellent game, excellent performance, highly recommended.
Had to run "PROTON_USE_WINED3D=1 PROTON_NO_ESYNC=1 %command%" to be able to start a new game without crashing to desktop. The main problem is persistent crashing at the bridge near the start, which occasionally produces an error with D3D "LowLevelFatalError" failing to load shaders. Tested without launch commands but can't start a new game without. Tested with different proton versions, and all fullscreen/windowed options and graphical presets but can't progress further (I'm below spec but so are others who have had more success).
Runs with Proton 5.0 and disabled esync, on a below spec device with low settings it still looks good and plays well
Audio in cut scenes is out of sync. Did not affect anything in terms of gameplay for me.
Fullscreen didn't work as launcher and panel still display, but Windowed Fullscreen works fine.
I'm below spec but the game runs smoothly with med textures and all else low, still looked surprisingly good and playable despite low fps. Very little stuttering encountered (only when exploring some new areas) and very smooth gameplay throughout. On any spec better than mine it should run fine.
Plays fine with PS4 & Steam controllers, but with mouse input the camera stutters severely; tried disabling v-sync and using borderless window mode re similar issue https://steamcommunity.com/app/102500/discussions/0/864979375655120478/ but no good. Controlling camera with keyboard works fine. (Rating Gold as this issue does not appear to be exclusive to running with Linux/proton). Had to change resolution in personal.ini in game folder.
Unlike others, didn't require any tweaks to get audio working. Performance fine at 720p. After 3hrs gameplay, only encountered the odd minor graphical quirks with fixed black rectangles appearing when moving in specific locations: https://steamcommunity.com/sharedfiles/filedetails/?id=1648234747
Ignore previous report of no audio tweak required, must have made the tweak after installing and forgot I made the change (see following https://github.com/ValveSoftware/Proton/issues/177). Played for 30+ hours, great performance generally apart from some minor audio distortion when some dialogues begin. The main issue is the semi-frequent "pure virtual function" crashes at seemingly random periods, could be 5 hours or 5 minutes until the next one. Otherwise, well worth playing and just remember to use quicksave regularly.
Despite enabling audio in launcher, no audio on first game start but fine on second start. Some fps drops throughout. (Completed game previously with wine and essentially the same performance running the game with proton so far).
Launches fine, auto-detects settings and resolution (or just edit render.cfg to set desired resolution). Running below spec on low settings benchmarks an ugly but just about playable 24fps (little/no drops). PS4 and Steam Controllers work apart from some issues where button prompts/hints are missing. Mouse and touchpad are detected on startup but not in-game, so no action or camera control (not linux/proton specific issue). Couldn't resolve this but some Windows users worked around by disabling Logitech Gaming Software: https://steamcommunity.com/app/356190/discussions/0/1698294337783003244/
When loading a new area the game stutters and would on occasion crash to desktop. Adding the launch command "PROTON_NO_ESYNC=1 %command%" prevented any further crashing after a full play through.
Crashes to desktop after loading new areas, but using no esync launch command prevents any further crashes (still stutters while loading)
The game seems quite graphically demanding for what it is. Minimum settings produced very poor performance for me, but custom settings with Visual Effects and Shadow Quality low and everything else medium/high produced a good performance overall.
Runs perfectly with Proton 5.0-10
I recently updated Proton to version 5.13-1 but the game did not launch using this version. Changing game properties in Steam to force use of Proton 5.0-10 launched the game successfully. Runs perfectly well with this version and no issues encountered so far.
Works perfectly
Full playthrough without issue. Played with Steam Controller. Runs like native.
Launches black window for a few seconds then crashes.
Plays well, no tweaks needed
Using Steam controller, the dash (X) button would sometimes be totally unresponsive for a few seconds. Killing your sprite (e.g. in a beam) seemed to resolve the problem immediately...otherwise, just keep trying to dash and it comes back. Haven't experienced on keyboard & mouse though.
Won't start at all. Followed tweaks from previous successful reports: updated to latest version of winetricks (20181203) installed dotnet4 with protontricks (albeit with errors re 64bit prefix) and tried Nvidia 410 drivers, none of which worked. Next step is to maybe install clean 32bit wine prefix with the above, but don't want to mess too much more with my system just for this one game.
Didn't launch previously but with proton 4.2-4 it now launches with no tweaks required (performance isn't great though with frequent frame drops even testing at 720p low settings). Also experiencing regular crashes (every 5-10 min) where the game freezes and StyxGame.exe has to be killed. Proton logs show opengl shader warnings e.g. "warning C7050: "vs_out[8]" might be used before being initialized". Disabled Steam overlay, reduced textures in game, tested with nvidia 415 and 418 drivers, no such issues with other proton games running 4.2-4, but the freezing persists. Surprising given the other recent reports have no issues, but for me it's sadly a nuisance to play.
Previously had issues installing Styx then stability issues playing. Glad to report it now installs and runs well with Proton 4.11 and D9VK. Add PROTON_USE_D9VK=1 %command% in launch options and performance and stability significantly improved. Still experiencing some frame drops here and there but nothing major.
Plays great with Proton 5.0
Some of the key bindings with the Steam Controller input were off, so just needed to remap keyboard bindings to match gamepad.
The native Linux version (as of this report) is no longer available on Steam, and had an issue sizing resolution correctly to my display, so that main title page and menus were not fully visible. Forcing use of Proton 5.0 resolved all issues and played great from start to finish without issue.
Owned and completed the game prior to removal of native Linux version from Steam by developers. Seems to run pretty much the same with Steam Play and proton (at least no better/worse than I recall from a couple of years ago i.e. a little sluggish in combat). By the sounds of it, more recent updates broke the old Linux port, so at least with proton those players may be able to finish their game, as it seems to run fine and no tweaks required.
Game is playable, not as good performance as first game (including old native version and with proton) as cut scenes seem ok but combat is more sluggish. Also experienced some scratchy audio issues; reducing Effects volume in game resolves this but you obviously lose the sound effects with it.
Completed without issue, no tweaks required. Performance is sluggish in combat compared to Windows (hence Silver rating) but otherwise runs fine, and it does mean you can at least continue your saga from the first game (TBS1 save location: ~/steamapps/compatdata/237990/pfx/drive_c/users/steamuser/Application Data/TheBannerSaga/Local Store/save)
Runs perfectly. Played through tutorial and found a match fine. Runs better than all the other TBS games.
Installed and played without tweaks. Graphically demanding but runs ok with only minor issues.
The game seems pretty graphically demanding but runs ok on med/low settings and still looks fine, not sure if this is the same for the Windows experience.
As mentioned in previous reports, closing out of the game results in a bug report prompt and you have to kill the council .exe to stop the game running in the background. Alt+F4 does the trick too though.
Runs perfectly out of the box with proton, no tweaks required (compared to wine requiring a few).
Minor issue: Changing resolution in the launcher from 1920x1080 (native) to 1600x900, results in unresponsive black screen upon launching the game, forcing a reboot. Changed resolution in the launcher back to native and game runs fine.
Runs perfectly out of the box
UE prerequisites fail to install on each launch. Either click cancel and ignore, or rename 'Redist' game folder (as per antimech report) to just click and play.
Great performance, runs perfectly so far (c2hrs gameplay). Not encountered any issues that others have reported with cut-scenes and broken autosaves etc. No tweaks required.
If crash to desktop after a minute or so in-game then disable Esync, though you may now experience screen flicker when transitioning menus. For full screen: enable 'Full Screen' and 'Exclusive Full Screen' in game launcher. Issue with HUD where screen fades very dark for 3 seconds after performing certain actions (loot/stealth); disable Health Meter to avoid some of these, though the fade always occurs when looting (despite disabling all HUD options/fades). Low settings Benchmark FPS: Min 12 Max 37 Avg 21. Actual gameplay FPS (prologue): Min 30 Max 60 Avg 45. Launch options: "PROTON_USE_WINED3D11=1 PROTON_NO_ESYNC=1 %command%"
Proton-5.9-GE-8-ST GloriousEggroll
- If using default Proton, disable Esync for stability and to launch game (tested with Proton 5.0-10), then to prevent black screen and allow video playback you'll need mf-install:
git clone https://github.com/z0z0z/mf-install.git
cd mf-install
export WINEPREFIX="/$Home/steamapps/compatdata/973760/pfx"
export PROTON="/$Home/steamapps/common/Proton 5.0"
./mf-install.sh -proton
- However, recommend Glorious Eggroll (https://github.com/GloriousEggroll/proton-ge-custom/releases) as Media Foundation baked in. Unpack to
$Home/.steam/root/compatibilitytools.d(create folder called 'compatibilitytools.d' first). You should then be able to launch, play cut scenes, start new game and continue (up to a point).
Steam cloud may not sync and local save wiped, so backup local save and prefix per @maberna instructions. Local save found here:
$Home/steamapps/compatdata/973760/pfx/drive_c/users/steamuser/AppData/LocalLow/CDProjektRed/Thronebreaker/SaveData
Frame rate dropped significantly after 30 min (to a sluggish 10fps in Gwent games). output_log.txt (same directory as SaveData) shows a memory leak error, which looks to be an unersolved Unity bug, confirmed by Unity Team as affecting performance (https://forum.unity.com/threads/jobs-lags-jobtempalloc-has-allocations-that-are-more-than-4-frames-old.513124/). Enabling V-sync may help but did nothing for me, I just reduce game settings to make it playable when it does drop.
Presented with black screen after loading campaign 3. TBClient-<date>.log (same directory as SaveData) is generated after each play and last line shows:
[Error][1][Campaign] FactDB Fact duplicate nr313_tokens_found exists
Looks to be same progression bug others have reported below. Can reproduce the error after any and all of the following:
- verifying game files in Steam
- re-installing
- rebuilding prefix
- disabling online mode in game & Steam Cloud
- loading old save and making different choices
Will test further if I come back to the game, but currently unable to progress any further as just black screen after loading campaign 3.
Summary
Needs constant tinkering, and with performance and progression issues, I can't recommend this to a regular Proton user. If you already own the game, don't mind tinkering, and are prepared you may not be able to finish it then give it a go.
Steam Controller: works fine but if controller turns off after inactivity, it's no longer recognised in-game after powering back on. (RT function also unresponsive in-game).
(See previous report)
(See previous report)
Occasionally froze and launched Unity bug tracker then crashed to desktop, output_log.txt indicated 'System out of memory' error, so possibly related to Unity memory leak bug (per previous report).
- Launch issues: game either does not launch, or launches and displays black screen after intro video(s)
- Progression issues: black screen encountered after load screen while loading next campaign stage
Resolution
Instead of using GE recommend Proton 5.0 with mf-install, as higher launch success rate and overcame progression issues. Steps taken below:
- Backed up old prefix
- Forced use of Proton 5.0 in Steam
- Launched game so Steam builds prefix
- Killed Thronebreaker process (as black screen due to MF requirement)
- copied save data to new prefix
- ran mf-install
- launched and continued game, progressing successfully into campaign 3 (etc)
Encountered same progression issue in some subsequent campaign transitions, but either ran above steps again, changed Windows version from 10 to 7 in prefix, or just relaunched and lucked out.
Summary
Still can't recommend this game to a regular proton user. If you're happy to tinker (and have patience to spare) then go for it and you may be able to complete the game.
Performance issues with animations but nothing to prevent playing
Animations, whether in combat or game menus drop frame rate from 60 to the tens. Other exploration and interaction in the game is fine though.
Seemingly esync related but followed the steps listed here to resolve: https://github.com/zfigura/wine/blob/esync/README.esync
The game takes 2-3 minutes to launch and animations cause big frame drops, although the sluggish animations (in combat at least) can make for some unintentional slo-mo style combat fun. It is generally fun and perfectly playable so far.
Seems ok overall
Some environmental textures may disappear when you crouch. Could well be the same on Windows though but unable to test this. Otherwise seems fine.
Scrolling through video options in the main menu seemed a bit temperamental when using trackpad/mousewheel so used keyboard for this instead.
Running at 720p with some fairly big frame drops (not specific to entering new environments/levels). DXVK launch command has no obvious effect on performance. It's playable but you'll probably want to hit the recommended requirements as opposed to minimum.
The game installs and launches fine without any tweaks but overall, performance isn't great with big frame drops throughout, so worth meeting recommended spec at the very least. The controls feel a bit sluggish but barring the other minor issues mentioned, it seems to run fine, and the performance/issues experienced may well reflect that of Windows anyway.
Proton-6.10-GE-1 GloriousEggroll
Proton-6.10-GE-1
Performance was very poor compared to similar turn-based combat games (e.g. XCOM 2 or Mechanicus). Lowering settings did little to improve performance either.
Launch success rate around 1 in 4. In prefix directory, the last entry in log.txt shows "Laucher waiting for exe to shut" after clicking 'Play' in game launcher. You can kill the Launcher.exe manually but the game does not launch so you have to: stop the game in Steam > click Play > wait for launcher to load > click Play in launcher. If it launches it'll launch in seconds, but if not, rinse repeat.
Default Proton (6.3-4) throws error with LauncherSettings.Config, prompting to delete and retry; doing so would open the game launcher on occasion but would crash on logos screen. When launched successfully with Proton GE, a full playthrough of demo was fine apart from missing some cutscene video (limitation of demo perhaps?) and would not exit to desktop (forcing Alt-Tab to then close). Coupled with performance and launcher issues mean it's a thumbs down.
Runs like native
Audio missing from the mini arcade games
When using Steam Controller, the Map/back button was not mapped so just had to set this manually by editing the corresponding button in the default DualShock 4 config.
If you're really into the mini arcade games then the missing audio might be an annoyance. Beyond that however, the game runs perfectly on Linux and seems to be well optimised in general.
