I'm using cycles.

Try duplicating the VDB object and leaving it in the same place. Then when you enter rendered mode you should end up with a bunch of artifacts. (I'm aware that 2 objects should never be in the same place, but it's the easiest way to replicate the issue).

As for the viewport clipping, I think that has something to do with large-scale scenes. It seems to show the clipping at the back of the VDB on top of the front of the VDB.

To fix the viewport clipping, you can change the clip start and end settings for the camera or view.

To fix the boxy look, you need to increase the maximum number of steps allowed for volumes.

Before	After

Using 3.1.2, on CPU and on GPU, I can confirm the issue of artifacts when the volume is duplicated and left in the exact same spot.

In T97061#1336260, @Ethan Hall (Ethan1080) wrote:

To fix the viewport clipping, you can change the clip start and end settings for the camera or view.

Ah yea this works. However, it seems to show the back clipping in front of the "unclipped" volume.

With other objects, the unclipped is shown in front (as it hasn't been clipped)

but with volumes that doesn't seem to be the case.

@Christopher Hosken (Cjhosken) Bug reports should be limited to one issue. I have created a new report (T97094) for the overlapping VDB rendering artifacts with a minimal test file that reproduces the issue. You can change this report to focus on the clipping issue, if you are still not able to resolve it.

@Christopher Hosken (Cjhosken) Is the clipping issue resolved by adjusting the clip planes?

If the entire vdb fits within the clip planes, then everything is fine. But in cases where the back of vdb doesn't fit within the clip planes, it cuts out the front of the vdb too.

I don't think you should rely on volumes getting clipped in the same way as geometry, they are rendered differently, so I don't think this will be considered a bug. We can continue investigating the main issue in T97094.