Mac Steam startup crash

[mstephens]

Haven't been able to open the game yet as it crashes on startup.  I attached the crash details.

I also found my RuntimeData folder and took a snapshop... looks as though I'm missing a few things.

[x4000]

I dont see anything that appears to be missing in runtimedata, and unfortunately a crash log likethat never seems to contain any useful info. We have our own crash logs that are helpful, but he fact that those didn't get logged in runtimedata means it didn't even get to the point of running our code. This generally means a corrupt install, with not all files downloaded or similar. I'd try refreshing you local steam cache for the game, and that should fix whatever files are missing or corrupt.

Hope that helps!

[mstephens]

I gave that a shot, and also downloaded the demo and tried it separately.  No luck 

Suggestions?

[x4000]

The steam demo, or the one from us?

We've literally never had anyone not able to run the game in this fashion before on the unity versions, so I'm pretty baffled.  Info on your system (mainly the OS version, etc) would be appreciated.  But also how much ram do you have?  And are you running any antivirus?  Sometimes that gets aggressive with unity programs and prevents them from running properly, but that usually results in a crash.

You might also try right-clicking the AIWar.app and hitting Show Package Contents, then going into Contents/MacOS and seeing if you can run the executable in there directly.

Hope that helps, but this is definitely a very odd one. 

[mstephens]

I tried the demo from you guys.  Also tried to run the exec file.

OSX: 10.5.8
RAM: 1 GB
CPU speed: 2.16 Ghz Core Duo
Graphics: ATI Radeon X1600

[x4000]

Hmm, that is very odd.  Again, this isn't something we've ever seen.  It sounds like something external is failing and causing the game to crash.  Such as, if it can't initialize 3D for some reason.

Looking around based on your crash log, one thing I found similar was with BaseCamp crashing under similar circumstances here: https://forums.garmin.com/showthread.php?t=9707  Apparently in that case it was a driver from Apple being unstable in 3D, but I imagine it could also be OpenGL having a crash based on the libraries that are loaded.

I'm not an expert on OSX, but we use the Unity 3D engine so that a lot of this sort of low-level stuff is supposedly abstracted away.  Not so much in this case, eh?  But when I do a search for EXC_CRASH SIGABRT "unity 3d" osx I come up with literally nothing for OSX and the unity 3D engine (just a few things for iPhone).  This makes me think this it is something super unique not just with AI War, but with Unity 3D as well.

I'm sure that's of great comfort to you.  Sigh.  But it sounds like either you have some faulty OS software or driver software, or that there is some hardware that is starting to fail.  Seeing if you can update the drivers, if that's available, or if you can repair the installation of the OS, might be the ticket.  Or running some test software on your graphics card and/or ram.  On the PC side I'd recommend memtest86 to verify your ram, astra32 to check for hardware error messages in general, and dxdiag to check out your graphics card.  On the OSX side I'm really not sure what to suggest, but I imagine there are counterparts of some sort.

[Vampyre]

Hmmm maybe I can give you my five cents. 10.5.8... Sounds like Leopard to me. Snow Leopard being 10.6.x

What is needed to search is the compatibility of Unity Engine with Leopard. For that I have no idea, but I'm sure x4000 knows where to find the answer...

Edit : After having checked the docs in Unity, I found this :

System Requirements for Unity Authoring:
* Windows: XP SP2 or later; Mac OS X: Intel CPU & "Leopard" 10.5 or later. Note that Unity was not tested on server versions of Windows and OS X.
* Graphics card with 64 MB of VRAM and pixel shaders or four texture units. Any card made in this millennium should work.
* Using Occlusion Culling requires GPU with Occlusion Query support (some Intel GPUs do not support that).
* The rest only depends on the complexity of your projects!.

System Requirements for Unity iOS Authoring:
* An Intel-based Mac
* Mac OS X "Snow Leopard" 10.6 or later
* The rest only depends on the complexity of your projects!

System Requirements for Unity-Authored Content:
* Windows 2000 or later; Mac OS X "Panther" 10.3.9 or later.
* Pretty much any 3D graphics card, depending on complexity.
* Online games run on all browsers, including IE, Firefox, Safari, and Chrome, among others.

It seems the only compatibility issue is with IOS Authoring, which I doubt you used (that's for porting to iPhone). It seems though that Leopard is the limit for unity authoring.  Another line is the occlusion culling, which seems not to be supported on some Intel GPU (if I remember well, first intels in the macs were not supporting this) ). I don't know if you use this in the game though.

[x4000]

Per our system requirements, anything 10.3.9 or newer should work.

[sickboyedd]

Just to say, got the same problem, running 10.6.5, 4GB Ram, Macbook Pro. Going to try reinstalling it via Steam, but at the moment it just crashes on startup.

[x4000]

Did that do it?

[sickboyedd]

Ah, sorry, didn't work. I also tried verifying the files via Steam but nothing missing/corrupt. Likewise, opening the package contents and running it from there didn't work. I've attached my crash report, just in case it's insightful. Will try downloading the demo and seeing if getting from somewhere other than Steam helps...

[x4000]

Hmmm... did it log anything in your RuntimeData folder inside the game folder?  If it's a crash that happens after our code is actually initialized, that would have left something there.

[sickboyedd]

Hi. I just installed the demo independent from steam, got the same launch error. Nothing appears to get written to the RuntimeData folder either, in both Steam and non-Steam versions.

[x4000]

Hmmm... that's a new one on me.  My guess would be that there is a driver messed up or something along those lines, in that case.  That's something one generally sees more frequently on PCs, but it's definitely possible on a Mac, too.  I seem to recall hearing that there were some recent drivers by nVidia that were causing problems in various games.  I'm not sure if there is something newer out that fixes that, or if one needs to revert to something older than that, to solve it.

Info on your machine specs would be helpful, but based on the crash report it's not really giving us any useful information other than it dies before it really even gets a chance to start.  It's not even running our code yet (hence no errors logged in RuntimeData), it's just dying while the Unity 3D engine that the game runs on tries to start up.  My best guess would be that it's dying during the OpenGL setup step, but that's just as guess as I don't have any insight into the inner workings of Unity 3D (it being closed source).

Hopefully either a driver update or an OS update would fix this (I seem to recall their being some updates recently that were supposed to help with graphics performance, so maybe that's part of this problem).  If that doesn't seem to do it, though let us know.

[sickboyedd]

Just tried it on my work Mac desktop and it works fine, it having an ATI card. Are there any people out there who have managed to get it running on the stock 13" Macbook Pro (mid 2010 model)?