depth is always zero from three 134->135

[alexpineda]

I'm currently in the process of migrating to 133 to 136 in three. From 134->135 my custom effect no longer functions because the depth value coming from main differs

void mainImage(const in vec4 inputColor, const in vec2 uv, const in float depth, out vec4 outputColor) {

I'm wondering if anyone knows what changed in three from this version. I've poked around and see a lot of changes in renderer nothing I really understand, and their migration guides don't mention anything in particular.

My implementation: https://github.com/imbateam-gg/titan-reactor/tree/dev/packages/titan-reactor/src/renderer/fogofwar

I noticed in 6.23.4 that there is a comment:
Changed format of noise textures to RGBFormat to avoid issues with LuminanceFormat.

My fog texture happens to be LuminanceFormat. Is there some other single byte format I should be using?

[vanruesc]

I'm wondering if anyone knows what changed in three from this version.

I haven't investigated this yet, but depth texture support might be broken when multisample anti-aliasing is enabled (via multisampling). The reason for this could be that texture management was changed to use gl.texStorage2D() in three r135 due to issues with SRGB8_ALPHA8.

My fog texture happens to be LuminanceFormat. Is there some other single byte format I should be using?

You can use RedFormat if you're using WebGL 2. Otherwise, just stick to RGBAFormat because three recently removed support for RGBFormat.

[alexpineda]

Thanks for your response. multisampling at 0 did not rectify the issue unfortunately.

[alexpineda]

The latest version 6.24.0 has resolved this thank you such much. 🎆 👍

[alexpineda]

just wanted to showcase some of what I'm doing with postprocessing, using depth of field and scanline 👍

[vanruesc]

Nice, thanks for sharing!