# Big Difference in Material/Environment Behaviour Safari vs Chrome

**URL:** <https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831>\
**Category:** Questions\
**Created:** [November 19, 2020, 8:03am UTC](https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831 "2020-11-19T08:03:22Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![mimeeq3d\_neal](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/mimeeq3d_neal/32/13877_2.png) [@mimeeq3d\_neal](https://forum.babylonjs.com/u/mimeeq3d_neal)\
**Post date:** [November 19, 2020, 8:03am UTC](https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831/1 "2020-11-19T08:03:22Z")

</div>

@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](https://editoffice.eu/products/?category=%2FDesk%20%26%20Storage&variantCode=WU-SEO-7%3Dwood-a2)  
you need to rotate the camera a bit to get the same angle I sent

**Screenshot Comparisons**  
Chrome Left and Safari Right

 ![Material Comparison Safari vs Chrome](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/2X/0/045fc500ffa2758e5229144d7e5471b71c7bb181.jpeg)

**Chrome**

 ![Mac Big Sur - Safari](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/2X/a/a322b19af77a148680631397cb883c964cccf607.jpeg)

**Safari**

 ![Mac Big Sur Chrome](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/2X/c/ce6d10b9b11aab7a5574c9c851be5d575fd038de.jpeg)

@mimeeq3d_milosz @xmac @Marcin_Zamelski FYI

---

<div class="post-metadata">

**Author:** ![mimeeq3d\_neal](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/mimeeq3d_neal/32/13877_2.png) [@mimeeq3d\_neal](https://forum.babylonjs.com/u/mimeeq3d_neal)\
**Post date:** [January 4, 2021, 4:41pm UTC](https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831/2 "2021-01-04T16:41:21Z")

</div>

@Cedric Happy New Year  
did you see this? Any ideas what might be causing that or could you point me in the right direction

---

<div class="post-metadata">

**Author:** ![Cedric](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/cedric/32/2742_2.png) [@Cedric](https://forum.babylonjs.com/u/Cedric)\
**Post date:** [January 4, 2021, 4:47pm UTC](https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831/3 "2021-01-04T16:47:08Z")

</div>

Hi @mimeeq3d_neal I wish you the best for this year 🙂

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.

---

<div class="post-metadata">

**Author:** ![mimeeq3d\_neal](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/mimeeq3d_neal/32/13877_2.png) [@mimeeq3d\_neal](https://forum.babylonjs.com/u/mimeeq3d_neal)\
**Post date:** [January 4, 2021, 5:54pm UTC](https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831/4 "2021-01-04T17:54:17Z")

</div>

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%.

Will be back later in the week with an update.

---

<div class="post-metadata">

**Author:** ![Marcin\_Zamelski](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/marcin_zamelski/32/4999_2.png) [@Marcin\_Zamelski](https://forum.babylonjs.com/u/Marcin_Zamelski)\
**Post date:** [January 18, 2021, 10:05am UTC](https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831/5 "2021-01-18T10:05:55Z")

</div>

@Cedric Yes, Safari is using WebGL1.

We tried using WebGL1 at other browsers to verify if it’s related to this.

And I was able to reproduce this issue on Chrome WebGL1.  
 ![chrome](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/2X/6/627b9a7f6d3df800ab855156a4d260d2fa4f5e01.png)

But Firefox WebGL1 is working correctly.

![firefox](https://us1.discourse-cdn.com/flex024/uploads/babylonjs/original/2X/c/ce4107835aabe9613068c92e8995b8170a4a6abf.png)

So I think this issue may be rather with WebKit/Blink than WebGL1 itself.

---

<div class="post-metadata">

**Author:** ![Cedric](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/cedric/32/2742_2.png) [@Cedric](https://forum.babylonjs.com/u/Cedric)\
**Post date:** [January 18, 2021, 11:08am UTC](https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831/6 "2021-01-18T11:08:25Z")

</div>

Do you have an idea about what’s causing this issue @sebavan @Evgeni_Popov ?

---

<div class="post-metadata">

**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\
**Post date:** [January 18, 2021, 1:29pm UTC](https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831/7 "2021-01-18T13:29:33Z")

</div>

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,

---

<div class="post-metadata">

**Author:** ![mimeeq3d\_neal](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/mimeeq3d_neal/32/13877_2.png) [@mimeeq3d\_neal](https://forum.babylonjs.com/u/mimeeq3d_neal)\
**Post date:** [January 19, 2021, 8:16pm UTC](https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831/8 "2021-01-19T20:16:21Z")

</div>

thanks all for the help  
@sebavan Safari will support webgL2 finally then?

---

<div class="post-metadata">

**Author:** ![sebavan](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/sebavan/32/57_2.png) [@sebavan](https://forum.babylonjs.com/u/sebavan)\
**Post date:** [January 19, 2021, 8:30pm UTC](https://forum.babylonjs.com/t/big-difference-in-material-environment-behaviour-safari-vs-chrome/15831/9 "2021-01-19T20:30:24Z")

</div>

It should… it is now enabled by default in the preview so high hopes… 🙂
