Skip to main content

At last, testing O3DE 23.05

 Took some time, but at last I managed to install O3De 23.05. I have no time to extensively test it, because there is a project requiring all my effort, but I took a couple of nights to work with it.


I cant find any dramatic changes, this is not a big leap like 22.10 was. Im not sure if we will see another release like that again. Im not going to get into a proper analysis (a few hours are not enough), but here are some things that O3DE needs to improve:

  • Project creation process now involves a build, that requires Visual Studio. That is annoying for artists.
  • Project build is complex. And I mean complex. It takes 12 steps, and manually copying stuff. Lucky us, it is being fixed and I hope we will have the new building script in next major release.
  • Animation workflow is annoying. As  a developer currently working in a project that requires several animations and retargeting, I dont see feasible switching to a workflow that produces separate files for each animation. By the way, animation graphs are fucking awesome, check the video!
  • Documentation.O3DE severely lacks documentation and tutorials.
I keep my projections: maybe in three more releases it will be usable.
Labels:

Comments

Post a Comment

Popular posts from this blog

Isometric camera with Godot

Took some effort and some of my sleep hours, but at last, I made it. Here is my first videotutorial: implementing an isometric camera in 3D, with Godot. Useful if you want to emulate the look of old classics like Fallout 2, but with some extra features. Considering that my voice is not so nice, and my english pronounciation is even worse, I also added texts to help you underestand what Im saying. You will also notice some background noise, but cant do anything to solve that. Any suggestion is welcome. Expect another tutorial soon.... or sor tof. This time, will be about my AI system.
Post a Comment
Read more

Lessons about game dev

 Meet Bobby (not Kotick)! He is going to taught you a lesson about how NOT to make games. Bobby is a very sharp bussinessman, that sees everybody is playing games. More important, everybody is spending money in games. What would any smart bussinessman do? Well, get into the games bussiness, and he knows he has an advantage. See, Bobby is not going to spend hundredths of thousands dollars to make a game, when he can make it much cheaper.  And here comes the first mistake. Bobby goes to his birth city, in a shitty third class communist country, where it is easier to find a honest politician than a game developer. There, he assembles the Avengers... I mean, a team of talented guys that... never made a game in their lives. He invests in hardware, with good workstations equipped with fairly modern GPUs, pairde with the worst, cheapest 18 inches display you can get. Also, a server with a 24 VRAM GPU, because any game studio needs a server for... nobody knows exactly for what, but t...
3 comments
Read more

Vulkan and open source engines

It is weird, but even when Vulkan has embraced the open source philosophy (open drivers, tools, etc), Im not seeing too much enthusiasm to adopt it in open source game engines. I have been following mostly Godot and Urho3D, yet Ogre3D and Irrlicht doesnt seems to be rushing to implement the new renderers. It is worth to mention that Godot promissed they would delay the long needed refactoring of its 3D renderer until Vulkan release, but now they say they wont be using it, favoring GL ES 3 instead. The other engines seems to be dealing with lack of man power (Urho3D leader left the work on hands of community, as he is not working on Vulkan renderer right now) and base code designed for older APIs, specifically, DirectX 9. Lot of work is required to adapt this code base, not only for Vulkan, but for DirectX 12 too. Well, nobody said that developing a game engine was easy. The advantages of Vulkan have been widely detailed. From engine point of view, it would centralize all renderers...
3 comments
Read more