Chris
Member
|
Improved memory storage for Image3d
Hi,
How are Image3d's encoded in memory? It'd be good if I could have specific details to explain this data:
With: createTry(...,IMAGE_B8G8R8A8, IMAGE_3D))
Model 1: Alien
696 x 551 x 187 506,804 K
773 x 611 x 206 636,680 K
1015 x 801 x 270 1,245,132 K
Model 2: Tank
235 x 214 x 441 419,228 K
386 x 350 x 726 1,123,692 K
And (depending on above answer) is it possible to improve the memory encoding for it; e.g. with run-length/bit-change encoding?
Thank you,
-Chris
(This post was last modified: 12-17-2010 01:19 PM by Chris.)
|
|
12-17-2010 01:15 PM |
|
Esenthel
Administrator
|
RE: Improved memory storage for Image3d
They are stored as non compressed
I will not add rle.
|
|
12-17-2010 01:33 PM |
|
Chris
Member
|
RE: Improved memory storage for Image3d
Why no compression - is it performance/the way they're rendered? Or just too much to do..? Will it be done in the eventual future/ when voxels get added to the roadmap etc?
I'd have to implement a custom solution myself - but I guess that means not drawing voxels (not the end of the world - just using them as helper memory). Is there a way to access your GPU voxel renderer with a custom storage structure?
Thank you,
-Chris
|
|
12-17-2010 01:54 PM |
|