Cannot display WebGL geometry via Three.js
Hello,
I have developed a three.js component that works without issue on chromium. On Firefox, part of it does not display.
<unable to upload images, the upload hangs <- happy to send via email>
See chromium.png for how it should look. In firefox.png you can see that it is missing the surface area. For reference, the 3d axes shown are three.js components also.
firefox_console.png shows issue loading webgl
firefox_console_after_force_enable.png shows the same after webgl.force_enable was set to True in the config.
Can you offer any advice here? Our customer is keen to continue using FF.
Thanks in advance. Scott
모든 댓글 (4)
Can you provide a working example, like https://jsfiddle.net/aybalasubramanian/6xwo2ksg/
Thanks.
Thanks for getting back to me TyDraniu.
I am having difficulty to make this work on fiddle with the number of components involved.
However I've narrowed the issue down to Firefox not using a datauri in place of a file, which is fed into a loader (PLYloader).
Hopefully the following will help to explain, using Sean Bradley's tutorial here:
https://sbcode.net/threejs/loaders-ply/
He is using the PLYloader to load an external .ply file. I am sidestepping a file and building a datauri instead. It seems to be this part that fails to load.
If you substitute 'models/sean4.ply' for
'data:text/plain,ply\nformat%20ascii%201.0\ncomment%20VCGLIB%20generated\nelement%20vertex%208\nproperty%20float%20x\nproperty%20float%20y\nproperty%20float%20z\nproperty%20uchar%20red\nproperty%20uchar%20green\nproperty%20uchar%20blue\nelement%20face%206\nproperty%20list%20uchar%20int%20vertex_indices\nend_header\n0%200%200%200%20255%20163\n1%200%200%200%20255%20132\n1%201%200%200%20255%20132\n0%201%200%200%20255%20132\n0%201%201%200%20255%20132\n0%200%201%200%20255%20132\n1%200%201%200%20255%20132\n1%201%201%200%20255%20132'
it gives a good representation of my problem. In chromium you will see two triangles, in firefox nothing is displayed.
Hopefully some images will attach this time.
Can someone advise how to chase this further? I would like to reach out to mozilla developers if possible.
OK, you can file a bug in https://bugzilla.mozilla.org/enter_bug.cgi