Skip to main content

Happy with Urho3D

I had this engine in the pending tasks list since a couple of months (couple>4, really), but at some point I was motivated by a project I saw in FreeGamedev forums. Urho3d is a young project, and the first time I took time to look at it, I wasnt too kind with it. The editor was ugly and non intuitive, from my point of view, I didnt spent time looking at the samples, and also experienced troubles when trying to compile it.

Cant say that all the problems are gone, but in the last weeks I have learned to appreciate Urho3D, despite the lack of certain features, like terrain edition tools. Or (I really miss this) having the editor integrated into the engine itself, like Unity3D and most ocmmercial engines. Being able to run the game, see how it looks, and go back to edit the scene is something really useful.

But something in Urho3D got my attention: it is really easy to learn. Even when I still far from mastering all the engine, I have achieved in a week much more than I had with any other engine.






In the previous images you can see my usual test prototype in action. The rendering quality is not good, but consider that I dont have a decent graphic card, what you see is running on an Intel GMA 4500 gpu, under Linux, with OpenGL 2.1. Currently, it implements isometric like camera, with rotation, scrolling and zoom, character movement with path finding using navigation mesh and probably will add animation support today or tomorrow. All that, in a week, just asking in the forums and studying the samples.

Considering this fast rythm, I can start working seriously on my next project next month, instead of January as I expected.

Comments

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.

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...

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...