"We add empty functions Start and Update for you - just remove it" - Unity

Awesome useful video. Have already watched tons of optimization videos before but some of tips were really new and useful. I need hundreds of such tips xD.

A must watch for every unity game developer! Thank you.

This is great, thank you for this. Please make more videos focusing on performance

please also a advanced session about garbage collection.. nice talk by the way

A note for myself: - Functions use the stack, fast, Class instances use the heap, be careful - If you have lots of objects, use a scriptable object to save shared properties - Choose the correct data structure - Use object pooling, decide how big the pool is - Properties (those with get and set) have an overhead, prefer just using fields aka variables, as shown here - Use the addressable asset system, since the resources folder slown down load time - Remove empty events when not using them - Activate or instantiate objects after the first frame, sine you might have too much things on start() and awake() - 22:33 When you change something using a string, compute the hash - Avoid complex hierarchies in your scene tree - Disable the accelerometer if not used - Move rigid bodies with their methods in fixedUpdate()! - Cache your references if you need to use thigns like Find()

Hi. This series is something much needed, thanks a lot. With respect to the recommendation about using preprocessing directives to eliminate properties: I had the notion that this kind of simple properties were inlined by the compiler in non-editor, or at least non-debug, builds. Why do why need to use this kind of tricks? Are this kind of properties not usually inlined? What about using AgressiveInlining with the MethodImpl attribute, would that make them be inlined?

T.Y. this what I'm talking about. Useful uploads, big time.

Thanks a lot, this is fantastic tips!

A lot of these tips i knew were good practice but i didnt really understand *why* before watching this video. Thank you very much for the presentation 🙏

Never thought that scriptable objects are can be used to save memory. Thank you for your kind effort!

This is a great video! Absolutely everyone who writes code for Unity should watch it!

UNITY IS GONNA REACH 1M SUBSCRIBERS !

Very useful Thank you!

Thanks for the video. Would it be possible to share the presentation? There are some really good examples.

What a fine explanation of stack and heap memory! Thank you for the good clarification. I m loving it.

yes, please !!

Good but basic stuff. I'd like to see more advanced tips regarding performances.

Nice presentation 👍🏾

I have a question about Transforming objects. If our rigidbody is kinematic, which class should I use to change position, Transform or Rigidbody?

Please do in depth presentation for these with best practices! thank you.

Can you guys do one on physics optimization? I can't quite grasp what the performance hit of rotating a rigidbody's transform is.

Super interesting video. Unfortunately, certain subtleties of the English language have left some areas of fog ... This is why I thank you warmly for using a presentation, which made viewing easier. I look forward to a sequel.

Is there an overhead of a complex hierarchy even if we don't define a method OnTransformChanged in our components ? Isn't the matrix of a Transform flagged for recompute and only recomputed if we access it ?

26:27 so if i want to rotate or move "RootGameObject" then it will affect gameobjecta and gameobjectb right ?

I would like an in depth/ practical example of getter/setter optimization. How much up a real performance boost are we talking? Are we talking better memory management or reduce load?

thank

Awesome

That hashing part caught me offguard. ;w;

What is addressable assets?

Aren't properties with no code automatically optimized by the IL2CPP pass & subsequent C++ optimisation ?

While these are very basic tips, I don't quite understand the need for ScriptableObjects in that particular case scenario if you can use static variables. Do static variables make copies of themselves for each instance? Same goes for consts.

Nice

Thxxx

Can we get a summary slide?

Explain that you're a 'game evangelist' to my grandparents. I dare you.

Is the stack and heap just a logical construct by the operating system or the compiler, because on a hardware level surely all the memory space is the same, their isn’t different types of memory cells in the memory sticks is there?

Why are you using new + destroy functions in GC example? Afaik It is never used this way. This example can confuse new unity learners.

2:06 mounee? What's that?

The second last advice is NOT right. Sometimes adding and removing a component is THE ONLY WAY to avoid it having an impact on other systems, even when diasabled, EXPECIALLY for a rigidbody!!! Absolutely not agree on that 🤔 ( Maybe to advice having 2 verions of the same object pooled, one with and one without the component .... that is good advice)

Nice