I want to point out two different issues/bugs I have encountered with BabylonJS version (5.0 - 5.5.5) and iOS 15.4.1 and Safari 15.4 and BabylonJS version < 5.0.
Basically SSAO2 does not properly work. You can try switching it on and off using the 1, 2, 3 keys on keyboard from the playground example and you will see that when pressing 3 (drawing only SSAO) with make the scene go completely blank/white. If you choose a BabylonJS version less than 5.0 it will work properly. https://playground.babylonjs.com/#7D2QDD#28
Another issue is that on BabylonJS versions less than 5.0 the input controls will not work at all on iOS 15.4.1 and BabylonJS version less than 5.0. I have no idea why this happened but I had to upgrade to the latest BabylonJS version to fix this issue. https://playground.babylonjs.com/
The thing is, on my scene I am using SSAO2 and when upgrading to the latest BabylonJS version in order to fix the input control issue on iOS 15.4.1 I encounter the SSAO2 issue.
Can someone please tell me what is up with SSAO2 on BabylonJS 5.0 - 5.5.5?
You need to disable antialiasing on IOS 15.4.1 as Safari as a huge webgl issue internally. It has been fixed on webkit but still Apple did not release the patch in a new IOS release. I have great hopes for 15.4.2…
antialiasing shoudl be disabled in the Engine constructor of Babylon.
Sorry, but SSAO2 is not working properly for me even on chrome desktop(windows) as well. And this only happened after I upgraded BabylonJS to 5.0 and 5.5.5. So I think this is a bug in Babylon right?
Just to make this clear, you’re still speaking only about SSAO2, right?
Because for me, SSAO is still working the same (and I actually prefer the render from SSAO). Personal opinion only.
I believe I could. I haven’t tried but I trust you on this. I previously experienced similar issues with SSAO2 (where rendering the layer alone would do nothing) but in fact, that didn’t mean it was not working (in real or in combination with the other textures). But I believe you checked in your scene, right?
I actually cannot create a playground with my setup or how I’m actually using the SSAO2.
But the playground example alone shows that there is something wrong going on with SSAO2 when it goes completely blank when drawing only SSAO2 by pressing 3.
Basically on my scene I am attaching a camera to the SSAO2 Rendering pipeline and then trying to take a screenshot. The moment I try to screenshot I get an error as below: