Model Processing with the XNA Framework Content Pipeline

Model Processing with the XNA Framework Content Pipeline
Describes the model conversion process implemented by XNA Framework Content Pipeline.

The conversion of a game asset in your project is a complex and detailed process comprised of many steps. The detailed description of the general process can be found here. However,it can also be helpful to follow the process from the perspective of a single game asset type—specifically,a model. This discussion focuses on one section (a horizontal cross-section,starting with the top asset group) of the Content DOM graphic,shown here.

Output from the Content Importer

The content pipeline content DOM represents an exported scene (from a modeling package) as a hierarchy of NodeContent objects. This means that a content importer designed to import a 3D scene or model must convert a 3D file into a NodeContent hierarchy containing a parent,a transform,and a collection of children. Some of these nodes will be of type MeshContent,derived from NodeContent. They represent the 3D objects in the scene with a mesh of triangles.

在XNA中,importer将art asset文件转成一个由NodeContent组成的层次结构。其实就是一个有节点组成的层级结构,和Ogre的现实对象组织方式一致。这个节点包括父节点和自己点等信息。

A MeshContent object is composed of a collection of GeometryContent objects. All triangles within a GeometryContent object have the same material applied to them. Their vertices contain the same type of per-vertex data,such as normals and texture coordinates. Since each GeometryContent collection is contained by a single MeshContent object,they share the same world transform.

1.MeshContent由GeometryContent组成。也很好理解,就是网格内容有几何内容组成。

2.所有的几何图形都可以由若干三角形来组成。

3.属于同一个MeshContent的GeometryContent都有同样的world transform。

Each GeometryContent object contains a VertexContent object (storing the values of all per-vertex data channels,and also indices into the shared Positions collection in the parent MeshContent) and an IndexCollection Class,containing indices into the VertexContent object.

The content pipeline content DOM represents a model material by the MaterialContent class. MaterialContent has two derived classes often used by the content pipeline: BasicMaterialContent and EffectContent. Think of BasicMaterialContent as the content pipeline equivalent of BasicEffect. In the same vein,EffectContent is the content pipeline equivalent of Effect.

详细解释了GeometryContent的组成。以后根据需要在学习好了。

可以看出来,通过importer处理之后,一个art asset从文件转换成了一组XNA可以处理的对象,例如,一个model文件会被组织成一组层级结构的NodeContent对象。这组对象将由processor进行处理。

Output from the Model Processor

The scene hierarchy (previously created by the content importer) is the input of the model processor (implemented by ModelProcessor) and is converted into a format usable by your game at run time. Optimization,such as reordering mesh triangles to maximize cache coherency,is also performed at this time. The conversion of content importer output to a run-time type or types,is the main goal of the model processor.

processor的主要目的就是将importer的输出转换成运行时的type。这里面会进行一些优化过程。

The types output by ModelProcessor are close to the final XNA Framework run-time types. For example,the ModelProcessor output type ModelContent corresponds to the XNA Framework run-time type Model Class. This class is similar to the run-time type but stores the model data as simple managed objects,rather than GPU data types. This approach avoids the instantiation of actual GPU objects during the XNA Game Studio Content Pipeline build process.

注意,processor处理后的输出并不似乎GPU可以处理的对象。因为XNA需要支持跨平台的开发,这里面就包括了XBox平台。

This is essential when building graphics for the Xbox 360 platform because instantiation of these types on the Windows GPU during the build process would not be feasible.

如果直接转换成GPU可以读取的对象,那么在XBox上就没法访问他们了。因为XBox没有GPU来读取。

Conversion of the scene hierarchy is broken down as follows:

The entire scene hierarchy,represented by a root NodeContent and its children,is converted to a ModelContent object.

在这个例子中,一个model的加载和处理过程如下:

1.Importer ->NodeContent

2.Processor -> ModelContent

Note
Children of type NodeContent are turned into ModelBoneContent Class objects,and children of type MeshContent are turned into ModelMeshContent objects.

