Let me first state that so far I’ve been impressed by Unity3D in my trial period and me and my team will most likely be licensing the engine.
However, we have encountered yet another (the third one alreadly) bug that only occurs in the web player or stand alone application and is not visible in the editor when we play.
We have fixed the first two but are very much stuck on the third bug. Which involves the player hitting a trigger which causes an AI agent to run towards another node in a path. This works perfectly in the editor - but not at all in the build. By not working I mean it doesn’t crash but the agent stands in place instead of running away.
The debug console displays no warnings, errors, or what not in the editor despite extensive attempts to make it occur. So what I need know is to know is there some method of making the editor behave -exactly- as the build and / or display warnings about things that might result incompatibilities. Or any other help in debugging these issues.
Also we are facing a bug where Time.deltaTime seems to be zero for extended periods of time. Example:
zSpeed = inputLeft * moveSpeed * Time.deltaTime;
Results in no movement - no matter how much inputLeft and moveSpeed are tweaked. Simply removing deltaTime fixes the issue but that is obviously not what I would like.
Any advice would be greatly appreciated as these issues are greatly affecting my opinion of the otherwise fantastic engine.
-BenV
[Edited to be more clear]
