Facebook Twitter YouTube Frictional Games | Forum | Privacy Policy | Dev Blog | Dev Wiki | Support | Gametee


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Crashes on Late 2013 Mac Pro
Stealthbug
Unregistered

 
#11
Solved: 9 Years, 2 Months, 1 Week ago RE: Crashes on Late 2013 Mac Pro
Crashed. Here's the log.

Thanks again for the help, guys.


Attached Files
.log   hpl.log (Size: 4.66 KB / Downloads: 174)
09-22-2015, 09:51 AM
jens Offline
Frictional Games

Posts: 4,093
Threads: 199
Joined: Apr 2006
Reputation: 202
#12
Solved: 9 Years, 2 Months, 1 Week ago RE: Crashes on Late 2013 Mac Pro
It did not use the settings file. Hmm did you put it IN the folder? It should be next to the folder.
09-22-2015, 09:53 AM
Website Find
Stealthbug
Unregistered

 
#13
Solved: 9 Years, 2 Months, 1 Week ago RE: Crashes on Late 2013 Mac Pro
This is what happens when I try to do things at 4:55AM.

Heh, here is the log with the file having been NEXT to the folder.


Attached Files
.log   hpl.log (Size: 4.86 KB / Downloads: 165)
09-22-2015, 09:56 AM
jens Offline
Frictional Games

Posts: 4,093
Threads: 199
Joined: Apr 2006
Reputation: 202
#14
Solved: 9 Years, 2 Months, 1 Week ago RE: Crashes on Late 2013 Mac Pro
I'm afraid I'm not sure what to do. I will have to ask the Mac porter to look into this. Do you know if you are running a 64-bit OS X? You can check by opening the terminal (in Applications/Utilities/) and type uname -a and hit enter. It should say something like "14.5.0 Darwin Kernel Version 14.5.0: Wed Jul 29 02:26:53 PDT 2015; root:xnu-2782.40.9~1/RELEASE_X86_64 x86_64"
09-22-2015, 10:23 AM
Website Find
Mudbill Offline
Muderator

Posts: 3,881
Threads: 59
Joined: Apr 2013
Reputation: 179
#15
Solved: 9 Years, 2 Months, 1 Week ago RE: Crashes on Late 2013 Mac Pro
In case you're unaware, all OS X versions past 10.6 Snow Leopard (from 2009) are 64-bit only. Anything after 2011 should be 64-bit. OP says he has a 2013 MP.

Considering the OP wrote that the error specifies a C:/ path, this has me thinking someone were testing in a Windows environment and forgot to update an absolute path. Obviously you will never find anything on C:/ on a Mac since it doesn't exist.

I can test running the game on my Mac later today (in about 6 hours) and see if I have any issues like this.

(This post was last modified: 09-22-2015, 10:48 AM by Mudbill.)
09-22-2015, 10:44 AM
Find
jens Offline
Frictional Games

Posts: 4,093
Threads: 199
Joined: Apr 2006
Reputation: 202
#16
Solved: 9 Years, 2 Months, 1 Week ago RE: Crashes on Late 2013 Mac Pro
Yeah I was fairly certain os x was 64 bit only, wanted to make sure!

The hpl.log was not the correct one so do not pay attention to it Smile
09-22-2015, 10:46 AM
Website Find
Mudbill Offline
Muderator

Posts: 3,881
Threads: 59
Joined: Apr 2013
Reputation: 179
#17
Solved: 9 Years, 2 Months, 1 Week ago RE: Crashes on Late 2013 Mac Pro
I see. I'll do a test anyway. Hopefully there will be no issues.

In the mean time I suppose a clean reinstall could be worth trying out.

(This post was last modified: 09-22-2015, 10:50 AM by Mudbill.)
09-22-2015, 10:50 AM
Find
jens Offline
Frictional Games

Posts: 4,093
Threads: 199
Joined: Apr 2006
Reputation: 202
#18
Solved: 9 Years, 2 Months, 1 Week ago RE: Crashes on Late 2013 Mac Pro
Stealthbug, do you get a system crash report when the game crashes? If we could get that it would be helpful.
09-22-2015, 01:31 PM
Website Find
Stealthbug
Unregistered

 
#19
Solved: 9 Years, 2 Months, 1 Week ago RE: Crashes on Late 2013 Mac Pro
Yes. Here it is.

Also, I performed a clean reinstall, restart, verfied the game cache, and no luck


Attached Files
.pdf   SOMACrash.pdf (Size: 114.74 KB / Downloads: 179)
09-22-2015, 06:31 PM
Guest
Unregistered

 
#20
Solved: 9 Years, 2 Months, 1 Week ago RE: Crashes on Late 2013 Mac Pro
The game does not work with multiple monitors on mac.
I unplugged both of my additional monitors, and the game opened.

Additionally,
It doesn't appear to crash if I plug the monitors in AFTER the game has booted up.
09-22-2015, 07:39 PM
Jump to the post that solved this thread.




Users browsing this thread: 1 Guest(s)