You Are Using Update Loop Wrong | Practical Unity Tutorials 

During my early Unity years, I challenged myself to create modules without using "Update" except when you need to accept Inputs from the user. This is something that I still follow and have also taught this to many of the junior devs in my company. It's almost always part of my TODOs for writing any thing. Events are the best.

I've always done GetComponent just once in Awake() or Start() and assigning it to a variable within the object. Never thought of just dragging the reference in the Inspector, but good to know.

My friend, your audio only goes into my left ear.

The only thing you should do each frame is listen for player input. Everything else should be event based. Send out an event (I like Action/Func), and whatever system interested in knowing can subscribe to that event.

Man, this video is just insane, thank you so much. I subscribed.

My left ear enjoyed this

This was an awesome video! Can't wait for more, specifically on coroutines!

Man, please never leave youtube, my game fps gone from 15 fps to 144fps (monitor max fps), thanks 💯

thanks for the advice, very useful!

Thank you ! your way of explaining is very soothing and easy ! THANKS

Svaka cast! Ovakvi detaljni tutorijali su nam potrebni! Kada sam poceo game development, moja prva prosta android igrica "Falling blocks" je jedva radila na telefonu upravo zbog lose optimizacije! Ali godinu dana kasnije, sa zavrsenom IT akademijom i dobrim znanjem C# jezika, sada svaka igrica radi u 60+ fps

I like your presentation. The only one I truly understand. Please keep these coming. Subscribed, and liked all of your posts.

Just the kind of content I was looking for!

This is really great information.

Join our discord community and get the best Unity tips discord.gg/4CqnGESuRn. And sorry for the audio.

nice content, you got your 1000th subscriber 😁

your voice is entirely only on the left audio channel...

Instead of checking for if enemy is dead you are checking if projectile has hit.

This video feels like a marvel henchman is menacingly teaching me C# instead of interrogating me lol

You have to be careful with OnTriggerEnter or OnCollisionEnter too. And don't forget about the collision filter. What can you say about UniTask? As an alternative to updates and coroutines? Suppose we run a UniTask loop with Delay Frame(120) or just Delay(seconds) So that the check does not take place every second, but only a certain number of times per minute?

Great video, I have subscribed.

My left ear enjoyed the video

is doing some thing like decreasing the amount of times you want to call your function in your update with some cooldown using X-=time.deltatime bad?

Around 6:30 you say that update loop can only be disabled when game object is disabled, which is not true at all. You can disable individual components using Behaviour.enabled property

Hey, what’s the AR game you showed a clip of here?

That is a cool AR game.

At the beginning u felt if i didnt hand over ten k i was going to my knee caps slapped. So i subed instead

When I really need to make check in update. I will always go for fixedUpdate and if I can go even lower I will create a slowUpdate I only call 4x per second for some AI check for example and when they are out of the camera bounds I disable them. No one notice the difference in game except the fps.

Great video again ❤

very good content!

Coroutines are easy but you need to be aware how many times you are calling it, I often find myself in situations where my coroutine is getting called multiple times which results in erratic behavior and I spent hours figuring out what is wrong.

Thanks for the video man.. (The sound was a little off coz your voice came only from the left speaker, just a notice) Waiting for more informative videos ;)

Great video, great tips. Good job. Here's something else I like to do, maybe worth a try sometime. Good for performance, code readability, portability and coder sanity. In a monobehavior sub-class definition that I know I will need to call many of, often, I'll create a static list of the class within its definition. then OnEnable, instances of that class call a static method to register themselves within that static list if they don't already exist within it, and the app is running. and OnDisable, they unregister themselves under same conditions. Then I have one static 'UpdateAll' function that iterates through the list and updates them en masse, and as much as possible, without calling specific functions within the class implementations. Then once - per -often, i call TheClassName.UpdateAll(), and if any are registered, they update. This seems to speed things up quite a bit, even though internally it's probably very similar to what Unity does under the hood, I suspect there's added expense with the standard way from context switching or something, thread allocation who knows.

Thanks a lot for such great content, mate! Sub!

Science you explain you can also explain about FIXEDUPDATE You are the first one I finally got to understand thank you

i really dont like to put anything in update and i try avoiding the most but sometimes im just not sure how to update a value without a start point, but as you stated, events is good to go

Coroutine: be aware that this is not multi-threading. The coroutines still run on the main thread, just making it easier organize code that should run for a specific time. But its not optimizing CPU core usage.

good one..

Subbed

cool... like

RIP my left ear

Bros been insulting everyone whos looking at the thumbnail

let me guess you will talk about fixed update

You seriously need to check the audio using headphones when editing your video.

Umh, I think you really scratched the surface here. Okay, those 3000/frame checks will take some time, but its not the most important thing here. First of all, you need to learn habit to periodically check for stuff that is less important. For example, enemy can check for path to your player every 0.25 or every 0.5s or so. Promity check does not need to fire every frame, it can five every brief time, like 0.1s. But the most important is that every Update() call comes with a cost even if its empty, due to Unity costly marshalling operation. So instead of having 1000 entiteis with Update() loop, its actually much much better to have one object that iterates over list of 1000 enemies and manually calls method that updates logic (this pattern also makes easy to include levers how often you need to timeslice that particular entity type).

Mate you recorded your video mono, its pretty hard to listen to you. Still, the topic you talk about is a really nice one.

I cannot feel my right ear

Ähmm, even 100 000 checks per second is nothing. This is not where the bottleneck typically is for a Unity game. What is expensive are api calls.

I quit unity then i moved to defold engine 2d and 3d lua ggame engine.

Audio only in left ear, can't watch.

Well, very bad video that will lead you to the wrong way.

I disliked in first milisecond.