Right now I really dont care- All of that will not really be visible to the eye when there are many low poly objects in the game. As you can see an example of the level without my objects in, except for the dead trees so far. This is where all the fun and excitment comes in =D Importing all my objects into one big level.…
@Bombshell: everything can be learned, as does animation :) What software are you using? Why not just make the staff a child object of the hand bone which is "holding" it? I think in Blender parenting was done by selecting the two objects and pressing CTRL+P or something like that. I use it all the time but for some reason…
A low poly bedroom (WIP) for the interior of a house. I'm making the timelapse of each object of the room: https://www.youtube.com/playlist?list=PLzIHC2X5j0G8mhdI8wf03ThfGUkk3tbUx
@Egafgo The elements (continuous pieces of geometry) of a model don't have to share vertices, they just have to be considered a single selectable object in your application so as to avoid extra draw calls. For each material on each object being rendered another draw call is done, more draw calls = worse performance. That's…