by Ricardo Teixeira » Wed Feb 25, 2015 5:46 pm
Hello Eric,
Thank you for reporting the problem. The issue is caused by an outdated Shader in the publicly available AT2 package.
We have been playing catch with the Unity developers in the last couple of weeks with all the updates but it's finally becoming more stable; this issue should be less frequent after U5 is released. We are about to release an AT2 update that will ensure U5 RC3 compatibility, I will let you know as soon as its available.
By the way, I replied to your earlier email and added you to Skype, looking forward to our talk.
All the best,
Ricardo Teixeira