|
But if I set it to start in 0.0001, it works fine. What is going on here? Here's the test script I noticed this happening in-
(comments are locked)
|
|
But if I set it to start in 0.0001, it works fine. What is going on here? Here's the test script I noticed this happening in-
(comments are locked)
|
Once you sign in you will be able to subscribe for any updates here
By RSS:The best place to ask and answer questions about development with Unity. Check out our FAQ for more information.
To help users post good questions and use the site effectively we have posted a tutorial video. Please check it out.
Topics:
asked: Apr 29 '12 at 05:57 PM
Seen: 395 times
Last Updated: Apr 30 '12 at 01:42 AM
Early? What does the output look like? Is time not showing roughly 0,4,8... ?
As for the incTimes, since they wrap around every 4, and you print every 4, the values should "randomly" be 0 or 4 (depending if it prints just barely before or just barely after each wrap-around.)
A delay of 0.0001 is really 1 frame, so it would make sure you print times just after each wrap-around.
Nope- try it- it's going 0, 3, 7, 11, 15 etc. The second time it invokes, it jumps the gun by one whole second, and remains 1 second behind what it should be, forever after that.
No decimals? Debug will do some rounding. As a trick, you can print
Time.time*100to see more decimal points.