[OSX] Cannot start the campaign.

Avatar
  • 已更新
  • Completed - Resolved

I am on a macOS Sierra iMac Late 2013, and I cannot start the campaign.

It pans to some textures once i click "play" and it makes a wind noise. Any help?

Game Version:
Steam Public
Platform:
OS X
重复 2
OS X graphics artifacts & crash

Hi,

I'm on OS X. Here are my specs:

Image 2156


I remember playing the game and the Heart of Gold Expansion on 10.9.5 and everything worked perfectly. I recently updated to El Captitan and saw the new Crucible Update and was very interested in trying it. When I launch the game I get weird artifacts on my screen:



Image 2157


After a few seconds everything is back to normal. I decided to play the campaign again but when I launch the first level (1 - Awakening) the game just gets stuck and all I see is:



Image 2158


and a short part of the audio is looped. I tried to disconnect my secondary monitor because I read this might help but it basically leads to the same issues I described. I'm including my log file Player.log


Hope this can be fixed soon


Best Regards

Marcel Schulz

Game freeze when starting campaign mode (OSX)
Avatar k r

Game freezes when starting basegame campaign mode getting stuck on what I believe is an introduction video(?) (see screenshot below) and has to be forced quit. Sound is also getting stuck in a stuttering loop.


Game is working in other modes (skirmish etc), as well as the DLC Heart of gold campaign mode.


I've tried:

* rebooting computer

* reinstalling game

* verifying cache (steam)

* playing in windowed and fullscreen modes as well as trying different graphics settings


Computer specs:

Macbook Pro (Retina, Mid 2014)

OS X El Capitan 10.11.6

2,5 GHz Intel Core i7

16 GB 1600 MHz DDR3

NVIDIA GeForce GT 750M 2048 MB


Build is 1.5.0f10


Player.log


Image 2230

Pinned replies
Avatar
anonymous
  • 解答
  • Completed - Next Patch

Hey all, 


We will be pushing an update in the next few days which has fixed this issue. Please get back to us once you have updated if you still experience the crash

Avatar
Stefan Furcht Programmer

Sorry the button I mentioned is only available in Heart of Gold campaign view in case you own it.
Would be interesting if this one causes as well a freeze or if it is limitted to the main campaign cutscene.

Avatar
Stefan Furcht Programmer

Thanks for being understanding.
Then the way to go is introducing a way to disable cutscenes for now.
Can you just make 100% sure this is the root cause by confirming that clicking on "Replay Intro Cutscene" in the campaign menu view causes this freeze?
We are going to add a cutscene skip command for next hotfix, which hopefully will allow you to play campaign mode.

Avatar
k r

I was actually looking for "skip cutscenes" in the options before I submitted here; I wouldn't mind playing without them.


Thanks for swift replies and for your help!

Avatar
Stefan Furcht Programmer
  • Accepted

It's a bummer all three Player.log files look exactly the same.
All is fine, no errors and then suddently "Receiving unhandled NULL exception" which does not help.

It seems we will have to contact the support of Unity Technologies for this one, which means it could take quite some time to get this sorted.
If you not want to wait longer for a fix and just recently bought the game, then it is possible to refund it on steam store if you are less than 2 hours into the game.

Otherwise it will take up some time to get this sorted out I fear.
We could look into a way to disable cutscenes entirely by introducing a special command though,
but this could only be a temporary solution and finally you want to see the cutscenes as well.

In Unity 5.6 they are changing how cutscenes are integrated totally which will likely reduce issues caused by them especially on non-windows platforms.
But it's still some time to wait before this technology becomes available to us.

I am sorry, that we are unable to help quickly on this this problem.
Thanks for reporting and sharing your logs.

Avatar
k r

Hello

Thanks for a fast reply :)

I tried skipping with space but no luck I'm afraid; the freeze seems instant the moment I press "play".


I'm attaching two new logs - hope you can find something useful.

Let me know if you need anything else.


Player.log

Player 2.log

Avatar
Stefan Furcht Programmer
  • Under Review

Hello K.r.,
Sorry for such troubles, the log shows indeed a crash but Unity3d (our game engine) was failing on reporting any pointer for the cause.
All we got is:
Receiving unhandled NULL exception
Obtained 16 stack frames.

Which does not help to look for any cause.

Can you trigger the problem again and try to upload another Player.log?
With some luck next time we get a more decent stack trace.

Is it possible for you to skip the introduction video by quickly pressing space bar?

I hope it is not a general incompatibility issue.
However the way video scenes are put into Unity3d based games will change drastically in Unity 5.6
and I hope it reduces issues caused by cutscenes.
But till then there is still some time to wait.

Avatar
Lee "Noontide" Moon
  • Pending Customer

Best of luck, let us know how you get on. If you still have issues we'll try to remember to let you know as we update Unity that might help fix the issue for you.

Avatar
Marcel Schulz

Ok thanks for your help. I already have like 30 hours in the game so I can't refund it. Maybe I'll try to play it in Windows 10 with BootCamp.

Avatar
Scott Richmond Programmer & Producer

Thanks. I can see a number of problems occurring in the log there. However they are very vague and do not appear to be caused by our own code. I suspect some kind of hardware incompatibility between your hardware and the 3D engine we use (Unity).


Unfortunately I cannot provide any immediate steps to resolve this for you - It works on all the OS X hardware we have here. It may be resolved in a patch or two, however I understand that you may not want to wait that long and so I would suggest that you request a refund through Steam to get your money back.


I'm really sorry I cannot assist you immediately. We'll keep looking into the problem regardless. :(