StationIapetus VS froggy

Check Station Iapetus, "commercial project that will eventually be released in Steam".

Besides being clear and easy to use, one of its popular features is the scene editor, which provides a scene preview as demonstrated in this example:

StationIapetus is also big enough.

Thanks! I do have two pretty big games written with the engine - https://github.com/mrDIMAS/StationIapetus and https://github.com/mrDIMAS/rusty-shooter . I've started writing them because it is impossible to get right feature set, without a game that uses it.

Thanks! Huge breaking changes in the API are rare, I'm trying to design the API to be good from the first try. I have three dependent projects, so every breaking change forces me to fix all of those. Usually I need an hour or so to make it compile again, even on large projects like this.

Hello! I've been working on this project for almost 3 months already and it has some decent progress I want to share with the community. The game is about task-force agent sent to the space station to investigate why connection with the station was lost. The plot is incomplete, it is a bit early for writing it entirely, because I'm just "whiteboxing" everything for now, and working on mechanics of the game. Here are the project links: https://github.com/mrDIMAS/StationIapetus and https://github.com/mrDIMAS/rg3d .

Station Iapetus - https://github.com/mrDIMAS/StationIapetus

What I found in practice is that many people start using the ECS for speed, and then draw themselves into a corner of the design space. Now they have to weight every step on "how would it work in ECS?", and dedicate effort to fight the ECS paradigm.

For example, a mesh may contain multiple materials. Is each material chunk a separate entity? Or maybe each bone in a skeleton is a separate entity with its own "parent" and "transform" plus other component.

One of the different approaches is component graph systems [1]. It lacks the ability to mix and match components, but provides a more natural (and simpler) model to program for.

[1] https://github.com/kvark/froggy/wiki/Component-Graph-System

I had similar motivation back in the day for CGS in https://github.com/kvark/froggy, which was also powering https://github.com/three-rs/three. It's nice to see Rust ecosystem not locking itself on ECS, even if they are so cool :)