sounds like Flax Engine has some really good options, and that it’s perhaps too difficult to code an entire new way of processing the data stack, or then also that not sure these video games with a ton of bullets, and somehow enemies dumped in for the sake of it really sells, or are among the best video games at all
what think is that it’s a great discussion if this ECS coding could be useful at all, and sort of how to integrate something like that into an engine that has been built perhaps from the ground up to not run that way, or that ultimately if this is something that’d make more sense as an ’ official ’ plug - in, and with it’s own documentation page somewhere on the internet, etc
myself hope much more for RTX ( because have a laptop that supports that now ), and then also really want to see live destruction of 3D objects, or then that there are bug fixes in visject, and that sort of gets better ( Flax Engine has the best visual script right now ), or that there’s an official roadmap where one could read of all the new cool stuff, and how much the community is simply getting spoiled from this amazing program
link to Flax Engine 1.12 roadmap : Flax Roadmap | Trello
link to 1.12 milestone : 1.12 · Milestone #7 · FlaxEngine/FlaxEngine
there’s a ton of good stuff as it is, and not sure they’re very busy fixing important bugs, or that it might be a discussion to somehow add ECS to the 1.14, or 1.15 milestone, and then what kind of support for that, or if it’s gonna break with all the previous editions of the engine also
?!??
at the Godot Engine it was also decided not to add ECS logics because it was somehow less user - friendly, and that Juan Linietsky that’s sort of in charge of the engine decided it was better to focus on other things, or that there’s a link to an article where he explains their decisisons at the FOSS software