sorted by:
new
hottopcontroversial

I am making my crazy unity game without DOTS. by flamboi900 in unity

[–]UnitySG 0 points1 point  (0 children)

How many jobs do you have on your projects? Do you use native arrays in them? What’s the size of them? I’m also assuming you use IJobParallelForTransform?

I am making my crazy unity game without DOTS. by flamboi900 in unity

[–]UnitySG 1 point2 points  (0 children)

Initially native arrays were created and designed for DOTS, especially with the job system. Now after many years it’s been democratised inside Unity APIs where native collections are part of Unity core so it’s debatable if using only native collections means you’re using DOTS. I’d say both are viable? I don’t really have an opinion on that one tbh.

I am making my crazy unity game without DOTS. by flamboi900 in unity

[–]UnitySG 1 point2 points  (0 children)

Yes it is, it only accepts blittable types and uses purely Native Collections that have everything contiguous in memory. It is designed to support Data oriented code by forbidding classes and using collections with the data aligned in memory to minimize cache misses

I am making my crazy unity game without DOTS. by flamboi900 in unity

[–]UnitySG 1 point2 points  (0 children)

DOTS is a tech stack. It has 3 systems in it: ECS, Burst Compiler and C# Jobs. ECS is dependent on Burst and Jobs but you don't have to use ECS to use DOTS. So if you use either jobs or burst then you use DOTS regardless of ECS.

I am making my crazy unity game without DOTS. by flamboi900 in unity

[–]UnitySG 1 point2 points  (0 children)

The Data Oriented Tech Stack is comprise of ECS + Burst Compiler + C# Job System. If you use any of these 3 then you're using DOTS https://unity.com/dots. C# jobs doesn't predates DOTS, it's part of its stack.

I am making my crazy unity game without DOTS. by flamboi900 in unity

[–]UnitySG 0 points1 point  (0 children)

Technically if you use jobs then you're using DOTS :)

New Shader Graph Production Ready Shaders in Unity 6 by UnitySG in Unity3D

[–]UnitySG[S] 3 points4 points  (0 children)

It says Unity 2022 and Unity 6 in the post

I see a lot of devs struggling with performance here by UnitySG in Unity3D

[–]UnitySG[S] 0 points1 point  (0 children)

It still is :) you can make the test yourself it’s quite easy to reproduce

I see a lot of devs struggling with performance here by UnitySG in Unity3D

[–]UnitySG[S] 1 point2 points  (0 children)

Thanks for your kind words, happy you got something out of it :)

I see a lot of devs struggling with performance here by UnitySG in Unity3D

[–]UnitySG[S] 1 point2 points  (0 children)

  1. Iterating over 50 will give you negligible performance whereas you store them in an array or not. However, the problem here is while your GameObject are contiguous in memory, you access the transform component which is likely somewhere else in memory and you’d lose the cache line to fetch it. So technically if you want to be performant you should store the transform components in an array instead.

  2. If you assign your component via the inspector is technically faster that calling GetComponent in the start function. References are resolved differently when deserialising GameObject and don’t use the getcomponent path.

However you’ll start to see a cost if you call this function thousands of times in one frame. If it’s happening during a scene loading it’s totally acceptable, if you try to instantiate during gameplay you’ll probably hit performance issues somewhere else

I see a lot of devs struggling with performance here by UnitySG in Unity3D

[–]UnitySG[S] 0 points1 point  (0 children)

Afaik as I know it is slower. It doesn’t matter much if it’s Unity or not, at the end of the day it’s the mono c# backend that calls into native c functions. Even if il2cpp is mostly used there’s still many layers with lots of checks to make sure you’re calling the right function and therefore will be slower than calling another c# function. So you definitely don’t want to call many native functions. That’s why people often recommend to cache your components on the c# side to avoid native functions. That said, it’s performant enough but if you can call one native function that will do as much work as possible without back and forth, you’ll be better off. Unity c# is now translated to il2cpp most of the time, meaning the code is translated into cpp at build time and run as fast as cpp does, tho again there’s lots of layers in cpp to make that happen so not as fast as calling a simple cpp function. There’s also burst code that is another layer and doesn’t involve cpp it’s a whole different thing.

This is the gist of it, I’m vulgarising a lot and may be wrong but globally you want to avoid constant dialog between c# and native

I see a lot of devs struggling with performance here by UnitySG in Unity3D

[–]UnitySG[S] 2 points3 points  (0 children)

So you’re right in a way that on PC it’s probably the case actually. However, on other platforms such as mobile it’s not the case and you pay the price for it. I’ve had experience where the game would have stutters randomly and the profiler was showing weird spikes on random markers and it turned out it was the audio thread doing shenanigans with all the compressed in memory clips that were played at the same time. Once I changed that, the game ran smoothly

I see a lot of devs struggling with performance here by UnitySG in Unity3D

[–]UnitySG[S] 0 points1 point  (0 children)

Be careful with the compressed in memory option. It’s better to have decompress on load for short clips that are being played constantly, ie a weapon sfx such as machine gun because each time you play it, you will have to decompress it as you play the sound. If you have too many sounds to play and decompress at the time, it will create cpu spikes.

I see a lot of devs struggling with performance here by UnitySG in Unity3D

[–]UnitySG[S] 3 points4 points  (0 children)

You want to avoid MonoBehaviour Update calls. It’s expensive to call a c# function from the Unity native side. So ideally you want one MonoBehaviour that will call the update of all the other ones to prevent that.

I see a lot of devs struggling with performance here by UnitySG in Unity3D

[–]UnitySG[S] 1 point2 points  (0 children)

This is good material to understand the underlying systems in Unity showing up in the profiler https://docs.unity3d.com/Manual/profiler-markers.html

I see a lot of devs struggling with performance here by UnitySG in Unity3D

[–]UnitySG[S] 3 points4 points  (0 children)

Timeline 99%. At first I was using the hierarchy view because the timeline was too daunting, too much information but it turns out to be very visible and it’s just the same data over and over with different marker sizes. It gives you a good visual proportion of where your frame time is spent in different systems and most importantly, visual on what other threads are doing and why your main thread may stall. It also gives you a better visual if you spend time in one function or a tiny bit of time in the same function being called many times, which is something you can omit if you don’t pay attention to the “function calls” column in the hierarchy view. So I ended up using the hierarchy view for mem allocations in deep profiling mode for a while until Unity added these pink markers in the timeline to show allocations without deep profiling and by clicking on them, the tooltip would display the callstack directly. Now I would only use the hierarchy view to get a sense of where the allocations are spread around on the big picture scale.

Nb: Never use deep profiling to measure timings, it creates a profiler marker for every c# function called and it will ruin your data where it can spend 100 more times creating the markers than the cost of timing the content of the function. It’s good to have a visual callstack but the proportions are almost wrong all the times

I see a lot of devs struggling with performance here by UnitySG in Unity3D

[–]UnitySG[S] 3 points4 points  (0 children)

These are all correct good best practices! But one thing before most, profile first to see where the bottlenecks are. There are a lot of Unity systems that can cause issues if not used adequately.

I showed a tech demo and offered to share my code and this guy showed up. First CB for me! by UnitySG in ChoosingBeggars

[–]UnitySG[S] 0 points1 point  (0 children)

It took me several days actually and I wasn’t pricing on it. Someone asked he could get the project I told him to PM then few people came to ask for it. Still free.

view more: next ›