Your comments

Needs more information:


  • How many other units did you have
  • How many gateways did you own
  • What was the size of each Garrison

Looked into this.


Essentially when a 3x3 Garrison is created an augre will be attracted, however the room displays that it attracts 0 units at this size. Likewise two 3x3 Garrisons will attract 2 augres but both will only display a maximum of 1. If the maximum units attracted is zero then the attracted number will be in black.


Rep steps:

1. Start Sandbox

2. Create a 3x3 Garrison

Replication Steps:


1. Start Level 6

2. Convert a tile in screenshotted area

3. Drop workers in.

Replication steps:


1. Start C6

2. Reveal FoW

3. Clear out units in area

4. Convert nearby tile to player faction

5. Drop imps

6. Await slaughterpen capture

My workers behaved differently here, choosing to flee. I suppose they're fleeing from units on the other side of the door, unless the door itself has a threat value.

Confirmed on Level 6, after the screenshotted slaughterpen is captured.

@BouncingCzech

@Leo85


Hi Guys,

It's possible you're suffering from an unrelated but similar issue that has occured since Patch 1.4.2 was released (a fault in Unity causing some save games to become unload-able for some reason)

Have a look at this thread and see if it sounds familiar.


If it is related to that you might find the Previousbuild branch could have a temporary workaround.


Unfortunately I don't think there's much we can do with the op's corrupted save file and the cause is unknown. Based on Stefan's response I'll be closing this topic as it doesn't appear further issues have been suffered. But if anyone else has a similiar issue please do get in touch with your save file and logs etc. and we'll look into it.


Cheers,


Lee

Is it possible that these units were ranged units that were being chased by melee units. The AI of ranged units is set to try and keep distance so that threat from enemy is minimised, so they'll attempt to kite enemy units.

Hi Anthonypmarino,


I've merged your thread into a related thread. To catch you up, we've identified a fault in the underlying Unity engine that is causing these issues. We've contacted Unity for their assistance in resolving this matter.


There's a potential workaround that might help you if you have a second monitor attached some users have reported that detaching this from their Mac has allowed the game to run. I'd advise giving this a go while we wait for a response from Unity.


We're also expecting the next patch (likely a hotfix) will be using a new Unity version and if things go well we may roll that onto a seperate public test branch to see if it also solves the mac issue. I'll keep you posted.