I had a videogame idea in my head for a long time, and ended up choosing Urho3D. I am very new to the engine, but explored the code of the examples for some days.
Unfortunately, none of the examples give me a good base for starting point of what I had in mind and I miss some gamedev insights. Therefore I need a guide to not make catastrophic mistakes right in the begining.
For starting:
I need to place the players (StaticModel?) inside a Room (StaticModel/box.mdl?) Am I in the good direction?
A very newbie concept I am missing: How do I apply the texture(SetMaterial?) to the inside of the box? (always that I navigate with the camera inside a box object it becomes transparent)
Assuming the player will float in the 3 axis inside the room, Whatâs reference/example to look at if I want it to avoid him going out of the room?
Which examples/classes/links should I look at to accomplish this first step?
The answers to your questions depend on your project, and even then there are often many ways to approach similar goals.
But firstly, did you manage to set up some sort of empty project that compiles and runs?
Hi @Modanung in fact any path that is not totally wrong will do for me Thanks for welcome!
I compiled the whole engine, so currently I am playing/modifying over one of the examples(10_RenderToTexture). I understand in the future (among other things) I will need to pay attention to the Sample class and change it to fit my needs.
I know is not the cleanest way to start a project, but that gave me a fast way to make modifications add things and see its efects. So yes we can say I have a working environment for learning.
Probably not. A box is an object inside your Scene. The Scene is the box youâre thinking of. Everything will be in it.
I think this is done with normals. If you reverse the normals, youâll see the material on the inside, and it will be transparent when looking into the box, and visible when inside the box. But, refer back to your first question, you probably donât want to create a game or scene, with a box.mdl as your game container.
The skeletal animation sample turns the model when it hits limits. In c# that little bit of code looks like this:
// If in risk of going outside the plane, rotate the model right
var pos = Node.Position;
if (pos.X < Bounds.Min.X || pos.X > Bounds.Max.X || pos.Z < Bounds.Min.Z || pos.Z > Bounds.Max.Z)
Node.Yaw(RotationSpeed * timeStep, TransformSpace.Local);
How about the âstatic sceneâ sample. If you spend most of your time initially going through the samples, the rest of your time will be better spent. Then as you create your game, create your own simple, basic samples of each feature you add into your game. As @slapin wrote:
So how would I put walls to this Scene?
I saw the StaticScene example places all the mushrooms in a plane (and this node is direct child from the sceneâŚ)
Urho3Dâs Scene object is basically providing a Root Node for a Scene Hierarchy, consisting of Nodes which may or may not have Components attached to them. Nodes have transforms which are relative to their parents, but the root node of a scene generally has identity transform (no rotation, no translation, so position is <0,0,0>, and scale of <1,1,1>)
Scene hierarchies are pretty common to all game engines, so I would start by finding out what they are for.
It is notable for Urho3D that Components do not have a Transform (like Unity), but instead they derive their transform from their immediate parent node. The implication is that if you attach multiple Model components to the same Node, they all have the same Transform.
Therefore, you should have a unique Node for each Plane, and set the orientation for each Node to suit yourself.
It is also notable for Urho3D that multiple scenes can exist at the same time (unlike Unity), which can be useful for games that load content on demand, as each scene can represent a connected subspace, or even be used to contain stuff separate to the game itself (menus, gamestates, whatever).
This is a very flexible system in my opinion, it can be (ab)used in many wonderful ways.
Hi. If you not familiar with common gamedev concepts then itâs time to start investigate it. There are a lot of tutorials you can find on youtube (most of them can use some popular engines like Unity and Unreal - donât hesitate to look into it too, because concepts are pretty much the same in every engine; their documentation contains general stuff too).
Also, consider to get more familiar with 3d modelling (it is actually very fun to get familiar with) - Blender tutorials could be the good point to start (youâll know some basic stuff about vertex, edges, faces, normals, textures and materials; and then you could easily create some own easy assets without finding or buying it on the web) - you will know that box.mdl is not intended to be viewed from inside (but with basic modelling knowledge you can fix it in a few seconds), and you need different model or use scaled boxes/planes as a walls and floor.
Thanks! these are very relevant theoretic concepts.
I see lots of tutorials, but all I find are focusing in the teaching a specific engine, and going to the practical part without explaining the actual theoretic concepts behind, which as mentioned I hope to be common in all engines. Let me know if you would recommend any.
In fact that is how I started, by placing 6 flat boxes afterwards I though that could be done with only 1 box⌠then decided to jump here
Thanks! I think I will be able to start something from here.
If you wish to learn real âdeepâ in how rendering works there is an excellent tutorial for openGL (rendering, shaders, etc.) it is easy too follow and provide real great results and knowledge witch you can apply to any engine : https://learnopengl.com/
Previous link is only about rendering stuff, but to create an actual game you also need structural logic (scene, hierarchy, component system, etc). Actually you can start right away and find info you need during the process, but when you want to create something that is little bit bigger then example scene then it is time people actually start getting frustrated.
If somebody have some good gamedev sources (about logic and structural stuff, or how to start game development in ârightâ way, maybe some patterns) - please, share.
We could actually start a different thread for this kind of links, or make a dedicated page in tutorials. To create a real game engine knowledge is not enough.
Is a free online book, It focuses in the logics. I have read most of this book. It could be useful even if you donât plan to develop a game, and just learn about how & where to apply software pattens. âŚAlthough I think the level in this forum is higher.
Hi @Modanung some progress of course, questions are too many Iâll keep them to the strictly necessary.
On the way, I saw in the source code there is some sample of materials/textures/etc, but very fewâŚ
Is there a larger catalog of materials somewhere else?
Materials are usually made by artists, and we Export them to Urho3D, via the AssetExporter, and most materials can be defined by the standard set of shaders that Urho3D provides - but we can always modify materials, and we can provide custom shaders too - Iâm getting there quickly.
I can code shaders, but I donât know Urho3D well enough to make magic just yet⌠it will happen soon.
I generally use the editor to create materials. You may want to get to grips with writing your own shaders for more control. Although the provided techniques can get you a long way when combined with some nice textures.
I generally dont use the editor yet, but materials associated with models tend to come from the artist, not the coder - Iâll try again on the editor issue soon, at this stage its nice enough for me to make things work
we load a model, we apply a set of materials to it ⌠its not really relevant where the art came from until it comes to selling your product, or showing it in public, thats the thing they donât teach until the bachelor year, the legal issues, like what is plagiarism, and what does an NDA mean to you
Thanks for welcome!
