We have detected that cookies are not enabled on your browser. Please enable cookies to ensure the proper experience.
Results 1 to 15 of 15
  1. #1
    Join Date
    Jul 2020
    Posts
    1,925

    Procedure to update WINE to enable the 64-bit executable in the "Mac"/WINE client. Difficulty HIGH.

    ============================== ==========
    I have a revised, simpler procedure which replaces this one. Go to this thread here:
    https://www.lotro.com/forums/showthr...dure&p=8116531
    ============================== ==========

    A week or two ago, forum user Periadot reported that he was able to run the 64-bit executable of the "Mac"/WINE client on his Mac. At first I thought he was mistaken but after testing we determined that he was, in fact, running the 64-bit executable. Periadot did not make any changes to his WINE bottle – rather, he is not aware that he made any changes. I suspect that some other application he uses installed updated components in his WINE bottle without his knowledge and so now the 64-bit executable is able to run on his Mac because it has the dependencies which SSG now requires for that executable to run since the 2021-03-17 patch.

    Very recently, I was working with forum user Elphen to help him get the Windows/Crossover client running on his Mac. Elphen is an IT professional and so while we were working on that together he also took the initiative to attempt to update his WINE bottle on his own. He was successful. Some of the steps he described were unnecessary but using his reported success I was able to develop a procedure that includes only the necessary steps.

    The procedure I have developed is not simple, it is not quick, it is not for the impatient. However, it is a procedure which I think many of you might wish to attempt. If you perform the procedure successfully your "Mac"/WINE client's WINE components will be updated with (among other things) the latest Microsoft C++ components which will allow you, too, to run the 64-bit executable instead of being stuck with the inferior 32-bit executable. It will also prevent the browser nags you get when the LOTRO launcher application detects that those components are not installed – you won't get those browser nags because those components WILL BE INSTALLED!

    Note that you still must be using a pre-Catalina (i.e. Mojave or earlier) version of MacOS to run the "Mac"/WINE LOTRO client. This is because the LOTRO launcher application is 32-bit only and all versions of MacOS post-Mojave have no OS-level support of 32-bit applications. Some bits of open-source WINE are not fully "certified" to run in post-Mojave versions of MacOS for the same reason: They include some 32-bit components. So if you want to run LOTRO on a Mac with MacOS Catalina or later you must use Codeweavers Crossover which is basically the "pro" version of WINE. While not free, Crossover does provide a 2-week free trial so you can be sure it works for all the Windows applications you need to run before committing to a purchase. It is much easier to use than the procedure I detail in this message so if you have a little money I recommend going the Crossover route instead of following this procedure.

    I must warn you that this procedure involves many steps, the use of command-line tools, and the use of the sudo command which is very powerful and therefore potentially dangerous. I will repeat that it is not for the impatient, some things take time and do not show progress bars or other indications that they are working in the background. Copy-paste must be used carefully and/or command line instructions typed EXACTLY CORRECT. I therefore must recommend in the strongest terms that you perform a full backup of your boot volume before beginning any of this, and make another backup to another off-your-boot-drive safe location of the ~/Documents/The Lord of the Rings Online folder. Nothing described in this procedure is going to cause your computer to explode or suck you into the Matrix, but if you make exactly the wrong mistakes you might delete things or otherwise "break" things which were working OK before you started the procedure described in this message. Having a full backup allows you to restore your Mac to the exact condition it was in before you screwed it up. Having a handy backup of the ~/Documents/The Lord of the Rings Online folder allows you to restore all your LOTRO settings, keybinds, layouts, plugins, etc. easily if that becomes necessary.

    Before we begin, let's all thank Periadot for reporting the wacky behavior of his "Mac"/WINE client; Elphen for his technical expertise and individual initiative (even if he did leave me hanging in the middle of a fix-in-progess – j/k buddy!), David Baumgold (https://www.davidbaumgold.com/tutorials/wine-mac/) for his detailed Homebrew instructions (even if some of them are wrong or at least unnecessary for our purposes), and to Codeweavers and the open-source WINE project team for making any of this possible. Thanks to SSG for LOTRO too, I guess, but "no thanks" for refusing to provide a proper easy-to-install and fully functional WINE distribution for their Mac players subsequent to their 2021-03-17 patch.

    I wish to note that I tested this by creating a new – completely virgin – Mojave boot volume, fully updating Mojave using System Preferences->Software Update, downloading the "Mac"/WINE client from this website, installing it (which due to the Internet speed to my home took about 3 hours), testing it to be sure it worked (32-bit executable only, of course; I did test the 64-bit executable but of course it failed to run), and THEN following the procedure detailed below. After following the procedure detailed below, I was able to run the 64-bit executable successfully. The only thing I copied from my previous "Mac"/WINE client installation on my preexisting Mojave boot volume was the ~/Documents/The Lord of the Rings Online folder, everything else was installed from scratch. I also tested without using my copied ~/Documents/The Lord of the Rings Online folder and after making a few edits to the freshly-created .ini files was again able to run the 64-bit executable successfully.

    So it definitely works, but again, PLEASE, make backups first, follow all the instructions EXACTLY, and BE PATIENT during some of the installation steps which do not show their background progress. If you are not a detail-oriented person or are in a rush, please stop now and come back later, or stick with the inferior 32-bit executable, or go with Crossover.

    HOW TO UPDATE YOUR WINE BOTTLE...
    ...so that you can use SSG's "Mac"/WINE client with the superior 64-bit executable:
    1- Be sure you are booted into a version of MacOS which is between 10.11 El Capitan and 10.14 Mojave. No earlier or later version of MacOS will do. (You might be able to get away with 10.10 Yosemite but unless your LOTRO-playing Mac is truly ancient and incapable of anything more recent, please don't try.)
    2- If your Mac is capable of running 10.14 Mojave but you are running some older version of MacOS, I strongly recommend that you upgrade to Mojave before proceeding. I can't think of any reason not to use Mojave if your Mac is currently running something earlier but is capable of running Mojave. YOU might be able to think of a reason and if it's a good reason, well, OK then...
    3- Use System Preferences->Software Update (or in very old versions of MacOS, use the Mac App Store) to update whatever version of MacOS you use to the latest point update. For example, 10.14 Mojave is currently 10.14.6 and there are a number of security and Safari and other updates which will be installed even beyond the point release version number – so run an update even if you think you have the latest version just to be sure.
    4- Be sure you are logged in to your Mac with a Mac user account which has administrator privileges. You MUST have a password for your user account, if you run your Mac user account without a password not only will this procedure not work but you are running risks during general use of your computer that you should not be running. Go to System Preferences->Users & Groups to check, make whatever changes are needed.
    5- Be sure that LOTRO is not running. Be sure that no other applications which use WINE are running. If you have Crossover installed on your Mac, be sure it isn't running, either.
    6- Download this, you will need it later:
    https://download.developer.apple.com...ode_11.3.1.dmg
    After you download it, just leave it alone for now. It's fine to just leave it in your ~/Downloads folder or wherever it ended up after the download is complete as long as you know that location.
    7- Launch the Terminal application. You will find it here:
    /Applications/Utilities/Terminal
    The Terminal is a command-line tool which gives you access to powerful functions you can't perform with System Preferences or the Finder. It is not a rainbows-and-puppies Mac application with a nice click-and-drag GUI, it's just a text-based command line. Please be careful when pasting anything into or typing anything into the Terminal. Be aware that you must hit the RETURN key on your keyboard after entering a command into the Terminal.
    8- Resize the Terminal window so it's nice and big. This will allow you to see a lot of text at once.
    9- After you enter some commands into the Terminal it might ask you to enter your password. If asked, you must provide your password. You will not see your password as you type it, you will not even get asterisks (********), so carefully enter your password when it is requested and remember to hit the RETURN key afterward. I will not repeat this below, just be aware of it as you proceed through these instructions.
    10- We are now going to install a helper tool called Homebrew. Homebrew will allow us to update WINE. But in order to install Homebrew, your Mac must have a different helper tool called Ruby. If you are using any version of MacOS 10.11 El Capitan or later, your Mac has Ruby. (If for some reason your Mac does not have Ruby, I'm afraid you are on your own for installing it for now as I will not be covering the installation of Ruby in this procedure.) To install Homebrew, copy-paste the following line from between the CODE tags or VERY CAREFULLY type the following into the Terminal:
    Code:
    ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
    Stuff will happen, some of it will happen with the text equivalent of progress bars but some will happen with no way of knowing that something is happening – so if there is a long pause or you think things have frozen, HAVE PATIENCE.

    edit 2021-06-25: Forum use Filloston reported that the Ruby command here in Step 10 no longer works. This is because the people who maintain Homebrew changed the way they want it to be installed. Therefore, use this Bash command if the above Ruby command does not work:
    Code:
    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
    11- Eventually you will see the command-line prompt which means that Terminal is waiting for you to enter another command. When you see the prompt, copy-paste the following line from between the CODE tags or VERY CAREFULLY type the following into the Terminal:
    Code:
    brew doctor
    This will check your installation of Homebrew.
    12- Eventually, you'll see a bunch of text output. Read it, if there's something about Homebrew being broken or needing repair or reinstallation, you need to do those things. This should not be necessary. However, you do need to do some other installations now. Copy-paste the following line from between the CODE tags or VERY CAREFULLY type the following into the Terminal:
    Code:
    sudo rm -rf /Library/Developer/CommandLineTools
    13- Once you get the command-line prompt in Terminal (which means it's done with the last thing you told it to do), you need to install the Xcode 11.3.1 Command Line Tools from the disc image we downloaded way back in Step 6. Double-click that disc image then double-click on the Command Line Tools.pkg installer. Follow the prompts, enter your password when necessary. When the installer is done you can allow it to put itself in the Trash but do not empty the Trash – if you make a mistake you will need the disc image later to repeat this step.
    14- Copy-paste the following line from between the CODE tags or VERY CAREFULLY type the following into the Terminal:
    Code:
    brew doctor
    This will check your installation of Homebrew again. THIS time, it should tell you that's it's ready.
    15- We will now use Homebrew to install an updated version of WINE. Copy-paste the following line from between the CODE tags or VERY CAREFULLY type the following into the Terminal:
    Code:
    brew install wine-stable
    (I will note that Mr. Baumgold's instructions state to use the command "brew cask install wine-stable" but this requires the cask tool to be installed AND WE DO NOT NEED IT.)
    Once again, HAVE PATIENCE as this will take a little time and some things proceed without any visible progress. Wait until you see the command-line prompt.
    16- Quit out of the Terminal application.
    17- Assuming you were successfully using the 32-bit executable of the LOTRO "Mac"/WINE client before this, it should still work. Attempt to launch the game as you normally would (by using the lotroclient application). Check that everything is working as it was before you did any of the above steps. Then quit out of the game.
    18- Now let's get the 64-bit executable going: All you need to do is open the ~/Documents/The Lord of the Rings Online/User Preferences.ini file and change the following line...
    Code:
    GameClientType=1
    ...to this:
    Code:
    GameClientType=3
    Then SAVE the file and QUIT out of TextEdit.
    19- If you do not have a working UserPreferences64.ini file that you were using before SSG's 2021-03-17 patch, you need to create one:
    -->Make a copy of UserPreferences.ini. Rename the copy to UserPreferences64.ini.<--
    That's all there is to it. Do this only if you do not have a known-good UserPreferences64.ini file from before the evil patch in March.
    20- Attempt to launch the game as you normally would (by using the lotroclient application). Once you get to the character creation/selection screen, you can go into the in-game OPTIONS panel and turn your graphics settings up if you want to. The 64-bit executable can address far more RAM than the 32-bit executable which will allow you to play with fewer glitches and probably no crashes at all, even in player-dense or graphically-busy areas, even with your graphics turned up as high as your Mac can manage.

    21- I have set this final step a line below the rest because it is important but is not something you need to do now: Unlike a good, modern, well-behaved consumer application, there is no auto-update for WINE or Homebrew. Every now and then you need to check that they are updated to their latest versions. Fortunately, this is pretty easy. Just use the following Terminal command:
    Code:
    brew upgrade
    That will perform updates for both WINE and Homebrew itself. If you have been playing LOTRO and it stops working for some reason, try the BREW UPGRADE command in Terminal. This might be necessary a couple of times a year, maybe more often, maybe never – it depends more on whether and how often SSG demands further updated Windows/WINE components more than it does on anything in the current WINE distribution actually needing an update due to some internal issue.

    To repeat: I have tested this procedure and it works. If it doesn't work for you, try restoring your Mac to the condition it was in before you performed any of the above steps using the backup you made before you started; then try again. If you fail a second time, and have a specific question, please be welcome to ask it here in this thread. If you write, "Gee whiz, Tral: I followed all your steps twice and it still won't work for me!" I won't be able to help you. I need details, screenshots, and frankly there are many things that can go wrong because any command-line instruction you enter has to be EXACTLY CORRECT and the most likely problem is that you typoed or copy-pasted incorrectly somehow which I obviously have no way of knowing or helping you with. I'll do my best to help, but you need to give me as much information as possible in order to get a useful response from me.

    So there you go, have at it if you feel confident. MAKE A FULL SYSTEM BACKUP BEFORE YOU BEGIN! MAKE AN EXTRA BACKUP OF YOUR ~/DOCUMENTS/THE LORD OF THE RINGS ONLINE FOLDER BEFORE YOU BEGIN!

    I hope that SSG will release an updated version of their "Mac"/WINE client with the required updated WINE components which will auto install using Python or whatever other tool they choose to use because I know that, while many of you will be successful with the above, some of you will fail and others of you will not try because it's too daunting. Until then, well – there you go, the procedure is here if you want to try it. Good luck!
    Last edited by Tralfazz; Jan 02 2022 at 01:50 PM. Reason: TO DO, not DO DO

  2. #2
    Join Date
    Jul 2020
    Posts
    1,925
    I will note that it might be possible to run LOTRO in post-Mojave versions of MacOS using open-source WINE but this would involve using the "developer" release of WINE rather than the "stable" release of WINE. I will not provide instructions for doing so, I will not offer assistance to anyone who tries. Sorry, but there's a reason the "developer" release is not considered "stable" enough for most people to use.

    If you have a Mac whose CPU is an Apple System-On-Chip (a "SOC" or "Apple Silicon") rather than Intel, you will not be able to use the above procedure because Apple SOC Macs require, at minimum, MacOS Big Sur 11 to run. The Rosetta 2 Intel->Apple SOC instruction set translation layer works very well, you CAN get an Apple SOC Mac to run LOTRO using Crossover. However, as I write this, open-source WINE is not a viable path due to the 32-bit component restrictions both in LOTRO and in open-source WINE itself as I explained elsewhere.

    I will also note that it might be possible to get LOTRO to run DirectX 11 using open-source WINE but this involves DXVK which itself involves Vulkan and that's just way, way too much for me to even think about trying to develop a simple procedure for or provide support for on a message board. I see various web pages where people describe how to get DirectX 11 with DXVK and Vulkan running with open-source WINE, I see some YouTube videos too. It's a lot of work, I don't think it's worth it.

    So basically, if you want to run LOTRO in a post-Mojave version of MacOS or if you want to run DirectX 11 instead of DirectX 9, you are either on your own with doing that using open-source WINE or you must use Codeweavers Crossover. Crossover is basically the "pro" version of WINE with lots of extra functionality you won't find in open-source WINE and with an easy to use GUI instead of those nasty command line tools. It isn't free but it does have a 2-week free trial so you can decide if it's worth the expense for you. I use Crossover for several Windows applications, LOTRO and one other game plus a number of practical apps; I highly recommend it.
    Last edited by Tralfazz; Jun 04 2021 at 10:45 AM. Reason: Added stuff about Apple SOC Macs.

  3. #3
    Join Date
    Dec 2008
    Posts
    63
    That is a great walkthrough. I am assuming that you ran through all of that and then got it to work in your new Mojave partition. You really deserve some sort of Turbine Points or something from SSG for all of the support you have provided to everyone on the forums.

    The way that you have done it is a bit different than the way that I got it to work, but I did not start fresh as you did and how amazing you can replicate the fix in such a clean and concise manner.

    Makes me almost want to test it out but I don't have any other Mojave or below macs, they are all on Catalina


    Congrats!!!

  4. #4
    Join Date
    Jul 2020
    Posts
    1,925
    Elphen, if you are willing to create a new Mojave boot volume and do a fresh install of the “Mac”/WINE client, and then perform the procedure in the OP, I’d appreciate the effort. It would be good to have confirmation that the procedure works. I did test it, as I said in the OP. But it’s always good to have independent confirmation.

    Of course, doing that would be of no value to you since you have the game running on all your Macs already. And it is time-consuming (the downloading part, anyway). Just a thought in case you find yourself bored and looking for something to fill your time… Hehe!

  5. #5
    Join Date
    Dec 2008
    Posts
    63
    Quote Originally Posted by Tralfazz View Post
    Elphen, if you are willing to create a new Mojave boot volume and do a fresh install of the “Mac”/WINE client, and then perform the procedure in the OP, I’d appreciate the effort. It would be good to have confirmation that the procedure works. I did test it, as I said in the OP. But it’s always good to have independent confirmation.

    Of course, doing that would be of no value to you since you have the game running on all your Macs already. And it is time-consuming (the downloading part, anyway). Just a thought in case you find yourself bored and looking for something to fill your time… Hehe!
    Oh, I love to tinker and I have more Macs. I may not get around to it soon but I would definitely love to try it.

    Have a wonderful weekend.

  6. Jun 12 2021, 08:33 AM

  7. #6
    Join Date
    Jul 2020
    Posts
    1,925
    Hi, Darkwolfsburg!

    That .dmg is on Apple’s developer site. If you are logged in there with your Apple iCloud ID and click the link, you should be taken to a webpage that immediately asks you if you wish to permit the download to occur. If you are not logged in, you will be taken to a page that tells you so and you will find a link near the bottom of that page which will take you to a page where you can log in. Once you’re logged in, close those windows/tabs and click that link again to be taken to a page that will immediately ask you if you wish to permit the download to occur.

    Don’t be intimidated by the fact that it’s an Apple site for “developers” – any Apple iCloud account can sign in.

    The link at the bottom is VIEW YOUR ACCOUNT:
    https://developer.apple.com/account/...rship#/welcome

    I just tested this to be sure I remembered all that correctly. I did; the above is correct. Sorry if that threw you off, I assumed that anyone who was not already logged in would follow the link at the bottom of the “failure” page and therefore I didn’t provide more explicit instructions within the procedure in the OP.

    So try the download again after logging in. Please be welcome to ask additional questions if anything else comes up.

    edit: Darkwolfsburg deleted his two messages, one of which I responded to here.

    edit2: Just to expand on the above a bit more:

    You will need an Apple ID/iCloud account to access the Xcode 11.3.1 Command Line Tools referenced in Step 6 and Step 13 of the procudure in the OP. If you can't just follow the link, go to this one:
    https://developer.apple.com/download...20line%20tools
    ...and scroll down until you find "Command Line Tools for Xcode 11.3.1" then expand the entry to see the download link. The direct download link is:
    https://download.developer.apple.com...ode_11.3.1.dmg
    ...but you need to be logged in to the Apple developer site developer.apple.com in order to download the file or even see the page with the file description.

    Last edited by Tralfazz; Jun 13 2021 at 05:37 PM.

  8. Jun 12 2021, 04:25 PM

  9. #7
    Join Date
    Dec 2009
    Posts
    10
    Still can't get the file. Sent you a DM Tralfazz.

  10. #8
    Join Date
    Jul 2020
    Posts
    1,925
    Quote Originally Posted by Darkwolfsburg View Post
    Still can't get the file. Sent you a DM Tralfazz.
    I responded to your Direct Message. The only reason I knew to look for it was because I read your public message here.

    Please keep this exchange public. Continue to use this thread or create a thread just for your issue here in the Mac Technical Support forum. The only reason to go private or to email is if we need to exchange off-forum contact information which I generally think is a bad idea: Sharing such things with Internet randos can be dangerous even if I am the exception to that rule. Public messages also exist in a place where other people having similar issues can see them and perhaps solve their problem without needing to add to an existing thread or create their own.

    I hope the suggestions I made in my private reply resolve your issue. I look forward to your report either way.
    Last edited by Tralfazz; Jun 17 2021 at 09:40 AM. Reason: TO not IT

  11. #9
    Join Date
    Dec 2009
    Posts
    10
    Quote Originally Posted by Tralfazz View Post
    I responded to your Direct Message. The only reason I knew it look for it was because I read your public message here.

    Please keep this exchange public. Continue to use this thread or create a thread just for your issue here in the Mac Technical Support forum. The only reason to go private or to email is if we need to exchange off-forum contact information which I generally think is a bad idea: Sharing such things with Internet randos can be dangerous even if I am the exception to that rule. Public messages also exist in a place where other people having similar issues can see them and perhaps solve their problem without needing to add to an existing thread or create their own.

    I hope the suggestions I made in my private reply resolve your issue. I look forward to your report either way.
    I'm not going to bother with this. I am way too busy with work.
    Sorry I took the extremely inappropriate route of sending you a DM. I was just looking to fix my game. I still haven't done that, and now I'm being chastised for something I did instead.
    Peace.

  12. #10
    Join Date
    Jul 2020
    Posts
    1,925
    Quote Originally Posted by Darkwolfsburg View Post
    I'm not going to bother with this. I am way too busy with work.
    Sorry I took the extremely inappropriate route of sending you a DM. I was just looking to fix my game. I still haven't done that, and now I'm being chastised for something I did instead.
    Peace.
    That was not chastisement. That was a request with an explanation. There was no need for sarcasm. Even so, I wish I had chosen language in my last message in this thread which you wouldn't have found offensive, because something I wrote did strike you the wrong way. If you can suggest what I might have written which would have conveyed the same content without setting you off, please be welcome to do so.

    I agree that the process necessary to update open-source WINE is a lot of trouble. This is not my fault, it's just the way it is. I continue to suggest that it's better to use (and pay for) Crossover with its relatively simple GUI interface for managing its proprietary version of WINE, especially since Crossover will allow LOTRO to be played in post-Mojave versions of MacOS instead of forcing the user to stick with Mojave or earlier. For those that can't or won't use Crossover, SSG ought to get the WINE 6.0 distribution (the latest stable release version) in their "Mac"/WINE client download rather than WINE 4.8 – at least, I think that's all they'd have to do – or otherwise provide a simple WINE upgrader tool for their current Mac players.

    Until then, for those that neither want to wait and continue to use the 32-bit executable in the meantime, and for those who cannot or will not use Crossover; this procedure is available and while neither simple nor quick it does work.

  13. #11
    Join Date
    Jul 2020
    Posts
    1,925
    For archival purposes, the following is the entirety of the PM exchange between Darkwolfsburg and me:
    --------------------
    Quote Originally Posted by Tralfazz
    Quote Originally Posted by Darkwolfsburg
    Hi there, thanks for replying to my comment.
    I have been locked out of my Apple ID for years. I have not been able to contact Apple to get them to help me.

    I bit the bullet and created another account, but it asks me to PAY for a Developer account. I don't know what's going on but this is really convoluted and frustrating.

    Can you DM me that DMG file directly maybe? It's the only thing keeping me from trying to update Wine.
    Thanks for any help you can offer.
    I'm sorry you're having trouble, Darkwolfsburg. I have never paid for a developer account and I can access all that stuff with my plain-vanilla iCloud ID. I can't explain why that should be different for the two of us. I know a number of people who use Homebrew and you can't use Homebrew without the Xcode command line tools and the only way to get them that I know of is from that Apple developer site (other than some dicey torrent, I strongly recommend against looking for one of those).

    I know that free accounts can access Xcode and the other developer tools, I have helped other people with this without trouble. You might have tried to create a "pro" developer account which is the type needed to test and deploy apps in Apple's store. But don't worry, we can work around it regardless of the reason you are experiencing this.

    I'll send you the .dmg but only as a last resort. You shouldn't install things from some Internet rando like me. I am, of course, the exception to that rule! But it's a bad habit and someone who is trying to break into your system would say the exact same thing. If it comes to this, you will need to give me an email address because I can't post it on a download site or even my personal Dropbox storage - both because it's too big and because the license does not permit third-party distribution. I'm willing to sorta-kinda violate the license to send it to you, but not by posting it in a public site so I need to send it to you via email.

    So try this first:
    1- Open a Terminal window.
    2- Enter this command:
    Code:
    xcode-select --install
    3- You'll be told that Xcode needs the command line tools and you will be asked if you want to install them. Follow the prompts and install them.
    4- When the package begins downloading it will look like it will take HOURS to complete but it will only take a couple of minutes. Be patient, the progress bar is pretty accurate even if the "time remaining" notice starts off as way, way off the mark.

    If that doesn't work, you might need to install Xcode first. If so, go to the App Store and install Xcode then try that Terminal command again.
    https://apps.apple.com/us/app/xcode/id497799835?mt=12

    If you try the Terminal command and it doesn't work, and you then install Xcode from the Mac App Store and then try the Terminal command and it still doesn't work; let me know what did happen, tell me your email address, and I'll try to email it to you.

    I'd appreciate it if you were to not delete any future public messages to me, especially any that I respond to. Other people who might be following along to solve their own problem find that confusing.

    Best wishes,
    LOTRO Forums: Tralfazz
    LOTROINTERFACE.COM: JohnMHammer
    --------------------

  14. #12
    Join Date
    May 2021
    Posts
    68
    Quote Originally Posted by Tralfazz View Post
    10- We are now going to install a helper tool called Homebrew. Homebrew will allow us to update WINE. But in order to install Homebrew, your Mac must have a different helper tool called Ruby. If you are using any version of MacOS 10.11 El Capitan or later, your Mac has Ruby. (If for some reason your Mac does not have Ruby, I'm afraid you are on your own for installing it for now as I will not be covering the installation of Ruby in this procedure.) To install Homebrew, copy-paste the following line from between the CODE tags or VERY CAREFULLY type the following into the Terminal:
    Code:
    ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
    When I copied this text, I got the following response:
    Warning: The Ruby Homebrew installer is now deprecated and has been rewritten in
    Bash. Please migrate to the following command:
    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

    How do I adapt Step 10 to this new information?

    Thank you for the considerable amount of time you have invested in helping Mac users.

  15. #13
    Join Date
    Jul 2020
    Posts
    1,925
    Hi, Filloston!

    I knew that the Ruby installer for Homebrew was going to be replaced by a Bash installer because Ruby won't be installed by default in future versions of MacOS. However, I didn't think the Ruby installer was going to be deprecated. Apparently, it was. There was no good reason for the Homebrew crew to do this, but things like that sometimes happen with publicly-distributed open source software.

    When I have the opportunity, I will prep a fresh Mojave test volume and use it to test the new Bash installer. Until then:

    Bash is the normal Terminal shell. All you should have to do is type or copy-paste this line instead of the Ruby command:
    Code:
    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
    If that doesn't work, and ONLY if that doesn't work, try this command:
    Code:
    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
    This is based on what you reported, I don't know why that Terminal message should have suggested .../HEAD/install.sh" rather than .../master/install.sh" but it's possible the Homebrew folks migrated the installer to that different path when they removed the Ruby installer and added the Bash installer. Again, try this command line only if the one above does not work.

    If you do this, please report back with your results. As I said, I will test this myself when I can, but I can't do so right now. So your feedback on this will be greatly appreciated.
    Last edited by Tralfazz; Jun 25 2021 at 11:00 PM. Reason: Corrected the spelling of Filloston's name in the first line.

  16. #14
    Join Date
    May 2021
    Posts
    68
    Quote Originally Posted by Tralfazz View Post
    All you should have to do is type or copy-paste this line instead of the Ruby command:
    Code:
    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh)"
    This one, the first option you gave, worked like a charm. Because I had already taken the steps to install the command line tools, I did the step for checking the homebrew installation, which was fine. From there, I continued with your directions installing Wine, logging in as before, and then changing the UserPreferences.ini file.

    Result: I turned graphic settings back up to High. I was able to go to MT (Midsummer) and do crazy things like ride a mount, use Stable masters, and go to the Citadel without crashing. I experienced a little jerkiness. That is all. Before now, I avoided doing all these things at much lower graphics settings because I frequently crashed when I tried.

    Thank you for the quick response. Since you prefer details as a background, the specs of my system and LOTRO installation are at the bottom of this post.

    Filloston

    System:
    Model Name: MacBook Pro
    Model Identifier: MacBookPro12,1
    Processor Name: Intel Core i5
    Processor Speed: 2.7 GHz
    Number of Processors: 1
    Total Number of Cores: 2
    L2 Cache (per Core): 256 KB
    L3 Cache: 3 MB
    Hyper-Threading Technology: Enabled
    Memory: 8 GB
    Boot ROM Version: 427.0.0.0.0
    SMC Version (system): 2.28f7

    UserPreferences.ini (Partial)
    GameClientType=3

    [Display]
    AllowDesktopCompositing=True
    AllowFakeFullScreen=True
    AllowWindowResizing=True
    Antialiasing=Disabled
    ConfineFullScreenMouseCursor=T rue
    FixedOutputScaling=Default
    ForceFakeFullScreen=False
    FullScreen=False
    RefreshRate=Auto
    Resolution=1024x768
    ScreenMode=FullScreen
    SyncToRefresh=False
    TripleBuffering=False
    WindowedResolution=67109632
    [Graphics]
    AvatarTextureCompositing=True
    AvatarUpdateVisible=True
    PVMPPerformanceOverride=True
    [Input]
    InvertMouseLookYAxis=False
    JoystickDeadZone=0.25
    MouseLookSensitivity=0.10
    MouseLookSmoothingAmount=0.00
    PitchKeySpeed=60.00
    RollKeySpeed=60.00
    TurnKeySpeed=150.00
    XInputDetection=False
    [International]
    UseIME=False
    [Misc]
    PlayedIntroMovie=True
    TooltipDelay=0.30
    TooltipEnable=True
    [Net]
    BindInterface=
    ComputeUniquePort=True
    ConnectionSpeed=0.00
    UserSpecifiedPort=0
    [Render]
    AllowGammaChanges=True
    AlphaToCoverage=False
    AmbientLightBoost=0.00
    AmbientOcclusion=False
    AnisotropicQuality=4
    AspectRatio=Auto
    AtmosphericsDetail=Medium
    BlobShadows=True
    BloomIntensity=1.00
    BlurFilterQuality=Medium
    Brightness=1.00
    Contrast=1.00
    D3DVersionPromptedForAtStartup =0
    DisplayAdapter=0
    DistantImposters=True
    DynamicParticles=All
    EnablePortraits=True
    EnvironmentStencilShadows=Fals e
    FarLandscapeNormalMaps=False
    FrillDensity=0.75
    FrillDistance=Medium
    Gamma=1.00
    GlowMapping=True
    GraphicsCore=D3D9
    HavePromptedForD3D10AtStartup= False
    InteractiveWater=Medium
    LandscapeDrawDistance=High
    LandscapeLightingQuality=Low
    LandscapeShoreEffects=High
    LandscapeStaticObjectShadows=M edium
    MaterialDetail=High
    MaxHardwareClass=0
    MeasuredFillRate=0.10
    MemoryUsage=0.30
    MeshCombining=True
    ModelDetail=High
    MultiPassLighting=True
    ObjectDrawDistance=VeryHigh
    OverbrightBloomFilter=False
    PlayerCrowdQuality=1.00
    PrecipitationEffects=True
    ShadowMapQuality=0
    SpecularLighting=True
    StaticEnvironmentalObjects=Tru e
    StencilShadows=Medium
    SurfaceReflections=Low
    TextureDetail=High
    TextureFiltering=Sharp
    VideoPostEffects=True
    VolumetricLight=False
    PerPixelLightingAttenuation=Tr ue
    [Sound]
    AmbientVolume=0.50
    CombatVolume=0.48
    DefaultVolume=1.00
    EAXEnabled=False
    FocusBehavior=Persist Sound
    MasterVolume=1.00
    MaxPlayingSounds=64
    MusicDisabled=False
    MusicVolume=0.50
    PersistentSound=False
    PlayerMusicVolume=1.00
    QuantizedPlayerMusicVolume=1.0 0
    SFXVolume=0.47
    SoundDisabled=False
    SoundFeatures=OpenAL Soft on Built-in Output
    SoundProvider=OpenAL
    UIVolume=0.48
    VOVolume=0.47
    [Troubleshooting]
    EngineSpeed=VeryHigh
    MaximumFrameRate=121
    [UI]
    CharSelectSortType=0
    FloatyTextOnTop=False
    FloatyTextOpacity=1.00
    FloatyTextScale=1.00
    RadarMovementSmoothing=True
    WebstoreExternalWindow=False
    MapQuestListXScreenPercentage= 0.00
    MapQuestListYScreenPercentage= 0.68
    MountAppearanceShowPlayerMount ed=True
    Bag1Columns=5
    Bag2Columns=5
    Bag3Columns=5
    Bag4Columns=5
    Bag5Columns=5
    Bag6Columns=5
    BankRepositoryAccountItemDispl ayShowText=True
    BankRepositoryCharacterItemDis playShowText=True
    BankRepositorySharedHousingIte mDisplayShowText=True
    BankRepositoryStandardHousingI temDisplayShowText=True
    StatTreeShowAllStats=True
    [Voice]
    DefaultGroupVolume=0.75
    DeviceCapture=BB55ADF7-95FD-42DA-91D9-ED72B92AC136
    DevicePlayback=D13C0E8C-0044-40B0-96B5-C4AF0A9BA2F8
    HandsFree=False
    MicCaptureThreshold=0.30
    MicVolume=1.00
    NetworkLatencyThresh=250
    VoiceVolume=1.00
    [HttpProxy]
    HttpProxyAccess=PreConfig
    HttpProxy=:0
    HttpProxyAuthenticate=false
    HttpProxyUsername=
    HttpProxyPassword=
    HttpProxyBypass=

  17. #15
    Join Date
    Jul 2020
    Posts
    1,925
    I have a revised, simpler procedure which replaces the one detailed in this thread. Please go to this thread here:
    https://www.lotro.com/forums/showthr...dure&p=8116531

 

 

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