How to clear a texture3D?: Page 2 - Godot Community Forums

How to clear a texture3D?

xyz

But why go through all this just to toggle voxel visibility? That engine probably has voxel visibility control. Just set it directly on voxel. Going through shader with 3d texture is highly redundant... unless you plan to use it for ray marching or something like that.

itgiawa

@xyz good idea, I'll run it by Zylann and see if he thinks I should be doing this in the CPU. I don't plan on using it for raymarching.

xyz

You're already doing it on cpu, since according to your code, cpu already knows the visibility. You're effectively delegating something that is per-object decision to a needlessly repeated per-pixel decision. And in a very roundabout way that loads more work on both; cpu and gpu.

Yeah, check if there is a way to toggle voxel visibility via the engine, and just do that :)

itgiawa

@xyz Yeah you're right. However, I think actually the best option may be to wait for occlusion shading, which appears to be coming in 4.0: https://www.reddit.com/r/godot/comments/mcjspo/occlusion_culling_is_finally_coming_to_godot/ In theory, with that, I can do it all in the GPU...

xyz

Occlusion culling may not be directly usable for your thing. It really depends on how it'll be implemented. But if you can wait until 4.0, sure, try it out.

I'd still check with you current voxel engine and implement the simplest possible solution that utilizes capabilities of the engine. The engine most likely supports sending some custom data to the shader on per-voxel basis. Just use that mechanism so hide the voxel.

cybereality

You don't need occlusion culling for this. Voxels are on a grid, it should be fairly simple to determine visibility. Actually, I wouldn't be surprised if the voxel engine already supports it somehow, seems like the first optimization to do (if it doesn't, that's a pretty big red flag).

xyz

I peeked at the voxel engine docs. It looks quite competent, and critical code is native, I think.

« Previous Page