You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We introduced SegmentVector class to be able to render layers with >2^16 vertices — by maintaining multiple views ("segments") in the vertex array with different offsets. However, according to WebGL best practices, OES_element_index_uint extension that allows 32-bit vertex indexing as opposed to 16-bit one is universally supported and can be relied upon. We could use it to remove the segments abstraction, using the extension to render >2^16 vertices with a single draw draw call, and removing the complexity around splitting and maintaining segments.
The text was updated successfully, but these errors were encountered:
We introduced
SegmentVector
class to be able to render layers with >2^16 vertices — by maintaining multiple views ("segments") in the vertex array with different offsets. However, according to WebGL best practices,OES_element_index_uint
extension that allows 32-bit vertex indexing as opposed to 16-bit one is universally supported and can be relied upon. We could use it to remove the segments abstraction, using the extension to render >2^16 vertices with a single draw draw call, and removing the complexity around splitting and maintaining segments.The text was updated successfully, but these errors were encountered: