Regression: logarithmicDepthBuffer issues in v181, not present in v180 -- "cut" sprites

[PoseidonEnergy]

Description

I have a three.js scene with many small sprites scattered across a large terrain using InstancedMesh objects, and I occasionally enable logarithmicDepthBuffer to get some good screenshots of the scene. Otherwise I mostly keep logarithmicDepthBuffer disabled as it causes significant performance issues.

Anyway, I recently upgraded from three.js v179 to v182, and I noticed that starting in v181, with logarithmicDepthBuffer enabled, my sprites get "cut" when viewed at an angle.

I can say with 100% certainty, that the bug is NOT present in v180.

Here is a minimum reproducible example at JSFiddle:

https://jsfiddle.net/L602b3jh

Alternate the importmap URLs between three@0.180.0 and three@0.181.0 to see the difference between the versions.

Did anything change regarding logarithmic depth, or depth in general, between v180 and v181 of three.js that may be causing this?

Here is a screenshot comparing my scene in v179 and v182. The only change between the following two screenshots is the three.js version--the scene construction code is identical.

Version

r181

[PoseidonEnergy]

Update: added JSFiddle link for a minimum reproducible example: https://jsfiddle.net/L602b3jh

[Mugen87]

After some testing I can confirm reverting #32109 fixes the issue. Since the PR is not directly related to logarithmic depth buffer, it seems to have a side effect we are currently no aware of.

[sunag]

I'm checking, it seems that the once() method of positionView is not being reapplied in the fragmentation stage of that code. Now that we're using clipSpace for positionView.z, this should be necessary.