WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2024 Poal.co

679

(post is archived)

[–] 4 pts

This looks less shit than I thought it would, making a network component in C++ looks similar-enough to how Unreal handles components to make it decent to learn if you wanted to do that. Personally I wouldn't as I don't have a compelling reason not to just use Unreal.

[–] 1 pt

AFAIK, the biggest complaint on it is that building is difficult and tedious. And there has been lots of odd bugs.

I haven't watched this yet, but it's a good source for this type of info: https://www.youtube.com/watch?v=tBtp2OKMTeM

[–] 1 pt

Yea, seem like the devs couldn't give a shit for the community either. From the ytube comments - 'I seriously tried to learn how to use O3DE. I have many years experience with UE4/5, Unity, Godot and a few others. There is no documentation for O3DE and the API is unstable. The developers will change it and break your project if you update. There are no tutorials for O3DE and no documentation. The engine is full of bugs and doesn't even preform well. It is missing major features like native sound and particle system support. Script canvas it's scripting system depends on creating c++ code and the lua API has no documentation and has few examples (and the ones that do exist are from much older Lumberyard versions and don't always work because the c++ API is unstable). It is missing a lot of other basic features. The engineers that develop the code base are extremely smart and this is a problem because the level of c++ knowledge needed to use the engine is very high. They use a lot of advance C++ that makes scripting game logic and using existing components very difficult when trying to learn the engine. C++ game logic is 10x times easier to write for UE5 then O3DE. They also use a bus system for component communication that is not found in any other game engine hence is a hard to learn and follow with no documentation or tutorials. I followed the O3DE book written by one of the developers and the books was full of errors that he corrects in the git hub but does not tell the reader. Basically nobody talks about the engine because it lacks basic features, has no user base, no documentation or support, and is unstable. If you use their discord you find that questions asking for basic support go unanswered and that people drop O3DE because of basic lack of usability and merit. I do have hope for a AAA open source game engine and I hope that O3DE gets better but I think it is several years away from something that is on the same feature level of Godot. Honestly I just don't think the developers give two shits about the engine. It is an open source project with 0 passion for the project or community.'