Artifacts using camera Depth of Field lense effects

Bugs
#1

Hello,

When experimenting with camera filters (DoF), I’m seeing artifacts that seem to come from the intersection of my meshes and some hidden near and far focal planes.

While researching, I noticed that the playground link in the documentation exhibits the same issue. https://playground.babylonjs.com/#DX6AV#4

Tested with Chrome and Safari using Macbook Pro
w/ Radeon Pro 555X 4 GB Intel UHD Graphics 630 1536 MB.
Babylon.js v4.1.0 - WebGL2

Any thoughts?

Thanks,
Skrapper

#2

pinging @sebavan

#3

As the issue is on the lens rendering pipeline let me add @julien-moreau who built it

#4

Hey @sebavan @TheSkrapper unfortunately I’m not the author of that pipeline. I can take a look and try a fix but I’m pretty busy on the Editor right now as the release is coming soon. @sebavan I don’t know how you are busy but maybe you’ll get it working faster than me ^^

#5

@TheSkrapper could you highlight the artifacts on a screenshot ? I am not sure to see them locally, also did you try the defaultRenderingPipeline instead to get DoF ???

#6

@julien-moreau you used it a lot so I thought it was you creating it :slight_smile: sorry about that

#7

@sebavan absolutely not, only standard and default rendering pipelines ahahah I just know nothing about this pipeline unfortunately ^^

#8

Ohhhh yes Standard and not Lens !!! :slight_smile:

1 Like
#9

image
image1404×604 154 KB

The following is from https://playground.babylonjs.com/#DX6AV#4

#10

I’m new to understanding pipelines. I’m using the following:
lensEffect = new BABYLON.LensRenderingPipeline(‘lensEffects’, parameters, this.scene, 1.0, this.scene.cameras);

#11

I effectively reproduce on my iPhone 11 as well
Looks like it is not device-based and that’s good to know!

#12

I unfortunately can not repro on my device :frowning: What device are you using @TheSkrapper ?

#13

Tested with Chrome and Safari using Macbook Pro
w/ Radeon Pro 555X 4 GB Intel UHD Graphics 630 1536 MB.
Babylon.js v4.1.0 - WebGL2

#14

A fix should be in the next nightly

#15

@sebavan was this fix added into 4.2 at all? Or just 5 alpha? Experiencing the same issues described above in 4.2 right now

#16

4.2 was already shipped when the fix was done, so it’s 5.0 only.

2 Likes