это здесь не причем. у меня 2 ноутбука - примерно с одинаковой производительностью и у обоих сильная загрузка 25-32 % на пустых дефолтных проектах. да и штмл5 версия тоже неслабо грузит процессор. это я ещё с 1.2 заметил - с которой собственно и начал изучение.
вон же пишет выше человек
it has nothing to do with it. I have 2 laptops - with about the same performance and both have a strong load of 25-32% on empty default projects. Yes, and shtml5 version also heavily loads the processor. I noticed this from 1.2 - with which I actually began the study.
there is a person writing above
11900K = 14-16% CPU usage
i5 13th the gen = 10-18 %
i3 550 = 55-65 %
CPU 6405U @ 2.40GHz = 25-32%
So in my test Defold and Godot use more or less the same amount of CPU. Unity on the other hand is not. I’m not sure what the update loops looks like in Godot and Unity respectively, but it seems like Unity is taking a different approach when idle.
The problem is that the project does nothing, but already loads the processor by 20% or more.
The problem is that when the animation and sounds begin to play, network interaction and various calculations begin - then there will be low fps and high cpu utilization.
This will limit the range of devices used. In addition, you are constantly adding new functionality that will also eventually affect performance.
Not entirely sure it is a problem unless nothing scales to 100% CPU by doing something. Here I animate 25000 sprites and I’m not even reaching 40% CPU:
Yes and no. We do add functionality but also pay attention to performance. A lot of features we add will only impact performance if used. And sometimes we add functionality that will also improve performance.
It’s not like that. Let me try to explain it in a super simplified way.
Game engine loop is not like : run the loop 60 times and does nothing else.
It is a while(true) loop that does as many operations as possible.
Most of the time, this while(true) runs doing almost nothing (it calculates delta time and some other lightweight operations). But it is still an infinite loop that works as much as OS let to (in your case, for 30% CPU).
So, just for example, let’s say you run this almost empty loop 100.000 times a second, which takes 30% CPU on your PC.
Then you add some functionality. And now your loop have to do something. You can’t run it 100.000 times anymore, you run it, let’s say, 5.000 times where 60 times the engine does something which uses CPU time as well (logic, physics, networks and so on). So you have more or less the same 30% CPU usage, but this time you utilize this CPU usage with useful work instead of almost empty superfast loop.
Of course if you add a lot of functionality, CPU usage will grow even more than these 30%, but till some bar it will not be just adding to 30% CPU usage, but utilization of these 30%.
