defaultPipline.imageProcessing + individual imageProcessing for Material = weird result

Hold my beer :arrow_right: Playground :grin:


More seriously, I was having a look at this topic where a nice solution to your problem was given, but indeed it was said that it’s not working for MSAA. And indeed, it the related Playground a resize is as well triggering a freeze.


My solution is not really neat, since it appears MSAA doesn’t support the resize, what I did is a disposal of the different element including rendering targets and defaultPipeline, and reassigning them, using the engine.onResizeObservable trigger :slight_smile:

++
Tricotou

PS : @Deltakosh : :fire: link :smile:

2 Likes