All GeometryContent objects,containing the actual triangles,are converted to ModelMeshPart objects. As mentioned previously,a GeometryContent object contains a VertexContent,IndexCollection,and MaterialContent object. Although the ModelProcessor modifies the data in the IndexCollections,it does not change the type. The VertexContent object,received as input,has two corresponding output types: a VertexBufferContent Class,containing the optimized triangle data,and an array of VertexElement Structure objects,specifying the data contained in the VertexBufferContent Class.

The last step hands off any MaterialContent objects in the scene by chaining to the MaterialProcessor.

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


什么是设计模式一套被反复使用、多数人知晓的、经过分类编目的、代码 设计经验 的总结;使用设计模式是为了 可重用 代码、让代码 更容易 被他人理解、保证代码 可靠性;设计模式使代码编制  真正工程化;设计模式使软件工程的 基石脉络, 如同大厦的结构一样;并不直接用来完成代码的编写,而是 描述 在各种不同情况下,要怎么解决问题的一种方案;能使不稳定依赖于相对稳定、具体依赖于相对抽象,避免引
单一职责原则定义(Single Responsibility Principle,SRP)一个对象应该只包含 单一的职责,并且该职责被完整地封装在一个类中。Every  Object should have  a single responsibility, and that responsibility should be entirely encapsulated by t
动态代理和CGLib代理分不清吗,看看这篇文章,写的非常好,强烈推荐。原文截图*************************************************************************************************************************原文文本************
适配器模式将一个类的接口转换成客户期望的另一个接口,使得原本接口不兼容的类可以相互合作。
策略模式定义了一系列算法族,并封装在类中,它们之间可以互相替换,此模式让算法的变化独立于使用算法的客户。
设计模式讲的是如何编写可扩展、可维护、可读的高质量代码,它是针对软件开发中经常遇到的一些设计问题,总结出来的一套通用的解决方案。
模板方法模式在一个方法中定义一个算法的骨架,而将一些步骤延迟到子类中,使得子类可以在不改变算法结构的情况下,重新定义算法中的某些步骤。
迭代器模式提供了一种方法,用于遍历集合对象中的元素,而又不暴露其内部的细节。
外观模式又叫门面模式,它提供了一个统一的(高层)接口,用来访问子系统中的一群接口,使得子系统更容易使用。
单例模式(Singleton Design Pattern)保证一个类只能有一个实例,并提供一个全局访问点。
组合模式可以将对象组合成树形结构来表示“整体-部分”的层次结构,使得客户可以用一致的方式处理个别对象和对象组合。
装饰者模式能够更灵活的,动态的给对象添加其它功能,而不需要修改任何现有的底层代码。
观察者模式(Observer Design Pattern)定义了对象之间的一对多依赖,当对象状态改变的时候,所有依赖者都会自动收到通知。
代理模式为对象提供一个代理,来控制对该对象的访问。代理模式在不改变原始类代码的情况下,通过引入代理类来给原始类附加功能。
工厂模式(Factory Design Pattern)可细分为三种,分别是简单工厂,工厂方法和抽象工厂,它们都是为了更好的创建对象。
状态模式允许对象在内部状态改变时,改变它的行为,对象看起来好像改变了它的类。
命令模式将请求封装为对象,能够支持请求的排队执行、记录日志、撤销等功能。
备忘录模式(Memento Pattern)保存一个对象的某个状态,以便在适当的时候恢复对象。备忘录模式属于行为型模式。 基本介绍 **意图:**在不破坏封装性的前提下,捕获一个对象的内部状态,并在该
顾名思义,责任链模式(Chain of Responsibility Pattern)为请求创建了一个接收者对象的链。这种模式给予请求的类型,对请求的发送者和接收者进行解耦。这种类型的设计模式属于行为
享元模式(Flyweight Pattern)(轻量级)(共享元素)主要用于减少创建对象的数量,以减少内存占用和提高性能。这种类型的设计模式属于结构型模式,它提供了减少对象数量从而改善应用所需的对象结