Timeline for Entity Component System: system and components relation
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2020 at 22:34 | comment | added | DMGregory♦ | One way this is sometimes done is to define a set of "archetypes" defined by which subset of component types they use. [Components of] entities of each archetype are stored in contiguous arrays. The process of looping over all entities with a specific combination of components is then a process of walking through each archetype that includes all of those components and processing every entity of that archetype. | |
| Jan 7, 2020 at 21:49 | comment | added | Mark Ingram | How do you ensure that a system encounters a "valid" entity. i.e. a RenderingSystem may need a MeshComponent and TransformComponent etc. So how does the system combine relevant N components into a single view? An entity might have a MeshComponent but no TransformComponent? | |
| Sep 5, 2017 at 11:14 | comment | added | Andrew | Thank you for your detailed explanation. I think I'll go for an hybrid solution like suggestested. My main concern was to make sure I was using something "standard". In other words I wanted to be sure I'm not exploring new design patterns but rather using some consolidated ones. | |
| Sep 4, 2017 at 13:08 | history | answered | DMGregory♦ | CC BY-SA 3.0 |