Assimp  v3.1.1 (June 2014)
Todo
Member Assimp::Ogre::OgreBinarySerializer::ImportMesh (MemoryStreamReader *reader)
Check what we can actually support.
Member Assimp::Ogre::OgreImporter::CanRead (const std::string &pFile, IOSystem *pIOHandler, bool checkSig) const
Read and validate first header chunk?
Class Assimp::Ogre::OgreImporter

Support vertex colors.

Support poses/animations from the mesh file. Currently only skeleton file animations are supported.

" </dt><dd> \anchor _todo000004 This "set $x y" does not seem to be a official Ogre material system feature. Materials can inherit other materials and override texture units by using the (unique) parent texture unit name in your cloned material. This is not yet supported and below code is probably some hack from the original author of this Ogre importer. Should be removed? Techniques have other attributes than just passes. Support alpha via aiColor4D. Implement
Member Assimp::Ogre::Skeleton::blendMode
Take blend mode into account, but where?
"

Implement nnBinormal, nnColorDiffuse and nnColorSpecular

Remove this stuff once implemented. We only want to log warnings once per element.

Fix above comment with better read logic below

Support quads if Ogre even supports them in XML (I'm not sure but I doubt it)

Implement taking scale into account in matrix/pose calculations!