Hey there
I’ve been trying to use the THREE.BokehPass alongside with instanced geometry, however I’ve been running into some strange artifacts.
Take a look at this stack of oranges
There are 2 things that concern me:
The ground floor plane messes up the result of oranges, despite being behind them. There is an option to make it invisible just to showcase the difference
[Regarding instancing] When you move the camera around, you’ll notice that in the middle of the stack, there is a “glitched” orange. I think that is actually where the original one would be placed if it wasn’t instanced.
Edit: forgot to add, that the shape of the “glitched” object is always the same as the instanced mesh.
The bokeh was the last step for my project, so this setback is rather irritating. Does anyone have explenation for this? I would appreciate any help
Not sure. But I would suggest looking inside the implementation of Bokeh, it’s possible that it is drawing the geometry from the scene internally using a special material.
@Usnul thanks for the reply. It turns out you are correct and BokehPass is using this depth material to draw the objects
I tried applying this material as scene.overrideMaterial with renderer.render() (override material doesn’t work with EffectComposer and RenderPass ? ) and here are the results:
I guess that material doesn’t support instancing, renders only the original orange, but then blurs the instances as well, because they were passed through the tDiffuse. Since it doesn’t “see” them, the floor’s depth blends “through” them, which might explain my first point of confusion.
Gonna try to patch the depth material in the BotehPass next and see what I get
Personally I like better the default material.depthPacking (THREE.BasicDepthPacking), rather than the THREE.RGBADepthPacking, which seems to produce “wavy” results
