Voxel models problems (not bugs)

[Devan]

Voxel models in eduke32 or JFduke are loading too long. I don't want to make worse quality because then quality will be too bad. Is there some way to fix that problem? Because I like KVX's in classic software mode much more than MD2's and MD3's in OpenGL

[TerminX]

They take forever to load because they are converted into rather high poly models at load time.

[Devan]

Is this important only for polymost?

[Devan]

I've got one more problem: I converted some more models to KVX. They have very good quality, but this brokes the palette. When I switch fullscreen off then all colors are ok. I need correct colors in fullscreen!

[Devan]

The third problem: there are too many voxel models with perfect quality, and when I try to start Eduke32 it loads voxel models and startup window disappears. In eduke32.log file I found: ERROR: CACHE SPACE ALL LOCKED UP!

[TerminX]

The palette thing is a long-standing bug that neither JonoF nor I have been able to figure out as of yet. As for the other problem, simply don't use so many voxels.

[Devan]

will these problems be fixed? I'm making big voxel model pack. When I will finish it, I will upload it somewhere and everybody will be able to download it.

[TerminX]

They aren't problems, they're limitations. I suggest using less voxels. Each one requires a chunk of memory in Build's cache system; the cache is 32 megs in size and is shared by the sounds and 8 bit art tiles. The cache size will be reduced to 16 megs when JFAud is complete as the sounds will no longer need to be cached there. Increasing the cache size is not an option as it would then leave less memory available for higher resolution resources such as hightile textures or MD3s.

Again, use less voxels. ;)