Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
Hecs Alternatives
Similar projects and alternatives to hecs
-
egui
egui: an easy-to-use immediate mode GUI in Rust that runs on both web and native
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
ecs
Discontinued LeoECS is a fast Entity Component System (ECS) Framework powered by C# with optional integration to Unity (by Leopotam)
-
-
Entitas
Entitas is a super fast Entity Component System (ECS) Framework specifically made for C# and Unity
-
-
-
-
-
-
procedural-spider
Small game where you play a big spider chasing small spiders, written in Rust and Macroquad.
-
actors.unity
🚀Actors is a framework empowering developers to make better games faster on Unity.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
hecs reviews and mentions
-
Does it still make sense to roll your own ECS?
For Rust, I really like Bevy's, but it gets too much in the way. I'd probably use macroquad instead with something like hecs (I tried macroquad with Bevy ECS and didn't go well).
-
Why ECS pattern is popular in Rust?
The question arises from seeing a plethora of projects using ECS: hecs , Bevy , specs, legion
-
Learning How To Rewind Time - Save & Load
My current design has struct Core that is basically "everything you need to save in a savefile", it has a hecs ECS (which needs a bit of boilerplate the hecs docs show you how to write to serialize it), and a bunch of simpler gamestate stuff like the discovered map positions, the current player etc. Everything is tree-like and serializes into a text file. Entity handles from hecs serve as "pseudo-pointers" that can represent cycle-like structures without running into endless cycles.
-
After working on our Godot + Rust game fulltime for one year it is now up on Steam
Out of the other Rust engines we've tried I think Macroquad was the most interesting option, and even though I've only made a few small projects in it worked extremely well and was what I'd expect from a game framework. While working in Bevy I felt like it was "writing fun Rust", but it wasn't really making a game. Macroquad on the other hand got immediately out of the way, and using it together with hecs was a painless experience where the whole time I felt like I was working on "the game" rather than "building systems that are invisible to the player".
-
BITGUN Demo is now live on Steam - a game made in Rust and Godot by a two person fulltime indie dev team over the past 9 months
The last crate worth mentioning is probably hecs for ECS, which we don't really use as heavily as some ECS fans would assume, but it made working around some problems between GDScript and Rust easier by storing things in ECS, passing around handles and querying ECS instead. Initially we did this with a global object and lots of state (which we still use for some things), but as the number of "things" grew it became easier to put it into ECS.
-
A 2D Pixel Physics Simulator with Cellular Automata written in Rust
I use the awesome Vulkano for rendering and computation, and Rapier for simple physics. Contour is used for the initial shapes, but rapier forms the physics colliders from it. Hecs is used as well. And you might recognize Egui as gui :). I gotta say, I'm starting to be pretty happy with the rust ecosystem overall.
-
What is the plain Vec architecture in the hecs documentation?
In the hecs documentation there is a section, Why Not ECS?. In it, the author states, "If your game will have few types of entities, consider a simpler architecture such as storing each type of entity in a separate plain Vec."
-
Showcasing my game: The Process. Built with Rust and Godot!
Usually, what I do is creating large, robust components in Rust. In my game, most of the logic lives inside the Factory node, which inside holds a full ECS (currently using https://github.com/Ralith/hecs) as well as other associated resources. This node takes care of holding the state and simulating all the machines in the factory and their interactions.
-
Tiles as entities for common states and effects? (ECS related)
Generally, spatially-indexable data gets special treatment in games. (See Why not ECS for example, from the hecs ECS library.)
-
I'm trying to follow the RLTK tutorial and feel like it is too much at a time, please help me solve some questions
That impl basically says that Leftwalker is a System (or implements a System interface, to use a different parlance). Why exactly do Systems need lifetime is something better asked of the authors of the ECS library the tutorial uses. (personally I use hecs https://github.com/Ralith/hecs instead because I find it easier to use, no lifetime in sight :p)
-
A note from our sponsor - InfluxDB
www.influxdata.com | 18 Apr 2024
Stats
Ralith/hecs is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of hecs is Rust.