FAQ
FAQ, frequently asked questions.
Last updated
Was this helpful?
FAQ, frequently asked questions.
Last updated
Was this helpful?
Of course you can! By either becoming a and actively participating in the ecosystem or by ! We are happy about any help!
Especially for games or simulations... but also data-oriented applications where it is important to have and query a lot of flexible data!
You may have seen that Arch performs well in some benchmarks, but slower than some ECS frameworks. Does this mean that Arch is slow or poorly optimized? No, its the opposite! Every benchmark is implemented differently and sometimes uses a different (often outdated) Arch version. In addition, Arch has something that many other ECS do not have, . allow you to create huge amounts of entities at runtime and even remove them later to free up memory, but this adds a bit of overhead. It's a trade-off that's worth it though!
Arch's mantra is to be . A basic ECS that can be quickly and easily integrated anywhere with the possibility to expand it according to your own wishes. Thus we support clean code, separation of concerns and KISS as programming principles. Arch only does what it is supposed to do, to be a high-performance ECS that is easy to use and gives YOU the tools. Nothing more and nothing less, no hidden operations in the background. For everything else there is , a collection of tools and libraries that extend Arch.
You can do that too. You can use Arch anywhere you use .Net Framework 2, .Net 6 to .Net8. This means you can use Arch in a pure C# project or in an engine like !
Arch also works in AOT environments. Depending on how you use it, however, you may have to in advance or simply use .
You can do that too! In arch you can simply use classes and structs as components without having to play around with pointers or forcing only structs. This even has some advantages, it is faster to develop with it! If you want to get the maximum performance out of it, we still recommend using only unmanaged structs as components.