MeshParts Why do they exist? For my current game I'm working on I've decided to implement a custom model class to store my models in. Reasons being is that I want to make adding new models as painless as possible for the rest of the team without needing to go through the XNA Monogame content pipeline (Them having VS Dev framework installed just to compile a few models, or passing them onto me to compile every time a change is made would just get tedious further on, not to mention different timezones when testing slowing things down) To this end I've been looking at the model structure of different frameworks, XNA Monogame, SharpDX and AssImp.NET being the main ones. The structure for XNA MG and SharpDX is Model MeshCollection MeshPartCollection, whereas Assimp only has Scene MeshCollection. From previous experience in XNA, MeshParts seem kinda redundant. None of my meshes ever had more than one, and a lot of the XNA examples I've seen only ever had one mesh part per mesh. From everything I've experienced and seen, MeshParts seem redundant, surplus to requirements and just makes for an extra level of complexity (Should I use a loop, or just hardcode it to use the first element in the collection?). Is there some useful aspect of them that I am not aware of, or a particular use case or scenario where they are actually useful?