vpenades.MonoScene/src/MonoScene.Runtime.Content

#### MonoScene.Runtime.Content

This project contains all the classes required to define a 3d model in memory, and eventually, to serialize it (Most probably using ProtoBuffer)

The architecture loosely replicates the architecture of the glTF standard, which is a feature rich model architecture.

Architecture overview:

• ModelCollectionContent
  • Resources
  • MeshCollectionContent
    • MeshContent [n]
    • MeshPartContent [n]
      • MeshGeometryContent
    • VertexBufferContent [n]
    • IndexBufferContent [n]
    • MaterialContent [n]
    • MaterialChannelContent [n]
      • SamplerStateContent
      • Texture
  • ArmatureContent [n]
    • NodeContent [n]
    • Scale Animations
      
    • Rotation Animations
      
    • Translation Animations
      
  • Graph
  • ModelContent [n] <- entry point for a single model
    • DrawableContent [n]
    • RigidDrawableContent - References a rigid mesh in resources
    • SkinnedDrawableContent - References a skinned mesh in resources

Comparing with MonoGame architecture

MonoGame's content classes are designed to be used by the content processor pipeline, which can only be used at build time. This prevents loading public models at runtime.

MonoScene's content classes are designed to be used both for content processing at build time, and also for content loading and procedural creation at runtime.

One important aspect of 3D models architecture is resource sharing; in MonoGame, this is resolved at build time by the content processor pipeline, but since we require to load models at runtime too, we cannot process the models as deeply as an offline pipeline, that means that resource sharing is isolated to the context of a single source model.