Clean, fast and simple with Entitas and Unity - Unite Melbourne 2016
3 likes•2,085 views
This document discusses using an entity component system architecture with Entitas, an open source C# entity component system framework for Unity. It explains that Entitas keeps data separate from behavior using data-only components, and organizes game logic into systems. This results in code that is clean, fast and simple to work with. The document provides examples of how movement logic can be handled within a system in Entitas, and demonstrates that Entitas uses less memory and CPU than the default Unity object model. It positions Entitas as a viable alternative for organizing game code in a consistent and modular way.
![it["adds velocity to position"] = () => {
// given
var pool = Pools.sharedInstance.core;
var entity = pool.CreateEntity()
.AddPosition(Vector3.one)
.AddVelocity(Vector3.one);
var system = pool.CreateSystem(new MovementSystem());
// when
system.Execute();
// then
entity.position.value.should_be(new Vector3(2, 2, 2));
};](https://image.slidesharecdn.com/unitemelbourne2016-slideshare-161031193645/85/Clean-fast-and-simple-with-Entitas-and-Unity-Unite-Melbourne-2016-70-320.jpg)
Clean, fast and simple with Entitas and Unity - Unite Melbourne 2016
- 1. ENTITY COMPONENT SYSTEM ARCHITECTUREClean, fast and simple with Entitas and Unity
- 10. GAME ENGINE
- 12. DESIGN PATTERNS
- 20. ENTITAS#1 ECS ON GITHUB
- 28. UNITY COMPONENTS: Data + Behaviour ENTITAS COMPONENTS Data only
- 29. public class Archer : Troop { public int health; public float speed; // ... void Awake() { // ... } void Start() { // ... } void Update() { // ... } }
- 30. public class Archer : Troop { // Inheritance public int health; public float speed; // Data // ... void Awake() { // ... } // Initialization void Start() { // ... } void Update() { // ... // Update } }
- 31. // Data only - no behaviour public class PositionComponent : IComponent { public Vector3 value; } public class MovableComponent : IComponent { }
- 32. +------------------+ | Pool | |------------------| | e e | +-----------+ | e e---|----> | Entity | | e e | |-----------| | e e e | | Component | | e e | | | +-----------+ | e e | | Component-|----> | Component | | e e e | | | |-----------| | e e e | | Component | | Data | +------------------+ +-----------+ +-----------+ | | | +-------------+ | | e | Groups | | e e | +---> | +------------+ | e | | | | e | e | e | +--------|----+ e | | e | | e e | +------------+
- 34. LOGIC?
- 35. Games are interactive simulations — Maxim Zaks
- 36. public class MovementSystem : IExecuteSystem { public void Execute() { var movables = Pools.pool.GetGroup( Matcher.AllOf( Matcher.Velocity, Matcher.Position )); foreach (var e in movables.GetEntities()) { var pos = e.position.value; e.ReplacePosition(pos + e.velocity.value); } } }
- 38. SYSTEMS Chain of Responsibility +------------+ +------------+ +------------+ +------------+ | | | | | | | | | System | +---> | System | +---> | System | +---> | System | | | | | | | | | +------------+ +------------+ +------------+ +------------+
- 39. SYSTEMS Chain of Responsibility |-------------------------------- Game Loop --------------------------------| +------------+ +------------+ +------------+ +------------+ | | | | | | | | | System | +---> | System | +---> | System | +---> | System | | | | | | | | | +------------+ +------------+ +------------+ +------------+
- 40. SYSTEMS IN ENTITAS - Initialize System - Execute System - Reactive System
- 41. DEMO Match One
- 44. CLEAN Separation of concerns Composition over Inheritance Single responsibility principle Consistency
- 69. public class MovementSystem : IExecuteSystem { public void Execute() { var movables = Pools.pool.GetGroup( Matcher.AllOf( Matcher.Velocity, Matcher.Position )); foreach (var e in movables.GetEntities()) { var pos = e.position.value; e.ReplacePosition(pos + e.velocity.value); } } }
- 70. it["adds velocity to position"] = () => { // given var pool = Pools.sharedInstance.core; var entity = pool.CreateEntity() .AddPosition(Vector3.one) .AddVelocity(Vector3.one); var system = pool.CreateSystem(new MovementSystem()); // when system.Execute(); // then entity.position.value.should_be(new Vector3(2, 2, 2)); };
- 71. CONSISTENCY
- 72. CLEAN Separation of concerns Composition over Inheritance Single responsibility principle Consistency
- 75. UNITY VS ENTITAS: Objects 1000 objects with 2 components Memory: 9x (2.9 MB vs 0.32 MB) CPU: 17x (105 ms vs 6 ms)
- 77. ENTITAS VS UNITY: Logic update 25000 objects Memory: 5x (36.4 MB vs 7.6 MB) CPU: 2x (20.5 ms vs 9.6 ms)
- 78. UNITY BLOG 10000 Update() calls by Valentin Simonov
- 80. SIMPLE similar to Unity simple conventions easy to add features Visual Debugging Reusing code
- 81. SYSTEMS Chain of Responsibility +------------+ +------------+ +------------+ +------------+ | | | | | | | | | System | +---> | System | +---> | System | +---> | System | | | | | | | | | +------------+ +------------+ +------------+ +------------+
- 82. SYSTEMS Chain of Responsibility +------------+ +------------+ +------------+ | | | | | | | System | +---> | System | +------------------------> | System | | | | | | | +------------+ +------------+ +------------+
- 83. SYSTEMS Chain of Responsibility +------------+ +------------+ +------------+ +------------+ | | | | | | | | | System | +---> | System | +---> | System | +---> | System | | | | | | | | | +------------+ +------------+ +------------+ +------------+
- 84. SIMPLE similar to Unity simple conventions easy to add features Visual Debugging Reusing code
- 86. WOOGA.COM/JOBS