Mythruna

Hi im the new guy :)

Im looking forward to see this game released and buy it! :D

But one question really goes through my mind since i saw it...
I am a quite good programmer myself.
I really have written many lines of code in most programming languages
I have also fooled around a lot with JMonkey myself :)
BUT how the hell does he reach that performance???

That must be millions of Geometry or Spatial Objects (Blocks) with each 4 Vertices and 6 Faces...
I added 1 million Geometry boxes to the RootNode for fun and it died already at creation with "out of memory" exception...
I cant even imagine the performance if i could have used the fly cam...

How The Hell does he reach that perfect performance?  ???

I truely appreciate your answers as this leaves me no rest  ;)

This comes up on the JME forum so often that someone added hover text for "block world" that pops up "Block worlds are not made of boxes".

And they aren't.  They are made of air-facing quads batched into single large meshes.

If you press F11 in Mythruna you can turn on the detailed JME style stats.  It will show you how many objects and how many triangles there are.  Unless you've placed a LOT of custom objects, you should only see several hundred objects but millions of vertexes.  I think the initial single player view has a few hundred thousand triangles... and maybe 400-500 objects or something.  (Objects are JME Geometry objects in this case.)

The concepts are fairly straight forward but I still say the block worlds are the hardest type of game to write for still-learning 3D developers.

Mythruna also makes it more complicated because all of the odd block shapes.  Efficiently finding the non-air exposed faces is trickier then a simple block->block check.

Thanks a lot for your fast and informative reply!

Now that you say that this is one of the FAQs on JME Forum i start to realize that i behaved like a newbie -.-
It just overwhelmed me to just ask you :)
Sorry for that...

Question answered.
Thread closed.
Donation coming.

No big deal.  Sometimes our excitement outweighs our ability to find the most productive path to answers. :)

Some people have also posted some block engine code to the JME forums.  I hear it's tricky to get running and is probably pretty basic... but might be worth a look.  Something called bloxel or something like that.  Search voxel on the forums and you'll get a ton of hits, I think.

Im on it.

Thanks a lot!
This will be an interesting week  ;D

Once I started reading this I thought "Sides that you aren't facing on 6 faced squares don't show! So of course the speed would be good!"

It's not really about facing.  It's about eliminating the sides that will never show because they are between blocks.  The back faces are still part of the mesh but the GPU takes care of not rendering them.

But if you have a 2x2x2 block of cubes, there are 24 quads that you don't even need to draw... out of 48 possible quads (8 cubes * 6 sides each), that's a pretty significant savings.  And the savings is even better for larger blocks where cubes are entirely embedded.