X
MinhNguyen (Talk | contribs) |
MinhNguyen (Talk | contribs) |
||
| Line 18: | Line 18: | ||
* '''Syntax Format(s):''' -Binary Encoding, Text Encoding, Templates | * '''Syntax Format(s):''' -Binary Encoding, Text Encoding, Templates | ||
| − | * '''Family Format(s):''' | + | * '''Family Format(s):''' - .x |
| − | '''Description:''' | + | '''Description:''' - X files provide a template-driven format that enables the storage of meshes, textures, animations, and user-definable objects. Support for animation sets enables you to store predefined paths for playback in real time. Instancing and hierarchies are also supported. Instancing enables multiple references to an object, such as a mesh, while storing its data only once per file. Hierarchies are used to express relationships between data records. |
| − | '''History:''' | + | '''History:''' - In 1992, Servan Keondjian started a company named RenderMorphics, which developed a 3D graphics API named Reality Lab, which was used in medical imaging and CAD software. Two versions of this API were released. Microsoft bought RenderMorphics in February 1995, bringing Keondjian on board to implement a 3D graphics engine for Windows 95. This resulted in the first version of Direct3D that shipped in DirectX 2.0 and DirectX 3.0. |
'''Example(s):''' [[Example::Example Template]] | '''Example(s):''' [[Example::Example Template]] | ||
| Line 38: | Line 38: | ||
pDevice->DrawPrimitive( D3DPT_TRIANGLELIST, D3DFVF_LVERTEX, v, 3, 0 ); | pDevice->DrawPrimitive( D3DPT_TRIANGLELIST, D3DFVF_LVERTEX, v, 3, 0 ); | ||
| − | '''Identifier:''' | + | '''Identifier:''' http://software.intel.com/en-us/articles/ocean-fog-using-direct3d-10/ |
| − | '''Documentation:''' | + | '''Documentation:''' http://www.gamedev.net/reference/programming/features/d3do/page6.asp |
| − | '''File Extensions:''' | + | '''File Extensions:''' - .x |
'''Applications:''' - Windows versions such as vista, 98,... | '''Applications:''' - Windows versions such as vista, 98,... | ||
| Line 51: | Line 51: | ||
'''Magic numbers:''' [[Magic Numbers::]] - Unique identifying characters at the beginning of files for this engineering format. | '''Magic numbers:''' [[Magic Numbers::]] - Unique identifying characters at the beginning of files for this engineering format. | ||
| − | '''Format(s):''' [[Format::]] - | + | '''Format(s):''' [[Format::]] - .x |
| − | '''Rights:''' | + | '''Rights:''' Proprietary License |
'''Sustainability Factors:''' - Facts about the sustainability of this particular engineering format. | '''Sustainability Factors:''' - Facts about the sustainability of this particular engineering format. | ||
| − | * '''Standardization:''' | + | * '''Standardization:''' Used widely in game developing |
| − | * '''Adoption:''' | + | * '''Adoption:''' None |
| − | ** '''Licensing and patent claims:''' | + | ** '''Licensing and patent claims:''' None |
| − | * '''Self-documentation:''' | + | * '''Self-documentation:''' None |
| − | * '''External dependencies:''' | + | * '''External dependencies:''' None |
| − | + | * '''Technical protection considerations:''' None | |
| − | * '''Technical protection considerations:''' | + | '''Typical use:''' CAD, Modeling, Rendering, Texturing, Animation |
| − | + | ||
| − | '''Typical use:''' | + | |
'''File classification:''' - Specific properties that pertain to this engineering format. | '''File classification:''' - Specific properties that pertain to this engineering format. | ||
| − | * '''Type {Binary, Text}:''' | + | * '''Type {Binary, Text}:''' Binary |
* '''Raster data:''' - Section describes whether or not the engineering format supports raster data. | * '''Raster data:''' - Section describes whether or not the engineering format supports raster data. | ||
| − | ** '''Raster data 2D:''' | + | ** '''Raster data 2D:''' |
| − | *** '''Is Supported:''' | + | *** '''Is Supported:''' - Yes |
| − | *** '''Description:''' | + | *** '''Description:''' It support raster base on its rules. Rasterization rules define how vector data is mapped into raster data. |
| − | ** '''Raster data 3D:''' | + | ** '''Raster data 3D:''' |
| − | *** '''Is Supported:''' | + | *** '''Is Supported:''' Yes |
| − | *** '''Description:''' | + | *** '''Description:''' It support raster base on its rules. Rasterization rules define how vector data is mapped into raster data. |
| − | * '''Geometric representation:''' | + | * '''Geometric representation:''' |
| − | ** '''Implicit representation:''' | + | ** '''Implicit representation:''' |
| − | *** '''Implicit surfaces:''' | + | *** '''Implicit surfaces:''' |
| − | **** '''Is Supported:''' | + | **** '''Is Supported:''' Yes |
| − | **** '''Description:''' | + | **** '''Description:''' |
*** '''Implicit curves:''' - Can the format support implicit curves? Example: A format that can contain curves that are generated with mathematical equations that contain the independent variables x, y, and z, supports implicit curves. | *** '''Implicit curves:''' - Can the format support implicit curves? Example: A format that can contain curves that are generated with mathematical equations that contain the independent variables x, y, and z, supports implicit curves. | ||
**** '''Is Supported:''' [[File Classification Implict Curves - Is Supported::]] - Is the feature supported in the engineering format? | **** '''Is Supported:''' [[File Classification Implict Curves - Is Supported::]] - Is the feature supported in the engineering format? | ||
Revision as of 11:25, 22 May 2009
Title(s): -Direct3D model with .x files
Version ID: - Version 11
Date released: - July 2008
Date: - September 1995
Creator(s): Servan Keondjian
Contributor(s): - Microsoft, RenderMorphics Relationships: - In February 1995, Microsoft bought RenderMorphics and brought its CEO Keondjian on board to implement a 3D graphics engine for Windows 95. This resulted in the first version of Direct3D.
- Previous Version(s): - Reality Lab
- Contains: - .X files
- Syntax Format(s): -Binary Encoding, Text Encoding, Templates
- Family Format(s): - .x
Description: - X files provide a template-driven format that enables the storage of meshes, textures, animations, and user-definable objects. Support for animation sets enables you to store predefined paths for playback in real time. Instancing and hierarchies are also supported. Instancing enables multiple references to an object, such as a mesh, while storing its data only once per file. Hierarchies are used to express relationships between data records.
History: - In 1992, Servan Keondjian started a company named RenderMorphics, which developed a 3D graphics API named Reality Lab, which was used in medical imaging and CAD software. Two versions of this API were released. Microsoft bought RenderMorphics in February 1995, bringing Keondjian on board to implement a 3D graphics engine for Windows 95. This resulted in the first version of Direct3D that shipped in DirectX 2.0 and DirectX 3.0.
Example(s): Example Template
Drawing a triangle in Direct3D:
// A 3-vertex polygon definition D3DLVERTEX v[3]; // Vertex established v[0]=D3DLVERTEX( D3DVECTOR(0.f, 5.f, 10.f), 0x00FF0000, 0, 0, 0 ); // Vertex established v[1]=D3DLVERTEX( D3DVECTOR(0.f, 5.f, 10.f), 0x0000FF00, 0, 0, 0 ); // Vertex established v[2]=D3DLVERTEX( D3DVECTOR(0.f, 5.f, 10.f), 0x000000FF, 0, 0, 0 ); // Function call to draw the triangle pDevice->DrawPrimitive( D3DPT_TRIANGLELIST, D3DFVF_LVERTEX, v, 3, 0 );
Identifier: http://software.intel.com/en-us/articles/ocean-fog-using-direct3d-10/
Documentation: http://www.gamedev.net/reference/programming/features/d3do/page6.asp
File Extensions: - .x
Applications: - Windows versions such as vista, 98,...
- Native application(s): Engineering Format Application Template - Graphic games
- Interoperable applications: Engineering Format Application Template - Applications which can read or write files of this format, but are not native applications for the format.
Magic numbers: - Unique identifying characters at the beginning of files for this engineering format.
Format(s): - .x
Rights: Proprietary License
Sustainability Factors: - Facts about the sustainability of this particular engineering format.
- Standardization: Used widely in game developing
- Adoption: None
- Licensing and patent claims: None
- Self-documentation: None
- External dependencies: None
- Technical protection considerations: None
Typical use: CAD, Modeling, Rendering, Texturing, Animation
File classification: - Specific properties that pertain to this engineering format.
- Type {Binary, Text}: Binary
- Raster data: - Section describes whether or not the engineering format supports raster data.
- Raster data 2D:
- Is Supported: - Yes
- Description: It support raster base on its rules. Rasterization rules define how vector data is mapped into raster data.
- Raster data 3D:
- Is Supported: Yes
- Description: It support raster base on its rules. Rasterization rules define how vector data is mapped into raster data.
- Raster data 2D:
- Geometric representation:
- Implicit representation:
- Implicit surfaces:
- Is Supported: Yes
- Description:
- Implicit curves: - Can the format support implicit curves? Example: A format that can contain curves that are generated with mathematical equations that contain the independent variables x, y, and z, supports implicit curves.
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Point set: - Can the format support point sets? Example: A format that supports surfaces and lines that are generated by points that form triangles supports point sets.
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Implicit surfaces:
- Mesh: - Section describes whether or not the engineering format supports mesh.
- Manifold surface meshes: - Can the format support manifold surface meshes? Example: A format that supports surfaces that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Manifold volume meshes: - Can the format support manifold volume meshes? Example: A format that supports volumes that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Non-manifold meshes: - Can the format support non-manifold meshes? Example: A format that supports meshes that are not manifolds
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Manifold surface meshes: - Can the format support manifold surface meshes? Example: A format that supports surfaces that are mathematical spaces in which every point has a neighborhood which resembles Euclidean space
- Parametric representation: - Section describes whether or not the engineering format supports parametric representations.
- Parametric surfaces: - Can the format support parametric surfaces? Example: A format that can contain surfaces that are generated with parametric equations supports parametric surfaces.
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Parametric curves: - Can the format support parametric curves? Example: A format that can contain curves that are generated with parametric equations supports parametric curves.
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Parametric surfaces: - Can the format support parametric surfaces? Example: A format that can contain surfaces that are generated with parametric equations supports parametric surfaces.
- Contour sets: - Can the format support contour sets?
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- NURBS: - Can the format support Non Uniform Rational Basis Splines? Examples: The engineering formats IGES, STEP, ACIS, and PHIGS
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Implicit representation:
- Multi-resolution models: - Can the format support models with multiple resolutions? Examples: A format that supports a highly detailed and lowly detailed model simultaneously supports multi-resolution models.
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Dynamics: - Section describes whether or not the engineering format supports dynamics.
- Kinematics: - Can the format support kinematics? Example: Does the format allow model parts to rotate?
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Assembly: - Can the format support assembly? Example: Does the format allow the assembly instructions to be explicitly specified with a model?
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Force(s): - Can the format support forces? Example: Does the format support acceleration forces?
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Kinematics: - Can the format support kinematics? Example: Does the format allow model parts to rotate?
- Boundary representation - Can the format support models with boundary representations?
- Manifold surface boundary representations: - Can the format support manifold surface boundary representations? Example: The engineering format STEP
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Manifold volume boundary representations: - Can the format support manifold volume boundary representations? Example: The engineering format STEP
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Non-manifold boundary representations: - Can the format support non-manifold boundary representations? Example: The engineering format STEP
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
- Manifold surface boundary representations: - Can the format support manifold surface boundary representations? Example: The engineering format STEP
- Material transparency: - Can the format support transparency? Example: Does the format allow models to have a clear window in a car?
- Is Supported: - Is the feature supported in the engineering format?
- Description: - This field is used to describe the support or lack of support of the feature.
References: - A list of references regarding any aspects of this engineering format; any reading material supplemental to this page.