The first real opengl thing i ever did was make a thing to display Tiberian Sun and Red Alert 2 voxels. A voxel can be 255x255x255 in size, there designed for 2d. The Problem i have is the low fps, its perfectly fine for Tiberian Sun voxels but Red Alert 2 ones are normaly larger.

Im wondering if anyone has any ideas on how to improve speed, but still alow for animation (the voxels are animated by matrix's), voxels without hva's(the animation file) use the build list thing to improve speed.

Source can b found here: v 1.4 (unreleased) Source Code

To use the source you would need to download : OS : Voxel Viewer v1.3

EDIT: attached some voxels.

Screenshots:

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu

Why can't you use display lists for animated voxels? Since you said that animation is done by matrices, you can still use displaylists and just set the matrices before calling the displaylists. If that's a no-go, then take a look at VBOs that also can be used for dynamic meshes.

_________________
www.SaschaWillems.de | GitHub | Twitter | GPU Datenbanken (Vulkan, GL, GLES)

VBO? What is VBO?

VBO = Vertex Buffer Object. It's best described as a vertex array that's stored in VRAM. VBOs unite the best of display lists (speed, cause they're stored in VRAM) and vertex arrays (dynamic, and can be changed at will).

_________________
www.SaschaWillems.de | GitHub | Twitter | GPU Datenbanken (Vulkan, GL, GLES)

Hmm, might b able to just use display lists......... The voxes are split up into sections after all..... (hence allowing movement)

Does VBO work on very old cards? (Tiberian sun can be used on VERY VERY OLD PC's so my prog also has to be able to run on low end machines. Im guessing VBO can't)

_________________
Free Map Editor - Game Requirements - Stucuk.Net
-Stu