Shadowmap on ios

[expo]

Shadowmap on ios

[EvanBacon]

lol figured it out... just add this line before building the renderer, works on both platforms:

gl.createRenderbuffer = (() => ({}));

https://snack.expo.io/@bacon/three-shadows

[EvanBacon]

This problem came in SDK 25 when we shifted to using the native iOS framebuffer. I haven't tested to see if this was fixed in 26 - where we added support for OpenGL-ES 3 / WebGL 2.0.

[SvenJonsson]

I have the same problem at SDK 26, tried downgrading to expo SDK 24 and then SDK 23 but the issue remained to me. Can you confirm? @EvanBacon

[EvanBacon]

@SvenJonsson unfortunately EXGL versions work a little differently than the rest of Expo. EXGL is C++ that is used across both android and iOS, then bridged through the respective platforms, so downgrading doesn't work the same.
I'll take another stab at this tonight.

[bberak]

Hi @EvanBacon and @oosmoxiecode,

Did you find anything fishing going on with the z-depth/buffer after applying this fix?

Specifically, I'm finding the z-order gets messed up when using this fix and the EffectComposer with at least one shader pass.

Here is what my app looks like without any shader passes being applied. Notice the orange box gets rendered behind the blue platform when it falls.

Here is the same code with an additional sepia shader pass added to the effect composer. Notice that the box gets rendered incorrectly in front of the platform when it falls.

Removing the gl.createRenderbuffer = (() => ({})); line fixes the z-depth issue, but it causes other problems with shadows and some other shaders down the line.

I've tried this on both Expo SDK 27 and Expo SDK 31 - I get the same results.

Thanks in advance for any ideas/clues - and many thanks for all your work.

[tsapeta]

Hey guys, sorry for late reaction, but this issue comes like a boomerang so I investigated it more now 😄
My guess is that it's a duplicate of expo/expo#7502, so please see my comment there: expo/expo#7502 (comment)

If anyone is still working on it and can let me know whether the workaround works I'd be very grateful 🙏

EDIT: Of course gl.createRenderbuffer = (() => ({})); workaround is no longer valid, please use only the one from the comment mentioned above.