question about voxels...

[Devan]

Why do voxel models take a long time to load?

[TerminX]

Because Polymost requires that they be converted to polygons at load time.

[Awesoken]

My voxel rendering code for OpenGL tries to reduce the polygon count by combining neighboring coplanar faces. At load time, I generate a skin to hold the color data for all the little pieces of various sizes. Doing this allocation is a tricky process, and that's what takes most of the loading time.

My allocator is far from optimal. It works fine for low-res voxel models, such as the ones that come with Shadow Warrior. For higher detail models, you really ought to use MD3 format. I love voxels and their nostalgic look, but they don't make sense in OpenGL.

The loading process could be sped up by using a cache for the skin and related voxel data.

[Devan]

Originally Posted by TerminX

Because Polymost requires that they be converted to polygons at load time.

Can you add ability to eduke32 to turn this converting off? And ability to increase cache size to load better quality voxel models? I also love voxels.

[Mr.Fibbles]

I think Ken said it best:

For higher detail models, you really ought to use MD3 format. I love voxels and their nostalgic look, but they don't make sense in OpenGL.

from the man who made voxels.
asking to turn off the converting required by the rendering engine doesn't make sense to me.

[Mblackwell]

Originally Posted by Devan

Can you add ability to eduke32 to turn this converting off? And ability to increase cache size to load better quality voxel models? I also love voxels.

You couldn't do that and still run in OpenGL. If you don't want them to be converted to polygons... run in Software mode.

[Devan]

Originally Posted by Mblackwell

You couldn't do that and still run in OpenGL. If you don't want them to be converted to polygons... run in Software mode.

I talk about other thing. I like voxels in 8-bit but eduke32 ALWAYS at startup converts voxels to polygons, so I have to wait a minute or more

[DavoX]

Ken, is there any way to merge the Eduke32 code with that program you made a while ago, where you could destroy all the environment shooting at it? It would be cool to have some selected walls where we could do that in Duke3d.

It could be implemented like a special sprite wall that looks 3d and you can shrink/expand in Mapster, just like any 3d Model. I dunno about the textures, would it be difficult to be able to select any texture from duke to a voxel sprite in Mapster?

[drvarek]

I really doubt it. Theoretically it is possible, but theoretically dynamic lightning is also possible in duke, so i think you have your answer.

[DavoX]

Originally Posted by drvarek

I really doubt it. Theoretically it is possible, but theoretically dynamic lightning is also possible in duke, so i think you have your answer.

Dynamic Lightning has nothing to do with voxels. They aren't that familiar with the Code needed for Dynamic lightning. But Ken IS very familiar with the voxels code for instance it's more possible.

[DeeperThought]

Originally Posted by DavoX

where you could destroy all the environment shooting at it? It would be cool to have some selected walls where we could do that in Duke3d.

It's already possible to make destructible sprite walls / bridges / structures in EDuke32. One way would be to build the walls by stacking up "brick" models, then add some code to make them behave appropriately when they are hit.

[Awesoken]

Ken, is there any way to merge the Eduke32 code with ... (Voxlap)

Sorry, but mixing Polymost and Voxlap isn't going to happen. I have better things to do with my time.