<h4>Learn the differences between the update methods in Unity, as well their appropriate use-cases.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JYUlKD8xr-5tATnk" /><figcaption>Photo by <a href="https://unsplash.com/@hellolightbulb?utm_source=medium&amp;utm_medium=referral">Hello Lightbulb</a> on <a href="https://unsplash.com?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Perhaps, you’ve recently piqued an interest in developing games using Unity and you’re seeking clarity on the various Update methods an object can be scripted with. Or, maybe you are an old-timer looking to refresh your mind on the basics.</p><p>Each of the update methods are specially crafted to optimise performance. In this article, we will learn what these methods are, and how they’re designed to be used.</p><h3>Update</h3><p>This is called once every frame, <strong>regardless of the time difference between frames</strong>. So, if you target 30 FPS (frames per second), the Update method in your script will be called 30 times within a second.</p><blockquote>Typically, you would use the Time.DeltaTime to calculate the time between the last and current frame.</blockquote><h4>Use-Cases of Update</h4><ul><li><strong>Input controls</strong>: Updating an object based on the user’s input</li><li><strong>Transform changes</strong>: Making changes to the transform properties (ex. rotation, scale, position)</li></ul><h3>LateUpdate</h3><p>Think of this as an “OnUpdate” callback (kinda). All LateUpdate methods are invoked after all Update methods in the project have been invoked.</p><blockquote>If you have logic that depends on the latest state of some other object/prefab, you want to have this logic inside LateUpdate.</blockquote><h4>Use-Cases of LateUpdate</h4><ul><li><strong>Camera movement</strong>: In most third-person games, the camera movement tails the player. So, you want to update the camera’s position after the player’s position has been updated.</li><li>Updating an object based on the latest properties of other objects.</li></ul><h3>FixedUpdate</h3><p>This is distinct from the other two methods, because it is framerate-agnostic. It is invoked directly by Unity’s physics engine in its own interval. If you have any physics-intensive logic, FixedUpdate is the appropriate method to place them.</p><h4>Use-Cases of FixedUpdate</h4><ul><li><strong>Invoking Rigidbody methods</strong>: Using Rigidbody is one of the easiest ways of having an object’s motion fully controlled by Unity’s Physics Engine. So, the common interactions with the Rigidbody (ex. AddForce(...), SetDensity(...), etc) should be done from inside FixedUpdate.</li><li><strong>Cloth simulations</strong></li><li><strong>Collision detections</strong></li><li><strong>Ragdoll character physics</strong></li></ul><p>If you liked this article, clap, share and subscribe.</p><p><a href="https://tomisin.dev/subscribe">Subscribe * Tomisin Abiodun</a></p><img alt="" height="1" src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=d0fb220d289a" width="1" />

Learn the differences between the update methods in Unity, as well their appropriate use-cases.

game-development

Unity: Update vs LateUpdate vs FixedUpdate

Get one coding trick and an article delivered every week at no extra cost