Created attachment 452797 [details] A video of the bug happening This BabylonJS playground and others work fine on iOS 15.3: https://playground.babylonjs.com/#RLBZPF On iOS 15.4 beta 3+, drag the camera around with touch and the problem will become clear with the screen drawing over itself several times. The Babylon team says everything seems fine in the gl stack. Attached is a video of the bug.
<rdar://problem/89311294>
I wonder whether this might be fixed with the ANGLE roll forthcoming in Bug 235746. Several issues have been fixed upstream in resolving of multisampled renderbuffers to textures.
(In reply to Kenneth Russell from comment #2) > I wonder whether this might be fixed with the ANGLE roll forthcoming in Bug > 235746. Several issues have been fixed upstream in resolving of multisampled > renderbuffers to textures. Still happening in beta5.. not sure if this change you mentioned is in there yet.
I see a similar problem on three.js v128, on both iOS 15.4, iPad OS 15.4, and macOS 12.3 (on M1 Mac). These problems were not three in previous os versions. Can provide steps to reproduce: also, the problem is with gltf models with transmission, i.e. that require the renderer to render to multi-sampled texture.
The bug reports are beginning to flood in various Babylon features broken in 15.4. Thousands of devs rely on this library for commercial projects, would be good to fix ASAP :/
likely related https://bugs.webkit.org/show_bug.cgi?id=238022
On an M1 MacBook Pro and Safari Technology Preview Release 141 (Safari 15.4, WebKit 17614.1.3.8), with "WebGL via Metal" turned on, this example renders correctly. Perhaps this configuration isn't reproducing the same problem seen on iOS. It also renders correctly on Chrome Canary 102.0.4952.2 (Official Build) canary (arm64) with --use-angle=metal.
Thanks for the report. Even though Ken reports no repro on his side, I'll start this with the assumption this is related to the 15.4 msaa regression, linked to in the depends on -section.
Confirmed this is fixed in https://bugs.webkit.org/show_bug.cgi?id=238171
This fix shipped with Safari 15.5 (all platforms).