Jump to content

Running The Game On Ubuntu + Steam Play


69 replies to this topic

#61 ohartenstein23

    Member

  • PipPip
  • Little Helper
  • 20 posts

Posted 01 May 2019 - 10:15 AM

Updated the original post with links to the compile instructions. Thanks to everyone who's helped out figuring how to make this work, I appreciate it! Five months of not having to use a Windows partition just for MWO and it feels great.

Also not necessarily related to running on Ubuntu/Linux, but if you like to ALT+TAB frequently, running the game in windowed mode instead of fullscreen can help prevent some crashes or weirdness.

#62 Ch_R0me

    Member

  • PipPipPipPipPipPip
  • The Mercenary
  • The Mercenary
  • 278 posts
  • LocationPomeranian Voivodeship, PL

Posted 02 May 2019 - 01:18 AM

Did you done a run with newest Proton on Steam?

#63 ohartenstein23

    Member

  • PipPip
  • Little Helper
  • 20 posts

Posted 02 May 2019 - 11:36 AM

Only a cursory attempt. The Proton versions I have outside the local build will not properly initialize a wine prefix for MWO on my system so I haven't given them a more comprehensive test.

#64 Stormtux

    Rookie

  • 6 posts

Posted 11 May 2019 - 11:33 PM

View PostCh_R0me, on 02 May 2019 - 01:18 AM, said:

Did you done a run with newest Proton on Steam?

I am currently using proton compiled from the tag "proton_4.2" (last commit is fd5f3d0fba76906c280684dee8aae6f1f77bb11c in date May 1) and it works fine.
I even found the cause of the "crashes" I previously mentioned. The cause was me sometimes clicking the "Exit game" button instead of the "Quit match" when quitting before the end of the match Posted Image . Since this embarrassing discovery I never had a crash, the game is stable.

#65 Ch_R0me

    Member

  • PipPipPipPipPipPip
  • The Mercenary
  • The Mercenary
  • 278 posts
  • LocationPomeranian Voivodeship, PL

Posted 16 May 2019 - 01:16 AM

I'm thinking to actually compile a tkg-proton build, but IDK if contains MwO-related patches. If not - well, I know how to use "patch" command ;)

https://git.froggi.e...ster/proton-tkg

#66 Gagis

    Member

  • PipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • FP Veteran - Beta 1
  • 557 posts

Posted 16 May 2019 - 02:03 AM

View PostCh_R0me, on 16 May 2019 - 01:16 AM, said:

I'm thinking to actually compile a tkg-proton build, but IDK if contains MwO-related patches. If not - well, I know how to use "patch" command ;)

https://git.froggi.e...ster/proton-tkg
The documentation says "proton-tkg.cfg" and the mwo fix is one of the options there.

I run standalone wine-tkg-git and MWO performance has been really good for a while now.

#67 p5yc0runn3r

    Rookie

  • Big Brother
  • 2 posts

Posted 19 May 2019 - 11:45 AM

I have made MWO work without compiling anything. These are what I used:
  • OS: Pop!_OS 19.04
  • Latest Steam (to download game, IMPORTANT)
  • Latest Lutris (to run the game on WINE)
  • Gamemode (for performance)
  • Install Steam and download MWO.
  • Install Lutris and import MWO from steam.
  • Set up MWO to run on WINE with tkg-MWO-4.1 patch
  • Enable DXVK and ESYNC
  • Run Gamemode
  • Run MWO from Lutris.


#68 Gagis

    Member

  • PipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • FP Veteran - Beta 1
  • 557 posts

Posted 21 May 2019 - 08:08 AM

I'm finally happy with how my environment for MWO is set up.

Copying updates from Steam to a stand-alone installation since the Launcher has not worked for a few months. Can't get dotnet to work in such a messy environment.

Wine-tkg built from https://github.com/T...er/wine-tkg-git with MWO patch and other options resulting in a monster of a package name.

Quote

wine-tkg-staging-esync-dxvk-faudio-git-4.7.r0.g547e7c81-162-x86_64.pkg.tar.xz

dxvk includes the async patch

Then I launch the game using the following script:
#!/bin/bash
cd /home/gagis/.local/share/wineprefixes/mwo/drive_c/Program\ Files\ \(x86\)/Piranha\ Games/MechWarrior\ Online/
export WINEPREFIX=/home/gagis/.local/share/wineprefixes/mwo
 
export WINEDEBUG=-all
 
export WINEESYNC=1
 
export DXVK_ASYNC=1
export DXVK_STATE_CACHE=1
 
export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1
export __GL_SHADER_DISK_CACHE=1
export __GL_SHADER_DISK_CACHE_PATH=/home/gagis/.shadercache
export __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1
 
export STAGING_SHARED_MEMORY=1
 
wine ./Bin64/MWOClient.exe

Edited by Gagis, 21 May 2019 - 08:09 AM.


#69 Ch_R0me

    Member

  • PipPipPipPipPipPip
  • The Mercenary
  • The Mercenary
  • 278 posts
  • LocationPomeranian Voivodeship, PL

Posted 23 May 2019 - 04:13 AM

View PostGagis, on 16 May 2019 - 02:03 AM, said:

The documentation says "proton-tkg.cfg" and the mwo fix is one of the options there.

(...)

View PostGagis, on 21 May 2019 - 08:08 AM, said:

(..)

Then I launch the game using the following script:
#!/bin/bash
export WINEPREFIX=[$_MWO_LOCATION_STEAM_MODIFY_ME]
 
export WINEDEBUG=-all
 
export WINEESYNC=1
 
export DXVK_ASYNC=1
export DXVK_STATE_CACHE=1
 
export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1
export __GL_SHADER_DISK_CACHE=1
export __GL_SHADER_DISK_CACHE_PATH=/home/1000/.shadercache
export __GL_SHADER_DISK_CACHE_SKIP_CLEANUP=1
 
export STAGING_SHARED_MEMORY=1



Cool. I think for Proton, it would work that way, of course with the launch command removed (provided that modified Proton is compiled and installed):

/home/1000/abovescript %command%


in launch parameters in Steam.

Sources:
https://www.reddit.c...er_a_game_runs/
https://github.com/V...nux/issues/5740

Edited by Ch_R0me, 23 May 2019 - 04:16 AM.


#70 mclang

    Member

  • PipPipPip
  • Big Brother
  • Big Brother
  • 94 posts

Posted 07 June 2019 - 10:12 PM

View Postp5yc0runn3r, on 19 May 2019 - 11:45 AM, said:

I have made MWO work without compiling anything. These are what I used:
  • OS: Pop!_OS 19.04
  • Latest Steam (to download game, IMPORTANT)
  • Latest Lutris (to run the game on WINE)
  • Gamemode (for performance)
  • Install Steam and download MWO.
  • Install Lutris and import MWO from steam.
  • Set up MWO to run on WINE with tkg-MWO-4.1 patch
  • Enable DXVK and ESYNC
  • Run Gamemode
  • Run MWO from Lutris.


This worked for me also, except that I cannot use my Thrustmaster throttle stick as I am used to. The game crashes every time immediately when I try to map any button or axis of the throttle :(

In addition, minor issue is that in mechbay the mech is dark, but this doesn't affect gameplay.

Any idea what could cause the crash?

I'm using Solus with Lutris 0.5.2.1, tkg-mwo-4.5 and the newest nvidia drivers that are available (430.14) for me.

Edit: Here is my Lutris log about the crash:
https://paste.ubuntu.com/p/4Hrs5FZS7H/

Edited by mclang, 12 June 2019 - 10:37 AM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users