[x3d-public] New volume rendering extension proposals - more work needed

Patrick Dähne pdaehne at gmail.com
Wed Jul 17 05:49:31 PDT 2019

Hello all,

I do not understand the need for an ImageTextureAtlas node, and therefore would object to the integration into X3D.

The X3D Volume rendering component currently requires an X3DTexture3DNode to provide the voxels. So why not simply implement one of the existing 3d texture nodes, instead of introducing yet another node? That’s possible even on WebGL. When WebGL2 is available, 3d textures are directly supported in hardware. If only WebGL1 is available, it is a trivial task to emulate 3d textures by automatically creating a texture atlas internally. That’s how other engines do it, and I do not understand why this approach cannot be implemented in x3dom.

Best regards,


More information about the x3d-public mailing list