I feel it's a bit slower than it should be.
+-30fps... on something the size of a minecraft map.. is that right?
But.. something i'm thinking of using this for.
Mind explaining more..
Could I make 3D sprites? lets say 64x64x64 drawing multiple sprites..
IDK.. Just a cool idea I had to save time making and animating sprites.
As I could easily import images and convert those to 3d and make a editor for fine tuning VOXEL sprites!! =D
I have no idea where to begin with this.
Yes, sprites are the idea. The renderer uses only a minimal amount of geometry but because it renders the interior pixels, it can still be slow at high resolutions. A 256x256x256 voxel screen will actually only have 4*(256+256+256) = 3072 triangular faces (2 on each side of each cross sectional plane), despite being made of 256^3 = 16 million voxels. However, these faces are all overlapping and covering much of the screen. The texel transfer rate of video card becomes the dominant factor here.
A better strategy is to make a number of smaller, say 32x32x32 sprites, and render multiple copies of them. You can use VoxRenderVolume, or VoxRenderSubVolume in conjunction with glTranslate? to accomplish this for example. Additionally the Volume_Static may be useful if you don't intend to change a model after loading it or generating it. And of course you can mix conventional OpenGL graphics with voxel sprites. You can even use the VOXEL_NO??? flags with VoxRender or omit even calling it if you want to control the OpenGL states and matrices yourself.
Still, it is possible to make simple programs based on only a single central volume. But perhaps the 128x128x128 size I use in the Lines example is too much for some cards.