Unity Performance Tips: Draw Calls
ฝัง
- เผยแพร่เมื่อ 20 ก.ค. 2024
- A short video on how to improve your frame rate in Unity. This video covers various optimizations to reduce draw calls such as combining meshes, batching and gpu instancing.
Music Credit: LAKEY INSPIRED
Track Name: "The Process"
Music By: LAKEY INSPIRED
Official SoundCloud / lakeyinspired
Official TH-cam Channel: / @lakeyinspired
License for commercial use: Creative Commons Attribution 3.0 Unported "Share Alike" (CC BY-SA 3.0)
creativecommons.org/licenses/...
Music promoted by: Chill Out Records @ goo.gl/fh3rEJ www.ChillOutMedia.com / www.LoFi-HipHop.com
Music Credit: "KaizanBlu"
Track Name: "Remember"
• Instagram - / kaizanblu
• SoundCloud - / kaizanblu
• Facebook - / kaizanblumusic
• TikTok - @kaizanblu vm.tiktok.com/aCYwfx/
• TH-cam - / @kaizanblu
Licence: Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
• Music released by: Chill Out Records goo.gl/fh3rEJ @www.ChillOutMedia.com / www.LoFi-HipHop.com
I was always so worried about poly count, always trying to keep it to a minimum, but I love it that in this video you went from 0.5 FPS to hundreds without reducing a single polygon, always kept with those 21M.
There are various bottlenecks to be aware of, polycount is still one of them, but the aim is to solve the one affecting your particular situation.
@@Domarius64 why not apply all of the performance techniques at once? As soon as you solve the original problem, shouldn't you apply the other techniques?
@@xomvoid_akaluchiru_987 if you have infinite time, sure, you can do everything. But in the real world you are always making trade offs to get something produced in a way that still turns a profit.
@@Domarius64 Ok, time constraints, sure, but if a product is finished and you're coming back to fix some things then I don't see why implementing all of them would be an issue if the product really does benefit from it. If it doesn't benefit much then I just trust myself to have common sense and see that it's not worth it.
@@xomvoid_akaluchiru_987 that "extra time at the end" literally never happens in game dev :) you always end up releasing the game when its good enough, not because its finished, because it never is. And so you cant justify spending time on things that have no tangible benefit - remember, you said "why not do all of them?" Well, thats why not. If the game runs on the target hardware acceptably, there is no reason to optimise. Plus when you say "why noy do all techniques" like there are only 5 or something. Every different programmer could know any number of techniques they learned about somewhere, too numerous to list, you cant just "do them all".
And more importantly, those changes will not have zero impact, there will always be knock on changes related to that, and plenty of opportunity for new bugs to be introduced at every step of the way, all which will have to be fixed, taking even more time. If its working, you leave it alone.
The best Unity Performance tips on TH-cam ever
indeed
Great overview. I liked how you you showed multiple levels of improvement and how each setting improved frame rate and batches 👍
This will definitely be added to my greatest-unity-tutorials-of-all-time list.
You single-handedly saved my project. I went up from average 28-30 fps to 160 lol. Thank you so much
How are you doing mate? Is your game realesed yet?
Okay these are some really good tips explained very well and I absolutely love the cat at the end!
These are very professional and excellent quality tutorials. Keep up the good work!
Helpful, concise, and clear. Thank you for taking the time to make this video.
Conscise, precise and short. Sir, you have mastered the art of tutorials and I am eternally grateful!
the simplest and most understandable video on that topic thanks
This is so well explained. Great video!
Great work, the overall quality of the video is really high, please continue :)
i love these short concise videos full of great info, thanks so much
Great overview, quick and to the point, thanks
Short and clear. Nice vídeo man
Awesome video thank you bro. Loved the visuals and explanations. I now know exactly what I need to do for my use case.
This video is a gem, small but extremely valuable.
So much good information in such a short video. Just wow.
I CAN'T EXPLAIN HOW EFFICIENT IT IS!
THANK YOU!
Really nice, tutorials for enhance the game performance is one of my favorites, very useful!
Thank this is amazing I've been looking for something like this for a while now!
Quick and accurate! Great video 👍
i learnt more with your video than a lot of time on unity docs and asset store...thanks a lot perfect explanations
thank you for this! so much info in so little time
This was really cool, finally got to know why batching
Nice thank you, this is very clear, easy to understand and successfully removes doubts on the subject.👍🏼
Great tutorial! Very underrated channel in my opinion :)
Thank you so much, my game had a lot of belts in it and this was a great way of cutting down usage
Very clean and easy to understand.
very well-explained, thanks for the tips!
Dang I had no idea this was even a thing! Fantastic tutorial
Great tips! Thanks!
Woah nelly this is going to be so useful.
It's men like you that make the world a better place, I watch tons of videos on the same thing but you broke it down simple and easy to digest.
Incredible video, thank you so much!
SO USEFUL THANK YOU!!!
The only good video about batches on youtube
Nice tips, 800th subscriber. :D
thnks dude! powerfull information 👍
Thank youuu, I needed this soooo much for my mobile app! So, thank you ^-^
i wish i saw this video months ago, great advice!!!
Absolutely fantastic. I had no idea that marking an object as static actually did anything without scripts or rigid body’s applied to them
Really cool, thanks!
very informative, thank you!
Very good and helpful! Thanks!
Very important and very helpful lesson.
Very clear and helpful vid! thx!
That is brilliant. Finally, I understand!
What a nice tips! gonna try it
Thanks for clear explanantion!
short and informative
thanks!
Very intuitive instructions 10/10
ngl that funnel animation was mesmerizing asf 🤤
Great video! Thanks-
Thanks. This is insanely helpful.
You accidently exolained what happened to my scene. Ty I got it ans will make use of it ❤
Thanks so much for this video
wow this was informative! thanks a lot
Back after lots of months and now i understand
Been making jam games in unity for 2 years now, did not realise how important the Static tickbox was. Never used it before, changing that now!
Very well explained!
insanely useful considering i was using multiple materials for flat coloring instead of just using a texture.
Perfect tutorial
This is a very nice format to explain performance though: gradual improvement.
Loved it !! when i was about to upload my game i searched this and all the top results were just making the game look like potato 🥔 and today i found this video :) honestly TH-cam should push this video more...
Thank you, keep up the good work! :)
Nice vid, thanks 😊
you saved me. thanks man!
hatur nuhun bang. ilmunya mudah dipahami dan singkat
This is optimization-heaven
Awesome video, short, detailed with very good explanations and demonstrations, great job ! I have a question, for the GPU instancing on the material. We see in the video all building moving but how did you do that ? I suppose it thanks to compute shaders or by C# script ?
This is amazing!
GREAT VIDEO MAN
Awesome Tutorial
thx! Usefull video!
Please make more videos about optimizing your games to make them run smoother, thank you
Btw. GPU Instancing will NOT work, if you have enabled SRP Batching in the Render Pipeline Settings. The SRP Batching is also better in performance reasons, because your gameobjects do not need to share the same Mesh/Material.. just the same Shader.
I’ve never tried to measure the difference in performance by myself. But according to what people write at Unity forum, SRP batcher is generally slower than static batching. It has less memory footprint and easier to use though. And in some cases GPU instancing may be more efficient than SRP batching. In case of dense grass field made of 1 instanced mesh, for example.
Thank you man i wish if i saw your video before now
Thank you for the guide! Super easy to understand, entertaining, and you have a sexy voice. You have it all man keep it up!
Thanks this means a lot to me when I am developing on a Intel i5 2gb gpu appreciated
thanx for these tips
Awesome video 👍
Totally awesome channel !!!!!!!💥💥💥💥💥💥💥💥
Tysm, you deserve 1k Subs :)
awesome!
Best 5 min ever spent!
Great help!
the ultimate guide to go from seconds per frame to frames per second.
Thanks, REALLLLLY THANKSSSS.
Thanks man! ~!you LEGEND you!
Thank you for such a single explanation. Amazing! I do have a few questions though,
1. How much duplicate objects with the same mesh, materials and settings?
2. Are duplicate objects different draw calls?
3. Are duplicates affect the CPU/CPU in the same way? For eg. two buildings with different materials which has the same mesh and two building with exactly the same mesh and material.
4. What about complex meshes? What is people just use this technique on a mesh which is complex?
5. What if I mark an object Static and turn on GPU instancing?
6. Also, fbx vs obj in this case?
Well, make a PREFAB of any multi-duplicate object you are planning to use. So 1 object with it's material(s) for ex. (note: prefabs can be a parent object with "nested child objects" too)
Set it correctly, (Optimizing/combining, Static or GPU instancing) and use that prefab to build/compose.
Make a second prefab for the different materials using the same mesh.. it's another batch for each material/mesh relation if I understand correctly.
Unity will batch each of these separately but they will batch since a prefab is made for optimization and for batching.
Complex meshes: just like the multiple window objects, you should combine/join all the objects like so:
Static and or whole unbreakable objects should be combined/joined as ONE mesh. (NO need to connect all vertices like a sphere is). the breakable object would need to be seperate chunks objects which each a rigidbody component.
Separate moving parts (animation) for car-wheels, windmills for exemples. nested in a parent object.
Cars probably are all non-static so use gpu instancing. But not for the windmill structure -> static structure, and just for the rotating object -> gpu instancing. (although: you probably not gonna spawn 15 windmills so no real need of batching these. lol 🤣)
Characters: usually one mesh for the body skin. for more life: 1 mesh for each eyes, and even more: the tongue and teeth/gum.
Then customization of each cloth and bags, wearables ... is another story.. diff. approaches..
5. GPU instancing allows object to move while Static is static cant move. there is conflict right there.. but I don't know try it.
6. I have no clue which is best.
Amazing Vid, 824th Subscriber
But what about occlusion culling? If you've got an interior level made up of several walls and rooms, is it better to user lots of smaller meshes and occlusion culling?
Or what about the middle ground: making each room a large static object, and then using occlusion culling to turn off entire rooms at a time?
GREAT CONTENT
Thank you! One of the reasons I'm hesitant to try 3D is because I'm worried about performance. 2D is just so much easier and you don't need to worry about performance as much.
Thank you :)
Nice vid!
subscription for the cat and I liked it for the tip.
Thanks bro
I have a question about your 3rd point.
4:05
What should I use for organic material? For example, grass, trees, bushes, etc. - but these only "move" by a shader.
should I use GPU instancing or static mesh?
Good question, static batching should work for them. When I say no movement what I mean is that objects transforms should not change. Any movement done through the shader is fine.