Hrm now we will get another patch soon.
Just let us know how it goes, but at some point we might close this ticket if there are no further reports that point out this issue would be still a thing.

Cheers

All fixed, thanks for reporting :)

Nano Boucher I was able to reproduce that all units disappear after some minutes into the north western gateway but do never respawn.
Can you take a look why MQ fails here?
Cheers

Hello knightenterprises,

I did load your savegame and I can confirm that all enemies in the lane run into the north western gateway but do not respawn again.
So the issue can be reproduced and should be fixable.

I am sorry no one replied to you in the last two weeks.
This happened because the ticket was not changed from "Pending Customer" to "Accepted" after you replied and thus it was not realized internally and thus got accidentally ignored.
Normally the ticket state is switched when the user answered but this time it didn't work out unfortunately.
I will now accept the ticket again and make sure it is looked at soon.

Thanks for reporting bugs! :)

We also found a memory leak in current Unity version which doesn't free memory of a scene after it is unloaded.
So when you play many levels in a row it can eat your entire memory.
The issue is fixed in Unity 5.5 but it is still in Beta and we don't want to update before it is through all quality assurance.

Yes the player hand is a 3D object.
What you mentioned are all non trivial solutions and more a feature request than a bug report.
We experimented with this before but it had drawbacks, eg. you don't see what is in your hand anymore when you zoom out too far.
So we thought the current behavior has the best tradeoff between accuracy, visibility and simplicity.
So now I am unsure what to do with this bug ticket.

Let us know if there is a high memory usage (> 8GB) before it happens.
If so it might fix it self with Unity 5.5, however it is unsure if it will be ready when we release the next patch version 1.5, but if not it will be patched into version 1.5.1.
if its unrelated to the Unity memory leak we need to investigate further to find the cause.