Cesium: OIT not working correctly in Firefox

Created on 16 Nov 2016  路  13Comments  路  Source: CesiumGS/cesium

Blending vs. OIT
good
bad

I have only noticed this on Firefox so far, but will check Chrome on a different computer later.

type - bug

Most helpful comment

As a workaround, try setting orderIndependentTranslucency : false when constructing the Cesium Viewer widget.

All 13 comments

Is this new in Firefox? It may be a bug in Firefox or a change in the Firefox WebGL implementation that exposed a bug in OIT.

Yeah this is new, at most about a month.

Also reported here: #4718

A temporary workaround in my case was to update the about:config property
webgl.disable-extensions = true

see pjcozzi's comment below, it's a better solution.

Last comment... I still needed to disable extensions. Although orderIndependentTranslucency corrected transparency issues, I was losing outlines on some polygons, and was having some performance issues with picking.

Setting webgl.disable-extensions = true in my browser also fixed the issue. Though it is not really a workaround since we cannot ask users to change it in their browsers.

As a workaround, try setting orderIndependentTranslucency : false when constructing the Cesium Viewer widget.

@pjcozzi that workaround works great on my system.

also reported here: https://groups.google.com/forum/?hl=en#!topic/cesium-dev/Kd3gJciiCkQ

We should probably look into this sooner, rather than later.

I noticed Firefox is spitting out tons of the below errors (and I believe this is a new development). Maybe there's a bug in some new code they added.

Error: WebGL: texImage2D: Incurred CPU row conversion, which is slow.  Texture.js:147:17
Error: WebGL: texSubImage2D: Incurred CPU row conversion, which is slow.

Last update:

  1. The above errors occur even when OIT is off
  2. The rendering problem still happens even with ANGLE off
  3. Possibly related to #3068

@jroetman @jmgomezpoveda this should be fixed now via #4762. It will be in Cesium 1.29 on January 2.

Yeah this works fine now in Firefox 50. Thanks!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lilleyse picture lilleyse  路  4Comments

pjcozzi picture pjcozzi  路  4Comments

thw0rted picture thw0rted  路  4Comments

jony89 picture jony89  路  4Comments

mcenirm picture mcenirm  路  4Comments