I heard searched about ECS some time ago, but recently I learned that you can combine both ECS and the old GameObject system. I haven't found much info yet on performance with Hybrid ECS compared to using pure ECS and the old game object system but I will keep searching. I'd like to know, is it worth going from the old game object to Hybrid ECS when your project is already very deep in development?
#Should I Go Hybrid ECS When Already Deep in Development?
1 messages · Page 1 of 1 (latest)
The benefit would be moving work to other threads using jobs, so if you are bound by the main thread you could get some major improvements
That depends on if you have anything in your game that can be parallelised
Its probably not worth going for ECS since Hybrid solutions tend to not have much better performance than GameObject based ones. The intercommunication between ECS world and Monobehaviours is just slow. If you want some easy to reach performance go for burst and Jobs first and stay with gameobjects
Ok thank you guys for your answers. I read that there is a steep learning curve for this.
Indeed, but something that could still come to use for you is Jobs and Burst, especially if a profiller says a specific part of the game is eating all your performance :3