Juan LinietskyAs promised, an article about things that Godot is missing to tackle on bigger titles.
https://godotengine.org/article/whats-missing-in-godot-for-aaa/
Aras Pranckevičius@reduz nice article!
I do think chasing AAA is risky and might be not achievable (Unity made that mistake of trying to do that, I think). Especially modern AAA is *so far out* that their issues are mostly in the land of "we have this many terabytes of data that even Perforce struggles" or "how do I organize work of 1000 people at once".
@reduz If I were a king of some hypothetical engine, I'd perhaps explicitly say it's not going after AAA. Triple-III (indie teams with high production values), maybe AA, sure. And do that by focusing on pleasant workflows, good collaboration, fast iteration times. Mostly.
Ignas Kiela@aras @reduz For what it's worth, the main strengths of Godot has been the pleasant workflows and fast iteration times IMO. Collaboration is also coming along, though not as fast I'd say.
In the end, since it's a mostly community driven project, these things will probably remain a large focus, because they are relatively easy to fix in small pieces, which fits great with occasional contributor's flow.
In the end, since it's a mostly community driven project, these things will probably remain a large focus, because they are relatively easy to fix in small pieces, which fits great with occasional contributor's flow.
@ignaloidas @reduz Unity also had very fast iteration times and pleasant (simple) workflows before it tried to become more suitable for larger productions :)
It's complex balance it well; "just add a bunch of features" (that everyone asks for!) can lead to messy UI and settings overload. And so on.