- Home /
Update() calls start several seconds after launch
I created a simple GameObject with both a FixedUpdate() and an Update() method.
When I run my game, FixedUpdate() starts getting calling immediately and I can see its changes in Unity's inspector.
However, Update() does not get called at all until about 5-8 seconds in. From then on, it's called regularly per frame and does its job.
Why is that so?
It's not so; the first Update call is immediately after Start. I would guess you're misinterpreting the results somehow, but I don't have enough info about what you're doing to say anything more specific.
Provide the code that appears to be exhibiting this behaviour and we may be able to find out what's going on. Eric's right: you must be misinterpreting your data in some way.
You are right. Update() is being called (just tested via Attach to Process from the $$anonymous$$onoDevelop debugger), but the changes I apply to my bone transforms in Update() aren't reflected in the view until several seconds after the application started. I posted the code I'm using in my blog: http://blog.nuclex-games.com/2012/03/islandwar-animating-turrets/
Your answer
Follow this Question
Related Questions
Frame dependant game. Using update vs fixed update. 3 Answers
What causes long delay after hitting run in editor, how to reduce it? 0 Answers
FixedUpdate limits: consistant 0.01 s on mobile devices? 1 Answer
run code once every 10 second 1 Answer
Exact difference between fixedDeltaTime and deltaTime? 3 Answers