Open josefheks opened 2 years ago
Some further investigation has revealed it is related to this https://github.com/mrdoob/three.js/issues/19754, and can be fixed by forcing the WebGL1 renderer: https://threejs.org/docs/#api/en/renderers/WebGL1Renderer
Would be great to get some confirmation about this, and any future plans to amend so that it is compatible with a WebGl2 rendering context.
Hi @josefheks
The fix you've identified is indeed appropriate in this case.
We don't have any plans currently to upgrade this codebase to support WebGL2.
We are however working on a new web codebase that will support both WebGL1 and WebGL2. Unfortunately since this is early in the development phase, I can't give a timeline on when it will become available.
I also tried updating three.js used and hit this issue. I could get THREE.BufferGeometry rendering the vertices but not the actual faces as I got stuck at updating the now deprecated THREE.Face3 callbacks https://github.com/juniorxsound/Depthkit.js/issues/21
I seem to be having issues running on more recent versions on Three.js.
Particularly wanting to get it to run on r123 in a desktop browser (Chrome) and encountering this shader error: