<p dir="auto">I saw the relevant PR, and verified some of the performance improvements, but it has not been merged into this. Can the official support VAO? Or when will it be ready to support VAO?</p>
<p dir="auto">What is the current position of THREE.renderer concerning the usage of VAO's?</p>
<p dir="auto"><a href="https://www.khronos.org/registry/webgl/extensions/OES_vertex_array_object" rel="nofollow">OES_vertex_array_object</a> extension is supported on majority of devices and is going to be in core of WebGL 2.0 (According to <a href="http://webglstats.com" rel="nofollow">WebGL Stats</a> and <a href="https://www.khronos.org/registry/webgl/specs/latest/2.0/#3.6" rel="nofollow">WebGL 2.0 Spec</a>).</p>
<p dir="auto">I've found <a href="https://github.com/mrdoob/three.js/pull/5849" data-hovercard-type="pull_request" data-hovercard-url="/mrdoob/three.js/pull/5849/hovercard">#5849 issue</a> on that topic, but it seems to have no continuation.</p>
<p dir="auto">Could it be something like mentioned in that issue emulation level? (renderer acts like VAO is always available and interacting with it through THREE.VertexArrayObjectSomething which handles cases). Or should it be done by a separate renderer somehow? Or if the case is THREE doesn't need it, why it is so?</p>
<p dir="auto">Thanks in advance.</p>