Is there an XML specification for .mesh.xml v2 meshes?

[mrmclovin]

Is there an XML specification for .mesh.xml v2 meshes describing the expected structure and constraints? (apart from Tools/MeshTool/src/main.cpp and Tools/MeshTool/src/XML/OgreXMLMeshSerializer.cpp)

[dark_sylinc]

Nope. That's it.

The .mesh.xml hasn't really changed much between v1 and v2. In fact I don't remember them changing it at all.

The binary format changed between v1 and v2 to make directly loading disk to VRAM straightforward, to better account how vertex buffers are (not) shared across submeshes, the fact that v2 does not allow gaps between vertex elements, and to account for the new compressed vertex formats.

XML doesn't care about any of that, and shared geometry can be unshared by the loader. Any misc thing or special processing can be handled by the loader.
Restrictions should be obvious, off the top of my head: a 16-bit index buffer cannot contain values >65535, index buffer values must be in range [0; vertex_count)

[mrmclovin]

Nope. That's it.

The .mesh.xml hasn't really changed much between v1 and v2. In fact I don't remember them changing it at all.

The binary format changed between v1 and v2 to make directly loading disk to VRAM straightforward, to better account how vertex buffers are (not) shared across submeshes, the fact that v2 does not allow gaps between vertex elements, and to account for the new compressed vertex formats.

XML doesn't care about any of that, and shared geometry can be unshared by the loader. Any misc thing or special processing can be handled by the loader.
Restrictions should be obvious, off the top of my head: a 16-bit index buffer cannot contain values >65535, index buffer values must be in range [0; vertex_count)

Ok, so the <sharedvertices> in XML has no purpose in v2 meshes?

[dark_sylinc]

The loader (OgreMeshTool) will unshare them if the binary output is set to v2.