I am having troubles with the opacity map on IOS devices with the latest IOS version (15 at time of writing).
The opacity just doesn’t seem to get applied, whereas the very same code works on IOS devices pre version 15 and windows PCs or android devices.
Here is my example: Babylon.js Playground
Sprial correctly shown on IOS version < 15:
Torus shown on IOS version 15:
Sry for the long loading times, the example is from a larger application and I wasn’t able to simplify the GLBs on my own.
Any ideas what’s going wrong?
Maybe I am just missing a setting which has become required.
Hi @msDestiny14, well it actually should work on desktop too.
Which operating system / browser did you use?
Concerning loading times, I tried it on my laptop (Windows10 / Chrome) and on some iPads (IOS V14 / V15) and it always loaded between 10-15 seconds.
Not sure in which constellation it would load 6 minutes.
We found out that the issue seems to be related to the usage of KTX2 compressed textures.
The ring on the left side uses “normal” textures, on the right side the textures are compressed.
In IOS15 the opacity map is not correctly applied to the right ring.
Maybe it is a problem when using a combination of compressed textures + sRGB buffers. Try to put this code in the PG and see if that helps (it disables sRGB buffers):
The problem really seems to be related to the compression format of the KTX2 textures.
Our 3D artist re-created the textures in multiple formats as explained in these docs and examples:
After that it worked!
The individual formats contain textures with different colors, so we can see which KTX2 format is used on which device.
Green = png
Blue = dxt
Pink = astc
Red = etc2
…the spiral on the iPad was drawn pink, so it used ASTC, which is what we would have expected.
Here is the updated playground example: https://playground.babylonjs.com/#E2FYTU#35
Anyway this ticket can be closed.
Thank you all for your help!
@bghgary
Thank you very much for all the support you guys are giving us
Should we write a bug report in GitHub for this then incl. the reproduction demo etc. from here to have a central place to follow future development around this?
Just FYI: I’m a colleague of @TheHOF and I have also been following the discussion here with much interest.
Well, I still haven’t had time to look into why it’s broken. So, it’s hard to know which side is the problem right now. I will try to find time to look into it today or tomorrow.