We have detected that cookies are not enabled on your browser. Please enable cookies to ensure the proper experience.
Results 1 to 13 of 13
  1. #1

    Post LOTRO on Linux: A Modern Guide (2019)

    LOTRO on Linux: A Modern Guide (2019)

    LOTRO on Linux has gotten much easier. Yes you're still going to do some command line typing, but the folks who make the WINE system for running Windows programs on Linux, WINEHQ, have come up with some predefined commands, so all you're doing is cut and paste. LOTRO runs fine in WINE 4.0, so you no longer need the old workarounds like PyLOTRO, hence the need for a new guide.

    I'm assuming you've already installed Ubuntu or Linux Mint on your computer, or had someone else do it for you. Other distributions are less helpful when it comes to running LOTRO, or games in general. I could go on for another page on the installation process, but there are other guides to installing Ubuntu and Linux Mint, some of which explain how you can install them on unused space on your hard drive and dual boot.

    These instructions assume you are starting with a vanilla installation of Ubuntu or Linux Mint.

    First, you need to have the newest version of WINE, v4.0. Ubuntu and Linux Mint are good distributions with up to date drivers, but for some weird reason they still ship with a very outdated version of WINE, v1.6, that will not run LOTRO at all. Fortunately, WINEHQ has all your commands ready to cut and paste, to install WINE 4.0 in your Linux computer.

    You will need to know the root (administrator) password for your Linux computer. If you installed Linux yourself, you probably know it already; if you didn't install Linux, talk to the person who installed Linux on your computer if they didn't tell you already.

    Also, for those who are unfamiliar with the command line, there is a command called 'sudo' which runs a single command as root and then quits. We'll be using sudo a lot, but although it does ask for your password initially, Linux temporarily holds onto your root authentication, so you can type several sudo commands in a row before Linux will ask for your password again.

    First, if you haven't done it already, install the 32bit architecture. We'll be installing a 64bit WINE 4.0 here, but 64bit WINE needs some files from 32bit WINE to run 32bit applications, and until SSG gives us that great new 64bit client, you'll be running their 32bit client. These files work with all versions of WINE, so we can do it first.

    This is your command to install 32bit architecture:

    Code:
    sudo dpkg --add-architecture i386
    Now we add the WINEHQ Repository Key, the way in which you get secure transfers between your computer and the WINEHQ software repositories. Two commands:

    Code:
    wget -nc https://dl.winehq.org/wine-builds/winehq.key
    Code:
    sudo apt-key add winehq.key
    NOTE: wget downloads files directly into the directory in which you are currently sitting. No need to change directories to the Downloads folder first with wget.

    For the next section, use the command associated with your version of Ubuntu or Linux Mint (Linux Mint is based on Ubuntu). Remember to include the little ' marks, they're important for the Linux command line commands. Only use one command, not all four.

    Ubuntu 18.10

    Code:
    sudo apt-add-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ cosmic main'
    Ubuntu 18.04
    Linux Mint 19.x


    Code:
    sudo apt-add-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ bionic main'
    Ubuntu 16.04
    Linux Mint 18.x


    Code:
    sudo apt-add-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ xenial main'
    Ubuntu 14.04
    Linux Mint 17.x


    Code:
    sudo apt-add-repository 'deb https://dl.winehq.org/wine-builds/ubuntu/ trusty main'
    Now we tell Linux to update its list of available software sources.

    Code:
    sudo apt update
    NOTE: What we just did here is update Linux's internal updates system too. Now when you run updates in Linux, WINE 4.0 is the default and will be updated normally, instead of the outdated WINE 1.6 that installed with your original installation. You won't need to know any of this for the updating process, but it's good to know that you won't have to do these previous steps again.

    And now a word on Linux development of software. Linux developers generally maintain three stages of software for each software application: stable, development, and staging. As you may have guessed from the word stable, the other two are increasingly less tested. Fortunately, WINE 4.0 is the current (2019-03-13) stable version of WINE, so you don't have to venture into the wild west of software development just to run LOTRO in Linux.

    So this is the only command you need to run:

    Code:
    sudo apt install --install-recommends winehq-stable
    If everything installs without complaints, skip the next step

    The apt program may complain about missing dependencies, or software packages needed to run WINE. Each package name will be listed onscreen, so you can just type (replacing <package-name> with the package name>) to install the software package(s) WINE needs:

    Code:
    sudo apt install <package-name>
    Once the dependencies are installed, or if you didn't need to install any dependencies, you've got one more step before you can begin installing (or copying over from another machine) the LOTRO files. Get into the command line and type:

    Code:
    winecfg
    The winecfg application will create a special directory called .wine in your Home directory. This is the directory into which WINE will install any Windows applications, and where you will need to create directories to install LOTRO if you are copying files from an existing installation. In addition, winecfg will most likely find that you have not yet installed a Gecko and a Mono package, so say yes and install these packages. Gecko is a package containing software for running web browsers, and Mono is the open source version of the Microsoft .NET platform.

    UPDATE 2019-04-09: Sometimes GECKO fails to install properly, which is indicated by the window asking if you want to install it popping up again and again. If this happens, click Cancel on the install window, allow winecfg to finish, then use your favorite browser to download the gecko package manually (link). Scroll to the bottom of the list and download wine_gecko-2.47-x86_64.msi to your home directory, this is the only file you will need, the rest are for versions of WINE older than 1.9.2, and we're using WINE 4.0. Back into the command line, cut and paste this command:

    Code:
    wine msiexec /i wine_gecko-2.47-x86_64.msi
    This is the command used to install any Microsoft MSI installer file in WINE, in case you are really getting into learning Linux.

    While the winecfg window is open, click on the Applications tab and note, at the bottom of the window, that Windows XP is the default version of Windows used by WINE. That pulldown menu includes a bunch of other versions of Windows which you will probably not use, but you may end up coming back here later to change this to Windows 7. Windows XP works fine for now, so no need to change the setting.

    Now we'll install the extra files WINE needs to run LOTRO, using a application from WINEHQ called winetricks. First, from the command line, install winetricks:

    Code:
    wget http://winetricks.org/winetricks
    If you're using some sort of built in Intel graphics, the next command installs everything you need.

    Code:
    bash ./winetricks vcrun200{3,5,8} d3dx9 corefonts
    If you're using a NVidia video card, run this instead:

    Code:
    bash ./winetricks vcrun200{3,5,8} d3dx9 corefonts physx
    Just answer Yes or OK if asked, these are all needed to run LOTRO in Linux.

    If you're comfortable with the command line, you can probably skip this next part. If you aren't, and you use the file manager/browser in Linux, directories in Linux which start with a period, like .wine, are hidden in the normal file manager view. You'll need to click on View in the top file manager window, then select "Show Hidden Files". Or just press Ctrl+H as the menu shows. This will reveal all your other directories that begin with a period, in addition to .wine, but you only need to concern yourself with .wine for now.

    Now you can see the file folder in which all Windows software will be installed. The subdirectory "drive_c" is where everything goes, and if you are copying files from an existing Windows install, you may have to create a directory called "Program Files (x86)" because we still don't have that amazing 64bit client. It will be easier to create this new directory in the file manager, the Linux command line needs some simple but arcane commands to put spaces and parentheses into filenames.

    If you run the LOTRO installer in WINE, the Program Files (x86) folder will be created for you.

    Running the LOTRO Installer in WINE:

    If you downloaded the LOTRO installer using lotro.com, most likely the file was downloaded into your Downloads folder. Chances are it will have downloaded somewhere else only if you change this setting in your browser.

    Go into the folder with the installer:

    Code:
    cd Downloads
    Then type:

    Code:
    wine lotrolive.exe
    Select Express installation. This will speed things up and WINE needs to find the files in the place it likes to find them.

    Now here is the point where problems may occur. If the installer stops functioning or crashes, just run the installer again. It shouldn't take more than two tries to get to the point where the massive download begins, and any problems installing should be over by then.

    Once LOTRO finishes installing, you have two more changes to do. LOTRO will have created two icons on your desktop, one with the Ring on it. Right click on this Ring icon, and select, at the bottom of the dropdown menu, Properties. In the center of this new window, you should see a long command line command. Click on this command line once, then use the arrow keys to scroll all the way to the end. SSG only uses LotroLauncher.exe now, not TurbineInvoker, and all TurbineInvoker does is run LotroLauncher.exe. Change TurbineInvoker.exe to LotroLauncher.exe, and you're all set. We're making this change to speed up running LOTRO, and to allow you to more easily use command line options later, as TurbineInvoker ignores all command line options.

    Remember that Linux is case sensitive, so to Linux, LotroLauncher and lotrolauncher are two different filenames.

    UPDATE 2019-03-15: The second change you will need to make to be able to use the LOTRO Store (if you don't use the store, skip this step, you're done) is that you will have to run the LOTRO Awesomium client. Even with WINE 4.0 the regular client will not load the LOTRO store. You don't have to change the shortcut, just the LotroLauncher config file, and you don't have to go back into the command line again (if you like the command line, use your favorite Linux text editor for the following).

    From the Ubuntu/Linux Mint file browser/manager, go to View and "Show Hidden Files", then go into .wine, then drive_c, then Program Files (x86), then StandingStoneGames, then The Lord of the Rings Online. Right click on lotro.launcherconfig, and select Copy, then right click anywhere in the file window and select Paste (makes a backup copy before editing), then Rename the (copy) and add .old to the end (or don't, see below). Now go back to the original lotro.launcherconfig, right click on it again, and select one of the Open With options, either Text Editor or Notepad (doesn't matter which one you choose). The configuration file will contain an appSettings section. As the last line in this section, cut and paste the following line:

    Code:
    <add authoritative="true" key="GameClient.WIN32.Filename" value="lotroclient_awesomium.exe" />
    Now save the config file.

    Since LotroLauncher controls everything from that configuration file, it is possible to have LotroLauncher load the backup copy of the original configuration file (the importance of backups!) and run the regular client as well from the same shortcut link. This means that you could have the full benefits of the main client most of the time, and then briefly switch clients to run the Store. To do this, rename the edited lotro.launcherconfig to lotro-awesomium.launcherconfig, and then rename the backup to lotro.launcherconfig. When you next run LOTRO, WINE will ask you for a config file, and select the configuration file for the client you want to run for that session.

    There you have it, LOTRO on Linux.

    UPDATE: Inside the LOTRO Client, be sure to change your Options in Graphics -> Display to Screen Mode = Full Screen (Windowed).
    Last edited by Webgiant; Apr 09 2019 at 10:39 AM.

  2. #2
    Join Date
    Mar 2007
    Posts
    122
    Great walk-through! I got through the installation on my own using wine before I saw this, but I couldn't get the Store to work.

    One question, is there a reason to use the original config file? You mention the "full benefits of the main client". Does the edited config cause problems with normal play?

    Thanks for posting the guide.
    Neolythic : Iron Hills Dwarf Guardian (armorer) Arkenstone (Elendilmir)
    Niph : Female Hobbit Hunter (Yeoman) Arkenstone (Elendilmir)
    Sarabeth : Female Hobbit Burglar of Breeland (explorer) Arkenstone (Elendilmir)
    Trixie : Female Minstrel (Explorer) Crickhollow

  3. #3
    Quote Originally Posted by neolythic View Post
    Great walk-through! I got through the installation on my own using wine before I saw this, but I couldn't get the Store to work.

    One question, is there a reason to use the original config file? You mention the "full benefits of the main client". Does the edited config cause problems with normal play?

    Thanks for posting the guide.
    The store doesn't work with the main client. This appears to be a problem with the client, as using full Windows 7 emulation (the store worked in Windows 7) still does not make the store work. The workaround is to use the awesomium client loaded by the edited config file when you want to use the store.

    The default config file allows you to use the main client, which seems to work better and allows for better graphics, even though the store is inaccessible.

    I have confirmed that the awesomium client allows you to use the Store in Linux WINE 4.0. So its just a matter of switching clients when you want to use the Store, then back again for the better graphics.

  4. #4
    Hello and thanks for the great guide!

    I was having hard time playing lotro on my Thinkpad and Linux Mint with Play on Linux. One day it was working but on the other Play on Linux was crashing constantly. After lots of tweaking purged everything in frustration.
    Then I saw your guide and tried it with Wine only and now it's working, yey!

    Unfortunately I still have a problem and I am looking for help. I have 2 external monitors connected to my laptop and I want lotro to be played on one of them. When I was using Play on Linux the launcher was starting, but when I dragged it to another monitor I couldn't click on anything. That was before Play on Linux started to crash altogether and I removed it.

    Now with Wine only, Launcher starts, I can log and after server choice the screen goes to either black or the picture behind it. The only way to make the game load properly is if I disconect the external monitors. Which is very sad, because I want to play the game on one of them.
    Any idea how this could be fixed?

  5. #5
    Join Date
    Oct 2016
    Posts
    13
    Quote Originally Posted by Harwald View Post
    Hello and thanks for the great guide!

    I was having hard time playing lotro on my Thinkpad and Linux Mint with Play on Linux. One day it was working but on the other Play on Linux was crashing constantly. After lots of tweaking purged everything in frustration.
    Then I saw your guide and tried it with Wine only and now it's working, yey!

    Unfortunately I still have a problem and I am looking for help. I have 2 external monitors connected to my laptop and I want lotro to be played on one of them. When I was using Play on Linux the launcher was starting, but when I dragged it to another monitor I couldn't click on anything. That was before Play on Linux started to crash altogether and I removed it.

    Now with Wine only, Launcher starts, I can log and after server choice the screen goes to either black or the picture behind it. The only way to make the game load properly is if I disconect the external monitors. Which is very sad, because I want to play the game on one of them.
    Any idea how this could be fixed?
    I would attempt to run the game in borderless fullscreen. I often find that fullscreen mode in games often plays some havoc with many desktop environments.

  6. #6
    Quote Originally Posted by Thymir View Post
    I would attempt to run the game in borderless fullscreen. I often find that fullscreen mode in games often plays some havoc with many desktop environments.
    Thank you, but I even try to run it windowed... no luck

  7. #7
    Join Date
    Apr 2007
    Location
    Seattle, WA
    Posts
    62
    First, Webgiant thanks for putting this guide together.

    I'm having a problem myself, and don't really know how to fix it. Everything seemed to install without any major errors. However, when I use the lnk to launch LotRO it does the updates, lets me put in my username and password and select my world. The launcher closes and I get; Game Error 105 Could not initialize Direct3D. Please ensure that DirectX 9.0c [Dec 2005] or hisher is installed [105].

    How do I satisfy the program?

  8. #8
    Quote Originally Posted by SatinKnight View Post
    First, Webgiant thanks for putting this guide together.

    I'm having a problem myself, and don't really know how to fix it. Everything seemed to install without any major errors. However, when I use the lnk to launch LotRO it does the updates, lets me put in my username and password and select my world. The launcher closes and I get; Game Error 105 Could not initialize Direct3D. Please ensure that DirectX 9.0c [Dec 2005] or hisher is installed [105].

    How do I satisfy the program?
    Are you sure you have executed all the steps, because there is one step where one is asked to install DirectX? It looks to me you are having problems with DirectX.

  9. #9
    Join Date
    Apr 2007
    Location
    Seattle, WA
    Posts
    62
    Quote Originally Posted by Harwald View Post
    Are you sure you have executed all the steps, because there is one step where one is asked to install DirectX? It looks to me you are having problems with DirectX.

    Are you talking about this step? BTW, I'm running a Radeon HD 6870;

    bash ./winetricks vcrun200{3,5,8} d3dx9 corefonts physx

    To be sure I ran it again and the out put was;

    Paul@Mint:~$ bash ./winetricks vcrun200{3,5,8} d3dx9 corefonts physx
    ------------------------------------------------------
    You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
    ------------------------------------------------------
    Using winetricks 20190310-next - sha256sum: ad8b0383f6b05a3cc66c0299806c86 98d36c623fc9cdc4717e3cd123173a e45f with wine-4.0 and WINEARCH=win64
    Executing w_do_call vcrun2003
    vcrun2003 already installed, skipping
    Executing w_do_call vcrun2005
    vcrun2005 already installed, skipping
    Executing w_do_call vcrun2008
    vcrun2008 already installed, skipping
    Executing w_do_call d3dx9
    d3dx9 already installed, skipping
    Executing w_do_call corefonts
    corefonts already installed, skipping
    Executing w_do_call physx
    physx already installed, skipping
    Paul@Mint:~$
    Last edited by SatinKnight; May 28 2019 at 04:25 PM.

  10. #10
    Quote Originally Posted by SatinKnight View Post
    Are you talking about this step? BTW, (I'm running a Radeon HD 6870;


    To be sure I ran it again and the out put was;

    Paul@Mint:~$ bash ./winetricks vcrun200{3,5,8} d3dx9 corefonts physx
    ------------------------------------------------------
    You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
    ------------------------------------------------------
    Using winetricks 20190310-next - sha256sum: ad8b0383f6b05a3cc66c0299806c86 98d36c623fc9cdc4717e3cd123173a e45f with wine-4.0 and WINEARCH=win64
    Executing w_do_call vcrun2003
    vcrun2003 already installed, skipping
    Executing w_do_call vcrun2005
    vcrun2005 already installed, skipping
    Executing w_do_call vcrun2008
    vcrun2008 already installed, skipping
    Executing w_do_call d3dx9
    d3dx9 already installed, skipping
    Executing w_do_call corefonts
    corefonts already installed, skipping
    Executing w_do_call physx
    physx already installed, skipping
    Paul@Mint:~$
    Unfortunately I can not help you, because I don't know how

  11. #11
    Quote Originally Posted by SatinKnight View Post
    Are you talking about this step? BTW, I'm running a Radeon HD 6870;

    bash ./winetricks vcrun200{3,5,8} d3dx9 corefonts physx

    To be sure I ran it again and the out put was;

    Paul@Mint:~$ bash ./winetricks vcrun200{3,5,8} d3dx9 corefonts physx
    ...
    You may try configuring Dll overrides. Here is my working registry '~/.wine/user.reg' overrides section for comparison:
    Code:
    [Software\\Wine\\DllOverrides] 1559067816
    #time=1d5158276cd668c
    "*atl80"="native,builtin"
    "*atl90"="native,builtin"
    "*d3dx9_24"="native"
    "*d3dx9_25"="native"
    "*d3dx9_26"="native"
    "*d3dx9_27"="native"
    "*d3dx9_28"="native"
    "*d3dx9_29"="native"
    "*d3dx9_30"="native"
    "*d3dx9_31"="native"
    "*d3dx9_32"="native"
    "*d3dx9_33"="native"
    "*d3dx9_34"="native"
    "*d3dx9_35"="native"
    "*d3dx9_36"="native"
    "*d3dx9_37"="native"
    "*d3dx9_38"="native"
    "*d3dx9_39"="native"
    "*d3dx9_40"="native"
    "*d3dx9_41"="native"
    "*d3dx9_42"="native"
    "*d3dx9_43"="native"
    "*msvcm80"="native,builtin"
    "*msvcm90"="native,builtin"
    "*msvcp80"="native,builtin"
    "*msvcp90"="native,builtin"
    "*msvcr80"="native,builtin"
    "*msvcr90"="native,builtin"
    "*vcomp"="native,builtin"
    "*vcomp90"="native,builtin"
    "d3d8"="builtin"
    "d3d9"="builtin"
    "d3dim"="native"
    "d3drm"="native"
    Note that most compilers need to be set to "native" or try native first then buitin.

  12. #12
    Join Date
    Apr 2007
    Location
    Seattle, WA
    Posts
    62
    Quote Originally Posted by Lohdain_Meneldor View Post
    You may try configuring Dll overrides. Here is my working registry '~/.wine/user.reg' overrides section for comparison:
    Code:
    [Software\\Wine\\DllOverrides] 1559067816
    #time=1d5158276cd668c
    [snip]
    "d3d8"="builtin"
    "d3d9"="builtin"
    "d3dim"="native"
    "d3drm"="native"
    Note that most compilers need to be set to "native" or try native first then buitin.
    My user.reg had all but the last four lines noted above. I added them and rebooted the system. We'd just gotten update 24, so it took a little while to update everything and give the fixes a try. Unfortunately, LotRO still doesn't think DirectX is loaded (get as far as logging in, selecting server and hitting that play button). I get Game Error (105) Could not initialize Direct3D

  13. #13
    Quote Originally Posted by SatinKnight View Post
    My user.reg had all but the last four lines noted above. I added them and rebooted the system. We'd just gotten update 24, so it took a little while to update everything and give the fixes a try. Unfortunately, LotRO still doesn't think DirectX is loaded (get as far as logging in, selecting server and hitting that play button). I get Game Error (105) Could not initialize Direct3D
    I was stumped by DirectX9c at the same place. Here's a link to the full article which helped me, which hopefully may help you, too.

    https://www.dedoimedo.com/games/wine-directx.html

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

This form's session has expired. You need to reload the page.

Reload