FreeSO on Mac

Discussion in 'Support' started by RHY3756547, Nov 30, 2017.

  1. Mikaelo

    Mikaelo New Member

    Success -- got it working on Mac :) If anyone has any questions feel free to hit me up -- I ended up using my Windows PC to copy the game files over since cabextract wasn't behaving.
  2. RHY3756547

    RHY3756547 FreeSO Developer Staff Member Moderator

    If anyone else is missing cabextract or any of the other binaries, try install them through Homebrew instead.
  3. RHY3756547

    RHY3756547 FreeSO Developer Staff Member Moderator

    I've added new instructions that use Homebrew and our new TSO download source to the main post. These were written by @dotequals, so give him your thanks if they are helpful.
    dotequals likes this.
  4. JimGarb

    JimGarb New Member

    I know this is a rather old thread, but I've been unsuccessful in getting the application to start after an update process. I get a crash in the terminal. Of course I didn't record what the crash was (why would I think ahead?) I fixed it by deleting the contents of my "FreeSO" folder in Documents, re-downloading the updated version of the client and unzipping it and then unzipping the Macextras.zip again and overwriting files. This allows the application to start and download the update. Is there any way around this? Am I doing something wrong? Thanks for getting this working on the Mac, great job.
  5. dotequals

    dotequals Member

    Currently, yes, mono is supposed to crash after the download and before the update is supposed to start. On Mac and Linux the freeso.command and freeso3d.command scripts handle updating the client, so you just have to run them again after the crash.
  6. [7G] Wolfy

    [7G] Wolfy New Member

    is there any way to get a video to do this im not used to mac and im trying to help a friend
  7. JimGarb

    JimGarb New Member

    Hi Dot, thanks for the response. I do run the scripts again and I get into an update loop.
  8. dotequals

    dotequals Member

    Hmm, somebody else seems to be running into that here, but I haven't come across it. When you run freeso.command the second time does it have a bunch of text like "Inflating blah blah blah"? Did you close the terminal window with the crashed instance of mono before running it?
  9. Queenofthedelta

    Queenofthedelta New Member

    @JimGarb I was having the same problem on my girlfriend's mac. Haven't tried again since giving up, but have you had any luck yet?
  10. dotequals

    dotequals Member

    @JimGarb and @Queenofthedelta a screenshot or copy of the terminal output text after running ./freeso.command for the second time (after the game has downloaded the update and crashed once) would be helpful in figuring out this problem.

    If posting the info here, please take caution to edit out any personal info the terminal window might show such as your first and last name. Alternatively you can just send the output to me via DM on here or on Discord.
  11. JimGarb

    JimGarb New Member

    @dotequals Thanks for the response. I just went through the recent update semi-successfully. I've sent you a message in Discord on#support.
  12. spaz926

    spaz926 New Member

    Beta update-72h...
    2D mode: Launch, login, world load all work fine. When entering properties I'm presented with my sim standing in a fully white area with only the outlines of some objects showing.
    3D mode: Launch, login, world load all work fine. When entering properties, all items load correctly but other sims bodies are fully black. I can see their faces and hands and a fully black body. Some items disappear when in use.

    Also I've noticed on this thread a lot of people having trouble launching. Make sure you type the freeso.command in the terminal as
    Code:
    ./freeso.command
    the ./ is needed to execute. Terminal doesn't know what you mean if you don't add the ./ in front.
  13. dotequals

    dotequals Member

    @spaz926 For 2D mode try disabling anti-aliasing. As for 3D make sure you're at least a notch above the lowest lighting setting on the slider.

    Items disappearing in use is to be expected for objects that have different states that your client hasn't "seen" yet so it needs to generate the mesh if the object isn't part of the remeshed objects in your MeshReplace folder.
    spaz926 likes this.
  14. spaz926

    spaz926 New Member

    Thanks dotequals... Both of those tips fixed my issues.

    I also downloaded the MeshReplace zip file so I have FAR less disappearing items.

    Thanks to @zoey I got Discord integration working. Yay.

    EDIT: I also got two app bundles (one for 2D and one for 3D) created and working. Can be placed anywhere on the filesystem as long as FreeSO is in ~/Documents/FreeSO/
    I can't codesign them (so gatekeeper will complain that it is untrusted an untrusted source). But I can share them if anybody would like and is permitted on the forum.
    Last edited: Feb 15, 2019
    dotequals likes this.
  15. Newt

    Newt New Member

    The brew.sh GitHub 404s. Is there another way for me to get that?
  16. spaz926

    spaz926 New Member

    https://brew.sh
  17. Newt

    Newt New Member

    lol I'm trying to figure out how yours is different. It works, though. Thanks!
  18. spaz926

    spaz926 New Member

  19. Newt

    Newt New Member

  20. Pawel3d

    Pawel3d New Member

    Hey! I did everything in accordance with the steps in the first post, but it does not work for me. Terminal entry:
    Code:
     ./freeso.command
    AL lib: (WW) GetProcPath: Failed to readlink /proc/self/file: No such file or directory
    AL lib: (WW) alc_initconfig: Failed to initialize backend "jack"
    WARNING: The Carbon driver has not been ported to 64bits, and very few parts of Windows.Forms will work properly, or at all
    Stacktrace:
    
      at <unknown> <0xffffffff>
      at (wrapper managed-to-native) System.Windows.Forms.XplatUICarbon.CGDisplayBounds (intptr) [0x00002] in <5104060dae9b46fe810195014e83cde5>:0
      at System.Windows.Forms.XplatUICarbon.get_WorkingArea () [0x00005] in <5104060dae9b46fe810195014e83cde5>:0
      at System.Windows.Forms.XplatUICarbon.get_VirtualScreen () [0x00000] in <5104060dae9b46fe810195014e83cde5>:0
      at System.Windows.Forms.XplatUI.get_VirtualScreen () [0x00000] in <5104060dae9b46fe810195014e83cde5>:0
      at System.Windows.Forms.Screen..cctor () [0x00034] in <5104060dae9b46fe810195014e83cde5>:0
      at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) [0x0001e] in <58ef3af9ea4944daa82b0c341685a066>:0
      at <unknown> <0xffffffff>
      at System.Windows.Forms.MessageBox/MessageBoxForm.InitFormsSize () [0x00002] in <5104060dae9b46fe810195014e83cde5>:0
      at System.Windows.Forms.MessageBox/MessageBoxForm.RunDialog () [0x0000f] in <5104060dae9b46fe810195014e83cde5>:0
      at (wrapper remoting-invoke-with-check) System.Windows.Forms.MessageBox/MessageBoxForm.RunDialog () [0x00031] in <5104060dae9b46fe810195014e83cde5>:0
      at System.Windows.Forms.MessageBox.Show (string,string) [0x0000a] in <5104060dae9b46fe810195014e83cde5>:0
      at FSO.Windows.Program.CurrentDomain_UnhandledException (object,System.UnhandledExceptionEventArgs) [0x0002f] in <c74e75d7e33146bbbe8a3949fadc75dc>:0
      at (wrapper delegate-invoke) <Module>.invoke_void_object_UnhandledExceptionEventArgs (object,System.UnhandledExceptionEventArgs) [0x00068] in <58ef3af9ea4944daa82b0c341685a066>:0
      at (wrapper runtime-invoke) <Module>.runtime_invoke_void__this___object_object (object,intptr,intptr,intptr) [0x0001e] in <58ef3af9ea4944daa82b0c341685a066>:0
    Memory around native instruction pointer (0x7fff60a0dc9b):
    0x7fff60a0dc8b  53 50 48 89 fb 48 8b 05 a1 93 81 38 48 8b 48 18  SPH..H.....8H.H.
    0x7fff60a0dc9b  48 89 4b 18 48 8b 48 10 48 89 4b 10 48 8b 08 48  H.K.H.H.H.K.H..H
    0x7fff60a0dcab  8b 40 08 48 89 43 08 48 89 0b 89 f7 48 89 de e8  .@.H.C.H....H...
    0x7fff60a0dcbb  68 80 fc ff 48 89 d8 48 83 c4 08 5b 5d c3 55 48  h...H..H...[].UH
    
    Native stacktrace:
    
    Crash Reporter has timed out, sending SIGSEGV
    AL lib: (EE) alc_cleanup: 1 device not closed
    

Share This Page