I dunno how that will pan out, this post is mainly intended for pre-"Big Sur" macs.Ī general-use piece of wisdom for your life: don't buy apple. Building either FAF clients for Mac's new architecture is probably a tall ask, let alone emulating Forged Alliance. All of this was from the post-"Big Sur" era. I'll ask around to see if they can get a Mac native build going. I may not be able to answer your mac questions but if it pertains to proton and steam ect I'm pretty sure I'll be able to help out.Īlso I personally know jack shit about the python client, I use the downlord Java one (that's the one that's supported and who's support isn't going away anytime soon) I'm pretty sure you can get that one running natively too. That guy's guide will serve you much better. So yeah As you can see in the old thread I'd gotten an auto-install script working that was gonna work for every single existing operating system, even windows (this script doesn't work anymore because I haven't updated since it's really lost it's point: most of the things that were needed are no longer needed, it much easier today). I haven't actually played a multi game with it because my network is currently bad, but vs AI worked, and connecting in lobby worked, so it will probably work. It is not supported and will probably break randomly but oh well. Hopefully this is slightly helpful to anyone trying this. Since it pipes the output of wine, it is way easier trying to figure out why FA decided not to boot than going through forever.log or gamesession.log. Users/nrook/Library/PlayOnMac/wine/darwin-x86/3.17/bin/wine >/Users/nrook/FAForever/logs/winestdout 2>/Users/nrook/FAForever/logs/winestderr It is another dumb script, here is its contents: export WINEPREFIX=/Users/nrook/Library/PlayOnMac/wineprefix/steam Of course dumb_wine_shim is something I wrote myself. As such I just gave up and used this as the "exe" in the section of FA Lobby.ini: Įxe=/Users/nrook/code/faf-client/dumb_wine_shim PlayOnMac installs everything in "$HOME/Library/PlayOnMac/wineprefix/Steam/drive_c" so look there.įinally it was really hard to debug why launching FA was working or not working. Noah $(dirname "$0")/real-faf-uid don't know if this actually works well or not, so don't blame me if you get autobannedįor the FA directory, I used the directory from the WIne client. Then I renamed faf-uid to real-faf-uid, and in the place of faf-uid put this script: #!/bin/bash Specifically, I downloaded the linux faf-uid, then I installed this program called "noah" with homebrew. I had to do dumb stuff to get faf-uid working because there isn't a compiled Mac (BSD) client. I used the original FAF client because I know more about Python than Java, sorry Downlord. I don't remember exactly what I had to do here but it was annoying. At first Steam wouldn't download anything, I had to change it to use different download servers for some reason, using some weird advice I saw on Reddit or something. Once I had Steam I installed FA in there. I installed Steam with PlayOnMac, which is basically just a wrapper around Wine. hon_clientĮxcept I changed things whenever I had to. I basically started by following this guide. I got SupCom and FAF running on a mac and figured I should post about what I had to do, so anyone else who tries this has ideas.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |