This Week in Game Engines #26! https://enginesdatabase.com/blog/this-week-in-game-engines-26/
This week we have a major Flax engine update, a Ghost of Yotei tech "deep" dive, a CS:GO and CS2 network protocol tech DEEP dive (on Reddit of all places), and much more!
An interesting post with the impressions of a game developer moving from Unity to Flax engine:
https://forum.flaxengine.com/t/from-unity-to-flax-my-thoughts-so-far/2020
In my opinion, Flax has a lot of potential but it’s not quite there yet.
Just wanted to share my experience, as I finally decided to go for the Flax Engine for a new solo game project. I have been using Unity for over a decade across many different kinds of projects (games, visualization, VR, and so on), so I thought my transition experience could be useful to others looking into a change of environment. My main motivation to move away from Unity is their licensing model, which is too costly for small independent startups like mine. The cost also feels unpredictabl...
For those that uses #FlaxEngine, I've just created some containers to CI/CD. Currently, only builds for Linux (Flax itself has a bug presenting Windows compilation from a Linux OS). Android is WIP
I spent this week looking at alternatives to #Unity after that rugpull disaster from last week. I checked out #godotengine, #defold, #FlaxEngine and #luxeengine
There's no clear solution for me but I've written up my thoughts in my weekly devlog over in the Sharkbomb Discord.
TL;DR: Godot and Luxe are both contenders but I'm not sure I want to commit to the switch now, or after this project. Godot console support and Luxe editor features are my sticking points.
Messed around some more with #FlaxEngine researching what it would take to implement some things particular to my project. Overall, the editor seems very performant (at least with my silly test project), but a bit glitchy. I was able to do what I needed to do (mostly), but both the editor and GUI API are a bit limited, not well documented, and have some frustrating behaviors.
Later I'll try out Godot for a bit.
Looking at #FlaxEngine to see how its custom JSON assets (CA) compare to #Unity 's scriptable objects. I'm posting my findings in case others have the same questions.
1) A CA is backed by a JSON file on disk, and is serialized to a plain C# class, so it can also execute code.
2) A CA has a unique ID, saved in its JSON. You can add a reference to it to a script in the editor, but this is just a JsonAsset reference. You have to cast it to the type that you want.
(cont'd 🧵)
Will take a very close look on this engine, as porting Vehicle Physics Pro to it seems pretty straightforward.
I saw https://github.com/FlaxEngine/FlaxEngine in bird site, bandwagoning on #unity being a proprietary engine and changing policies as they please.
Isn't #FlaxEngine literally as proprietary (but source available) as unity?
LOL
henriquelalves
Vehicle Physics
Bruno MASSA
wavewalnut
Martin Nerurkar
Antiquity/Midnight Spire Games
libreware sniffer