4 ms·

There seems to be some missing triangles after a while (10-20 sec.) on Chrome on OSX Are these caused by some z-buffer issues caused by increasingly large coor

• erkaman 10y ago
  I think it has something to do with the z-buffer. My other theory is that WebGL is not given enough time to upload all the geometry, as the camera traverses the world and adds more chunks. I am not really sure what causes it...
• Baristan 10y ago
  It does looks like float32 errors from moving the camera too far in a scene. Seen it before while trying to create an infinite city in WebGL. I ended up creating a world offset for each sector, and every time the camera's position was more than a sector length, reposition the camera in the scene and adjust the sector offsets. May not be the best solution, but it was quick and worked.
  • astrange 10y ago
    You can use fixed-point math to avoid this, but it doesn't get all the cool language support.