Thanks!

since the AFRAME 1.5.0 => 1.6.0 the stencil-code of the https://xrfragment.org demoviewer is now in a catch22: if I enable stencil:true:

• it works in the desktop browser on my laptop (also in VR-mode via WebXR extension)
• randomly renders meshes on quest 2 in immersive-mode only

Any idea whether there some other factors at play here besides bugs in my stencilcode?

@coderofsalvation Three.js changed the default to no longer create a stencil buffer. This PR simply adds a way to re-enable it. So with stencil: true it should be how it was before.

The regression in your case is probably caused by a different change (possible in Three.js). Quickest way to find out is using git bisect to pinpoint which A-Frame commit introduced the problem for you.

@mrxz thanks for reminding. So yes it seemed to work when I set stencil: true in desktop-mode, but not in immersive mode (because of the latest included THREE-version I guess).
I've did a new build of the master-branch, and it seems it is no longer randomly rendering meshes [but there's still stencil-shenanigans in immersive mode on Quest only].
Thanks I will investigate further with git bisect.

UPDATE

Indeed THREE seems to be the culprit

$ git bisect start
$ git bisect good # did this a couple of times [and retried]
$ git bisect bad 
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[e08045481417d494c5e91ac53b36e8d453692c7d] Bump three to r163