Can you tell me what you were doing at the time when the crash occured?

Great to hear that Raul. If you have any issues let us know! :)

That's alright, best of luck!

It's not an ideal answer but if you can free up memory when WFTO is running you should be able to progress. Just be aware of course to be very cautious on the heavier levels, particularly when saving because it's a very memory intensive task.

A long term solution would be to invest in more RAM, at least double what you have now and of course you'd have to move to a 64-bit OS to make use of that.

I'm going to mark this as complete for now but do get in touch if you need more insight from us.

Cheers,

Lee

Thanks for the report. We're currently on XMas leave right now but we'll be sure to investigate further in the new year! :)

Sorry to hear about the crash though, Unity can be a bit flakey with Intel chips which is why we don't officially support them. I'll be sure to get this passed straight to code and they'll be able to respond next year with any thoughts.

My only input would be on a comparison of G3D Mark the Intel Iris 550 is just within Minimum spec for the game.

It'd be great if you could locate your player.log and get that uploaded direct to us here as well as your full specs for your Mac. :) Plus some extra insight on what was happening at the time of the crash would be great as well.

How to: Submit a Bug Ticket

Thanks for the report. We're currently on XMas leave right now but we'll be sure to investigate further in the new year! :)

That's strange though, the objective seems to have progressed but the shield is still up, how bizzare. Thanks for the save file if you've got the chance and haven't loaded the game since you might still have the output log as well which could be handy if you could upload that.

How to: Submit a Bug Ticket

Thanks for the report. We're currently on XMas leave right now but we'll be sure to investigate further in the new year! :)

Should hopefully be a quick fix on this one, took me a moment to notice the typo. "Imprerial" instead of "Imperial"

Thanks for the report. We're currently on XMas leave right now but we'll be sure to investigate further in the new year! :)

I took a quick look through the log and didn't see anything major standout, but the coders have much better eyes for that than I do.