From 219fe8a59beb13ebfa0353e3227583da20b713fd Mon Sep 17 00:00:00 2001 From: Dawid Masiukiewicz Date: Fri, 5 Mar 2021 20:22:10 +0000 Subject: [PATCH] Update Introduction --- Introduction.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Introduction.md b/Introduction.md index 6455e50..d6a6b5c 100644 --- a/Introduction.md +++ b/Introduction.md @@ -10,7 +10,7 @@ The core idea behind **BECS** technology is the way how it is managing memory an This layout provides fast memory access thanks to good cache locality. -Library provides a possibility to add/remove entity components. That operation means that entity changes it's **entity type** and memory needs to be copied to different location (into chunk of new **entity type**). This operation is quick enough to be used for infrequent logic changes. +Library provides a possibility to add/remove entity components. That operation means that entity changes its **entity type** and memory needs to be copied to different location (into chunk of new **entity type**). This operation is quick enough to be used for infrequent logic changes. Systems execution is managed by library itself. Developer gives the **BECS** information about system priority, components and dependencies. Systems are grouped into **passes**. The purpose for **passes** is to give possibility to run different systems with different frequency (e.g. default pass run once per frame, physics pass called multiple times per frame (fixed time step) and then rendering pass). Passes call all systems assigned to them in order designated by priorities. This type of systems execution model gives library a lot information which helps to improve performance.