^indeed! Patience isn't what most of us have

im tired of no download can you release this even with the bug?

^indeed! Patience isn't what most of us have

I agree with them, the bug is only a displaying bug, not an irrevocable crash so a demo of this with the bug would already be awesome.

Also, I thought about something that may be a faster way to draw the cubes but I am not sure if that will work so I first need to know some things:
-can you draw arbitrary sizes of sprites with Ndless C ?
-can those sprites support transparency ?

Annoyingcalc, I can see you are fairly obsessed... With your avatar and all.... LOL

Yep and so are pretty much all my friends

I have a question of my own, how exactly are you 'sorting' the cubes to draw?  Are you actually putting their distances in a list and sorting them?

Yes indeed. I pretty much optimized the sorting algorithm, but if you know a better way, I would like to know it

Also, I thought about something that may be a faster way to draw the cubes but I am not sure if that will work so I first need to know some things:
-can you draw arbitrary sizes of sprites with Ndless C ?
-can those sprites support transparency ?

I don't think that ndless does that, but it's quite easy to code.
Why ?

Quote from: annoyingcalc on September 26, 2012, 08:58:02 pm

im tired of no download can you release this even with the bug?

Quote from: blfngl on September 26, 2012, 09:29:18 pm

^indeed! Patience isn't what most of us have

I agree with them, the bug is only a displaying bug, not an irrevocable crash so a demo of this with the bug would already be awesome.

Ok, ok, here is the current version (I also can post the source code, if you want)
It won't crash, but there are 2 known "bugs" :
-Sometimes a cube isn't sorted correctly so its display looks weird
-When you are too close to a cube, it isn't displayed

And you will notice quickly that the render distance is really short
I will add an option to render the full world to see your creations.

Controls :
-8 to go forward
-5 or 2 to go backward
-6 and 4 to strafe
-Arrows to turn the camera
-Tab to remove a block
-Ctrl to add a block
-+ and - to select a block (the type is shown in a little triangle in the top right corner)
-Esc to quit

Isometric 3D would look extremely weird and is not at all suitable for first person games.

Isometric 3D would look extremely weird and is not at all suitable for first person games.

Yes, but read my post again, there is the adaptation of the method for non-isometric 3d ("real" 3d).

Quote from: Chockosta on September 27, 2012, 11:39:15 am

Quote from: Hayleia on September 27, 2012, 01:10:32 am

Also, I thought about something that may be a faster way to draw the cubes but I am not sure if that will work so I first need to know some things:
-can you draw arbitrary sizes of sprites with Ndless C ?
-can those sprites support transparency ?

I don't think that ndless does that, but it's quite easy to code.
Why ?

Well I thought about a 3d drawing method that could speed up the game, but I am not really sure.
Basically, it is based on the isometric 3d idea.

In isometric 3d, all the cubes are the same, so you only need to draw one in 3d, then use the image of this cube as a masked sprite to draw all the other ones.

In non isometric 3d, one cube is not enough since not all the cubes are seen from the same angle, but one cube per line is enough. If you have n aligned cubes you draw one of them using your current 3d engine, then use the image of this cube as a masked sprite to draw the other ones, using some sprite scaling.

So basically, if you have n lines of m cubes each, you don't need to draw n*m cubes in 3d but only n cubes and n*m sprites.

Do you get what I mean (or is my English really bad ) ?

No, this wouldn't work (if I got it correctly)
Here is a screenie to explain why :

Your method would be to store a the cube A's projection then scale it and paste it on all the cubes in the blue row, right ?
This would only work if the red lines were parallel, since an homothety keeps the angles, but they aren't...
Moreover, calc84maniac is right, scaling is very costly

The source code would be interesting

Here you are
Sorry, my comments are too rare...