MSAA disable when turn on other postprocess dynamically?

Questions
1

Using samples = 4 after creating DefaultRenderingPipeline that’s perfect effect on my project. When i try to turn on other postprocess(bloom, sharpen, chromaticAberration…) dynamically, the antialiasing didn’t work anymore. No matter how to setting samples, it had no effect.

2

Do you notice the same effect here - https://playground.babylonjs.com/#Y3C0HQ#650 ?

3

@DWork this definitely sounds like a bug, could you repro in the playground ?

4

I’m so sorry that my project can not be post to PG, because it’s too large, but the way to create postprocess just like PG https://playground.babylonjs.com/#Y3C0HQ#650. I had compare to the examples for all properties in DefaultRenderingPipeline, the result was almost the same. It’s has been over one week, i found nothing. I suspected there’s something wrong with ‘_MSAAFramebuffer’.

5

I ll have a look shortly

7

@sebavan I had found the problem my project. I added MotionBlurPostProcess in my project that the samples of mobtionblur will override DefaultRenderingPipeline. Is there any way to solve this conflict?

8

Let s add @julien-moreau to the thread as he is the daddy of the motion blur.

11

Hi @DWork !

Can you try to set the same samples count in the motion blur post-process? Like myMotionBlurInstance.samples = myDefaultRenderingPipelineInstance.samples.

Maybe the Default Rendering Pipeline and Motion Blur are not using the same render target textures. The MB post-processes uses at least geometry buffer renderer or pre-prepass renderer

1 Like
12

Hello @DWork just checking in if you had a chance to try Julien’s suggestion :slight_smile: