@Cedric
I hope you can shed some light on this one
See below the comparison to the same product on Mac os Big Sur Safari vs Chrome
I spotted this for the first time but I cannot say if its since updating to Big Sur or it’s just I started using Safari allot more since then that made me spot this.
Perhaps you can shed some light on this?
Running Babylon 4.1
Link to product
you need to rotate the camera a bit to get the same angle I sent
Screenshot Comparisons
Chrome Left and Safari Right
I don’t know how I missed your message.
Anyway, top of my head, this can be caused by a difference of webgl version.
I guess webgl1 on safari and webgl2 on chrome. Can you check it’s the case?
If it’s the case, can you also check that you get the same rendering as safari with chrome + webgl1 forced?
I’d like to see if it’s because of webgl1 or because of safari.
Also, babylonjs 4.2 has been released. I don’t know if you plan to upgrade.
No problem @Cedric and thanks for coming back so fast now.
That’s a good question
I will ask @Marcin_Zamelski to check ref WeBGL 1 vs 2 is the issue or it’s purely safari.
He is off till Thursday.
Ref Babylon 4.2. We do however we have to make a long test before updating since we have many connected parts of the whole app and we need to be sure all is working 100%.
It might be due to Safari not interpolating accross cube map faces in webgl… so not much we can do but their move to angle to support webgl2 which should now be real soooon will address it,