If any representative from Unity is listening, pretty pretty please patch this bug!
Here's the update that I received from our CTO:
"I interviewed someone yesterday who said he ran into exactly the same problem that we did. Even more telling, I had a phone conversation with someone at a game development studio called ******* (they did *******, among other games; there are approximately 60 employees there) and they have not only run into this same problem (although in their case it was using Unity with Perforce) but also, in conversations with Unity about the issue, were told that Unity is working on fixing the problem."
I can't find any public comment from Unity on the Bug... Anyone?
No comments:
Post a Comment