Anyone know why there are over 4 times as many vertex in CompactSubGeometry.vertexData compared to SubGeometry.vertexData?

and why the length isn’t divisible by 3 (x,y,z)

eg: Creating a sphere 30, 30 segments has 2883 vertex numbers with SubGeometry.vertexData: 31*31*3 = 2883

but for some reason using the new CompactSubGeometry returns 12493 vertex numbers…

CompactSubGeometry puts all data (vertex, normals, tangents, UVs) into one vector/buffer.  It’s a performance optimization.

You can take a look at vertexOffset, vertexStride, vertexNormalOffset, etc. to figure out how to get at the data you need from vertexData from an ISubGeometry.

Arr sweet, thanks for explaining… I figured it’d be doing something like that after reading the Away3D 4.1 Alpha release post, but just wasn’t 100% sure what it was doing.

So will this improve performance if I’m only updating the vertex positions? wont it mean I’m uploading data that isn’t changing? (normals, tangents, UVs)

I think that changing any of the interleaved data sets and not the others ( for example, changing vertex positions but not vertex uv’s ) has the same effect as changing all the data in a compact sub geometry. This could be less performing than using non compact sub geometries and altering only the buffer that deals with positions. I think there is an option in geometry to use separate buffers.

yes use
_plane.geometry.convertToSeparateBuffers();