Voxelizer shaders apears to be broken. about testbedhdrp HOT 4 CLOSED

This repository currently maintained with Unity 2018.3.0 and HDRP 3.3.0. It may not work on other versions because HDRP is under heavy development and has many compatibility-breaking changes between versions.

I'd recommend using the revision at c641e6b if you'd like to use HDRP 3.0.0. It's the last commit before updating to 3.3.0.

from testbedhdrp.

This repository currently maintained with Unity 2018.3.0 and HDRP 3.3.0. It may not work on other versions because HDRP is under heavy development and has many compatibility-breaking changes between versions.

I'd recommend using the revision at c641e6b if you'd like to use HDRP 3.0.0. It's the last commit before updating to 3.3.0.

Hi, I already was using that revision. It seems that the fragment shader is not right. When I move the camera the object goes completely transparent.

from testbedhdrp.

Okay. Some thoughts:

• The custom shaders only support deferred lighting path (with FPTL), so if you're using the force-forward mode, it will get black. I'd recommend checking if it works with the default HDRP settings.
• The custom shaders don't affect bounding boxes. It's recommended to expand the bounding box when using these kinds of animated effects to avoid being culled.

from testbedhdrp.

Okay. Some thoughts:

• The custom shaders only support deferred lighting path (with FPTL), so if you're using the force-forward mode, it will get black. I'd recommend checking if it works with the default HDRP settings.
• The custom shaders don't affect bounding boxes. It's recommended to expand the bounding box when using these kinds of animated effects to avoid being culled.

Oh wow Yes. It seems that I had forced forward on due to some other experiments. Thank you 👍

from testbedhdrp.