> Unity has signed a lucrative contract with enterprise technology firm CACI that will see it become the "preferred real-time 3D platform" for future systems de

> Unity has signed a lucrative contract with enterprise technology firm CACI that will see it become the "preferred real-time 3D platform" for future systems design and simulation programs across the U.S. government. I know that some might dislike this on ethical grounds, but then again, I guess I couldn't really be opposed to something like Blender being used for 3D modelling for all sorts of domains, so my views of Unity shouldn't be that different, either. From a business perspective, that's just securing a lucrative deal for a high profile client. That said, Unity still is one of the better options for 3D gamedev beginners: good workflows for assets and level design, lots of plugins and assets that are available, great platform support, good scripting with C# (performant enough AND reasonably easy to use), one of the best amounts of tutorials and guides available. Of course, the downsides are the instability of... pretty much everything in the last few years: the editor getting slower with each release and especially for large projects, VCS support with Git/LFS can be sub-optimal, URP/HDRP/legacy render pipeline split and problems with assets, DOTS being incomplete, multiple UI/input systems, new package management functionality and problems opening/upgrading 2-4 year old example projects, networking being deprecated and even the organization itself being a bit controversial. If I wanted to make a game to sell without being skilled enough to grok Unreal, I'd probably still go for Unity. But personal projects? Godot. The open source nature allows me to dodge all of the above, even if something as basic as terrain support must come in the form of a 3rd party plugin in Godot and I probably wouldn't ship anything good anyways (at least until Godot 4 is stable with better 3D support and 5-10 years pass and there are enough assets to use as a crutch). Regardless, it seems to have reached enough of a critical mass to remain a viable option even in the future and get more love than something like Xenko/Stride (which I've mentioned before), or jMonkeyEngine (although that is lower level) and avoid situations like happened with Machinery altogether. Back to Unity, though, I hope they stop implementing half baked functionality and spend 2-5 years fixing everything and working on consistency and stability instead. Which probably won't happen, much like in enterprise software rarely you get months/years to address all of the technical debt, but rather mostly keep implementing new features for direct business value.