LXO
From GICLWiki
Title(s): - .LXO, Luxology Modo file
Version ID: - 302
Date released: - 2008-04-03
Date: - Date the format was created (YYYY-MM-DD)
Creator(s): Entity Template - Luxology (R) LLC
Contributor(s): - Luxology (R) LLC
Relationships: - Luxology (R) LLC
- Previous Version(s): - Any engineering format that is a previous version format of this one.
- Contains: - N/A
- Syntax Format(s): - N/A
- Family Format(s): - N/A
Description: - lxo model file for Luxology Modo software.
History: - Historical description depicting major events surrounding development, creation, and maintenance of this format.
Example(s): Example Template - Information and example models of the engineering format.
Identifier: - http://www.luxology.com/whatismodo/techspecs.aspx
Documentation: Documentation Template - N/A
File Extensions: - lxo
Applications: - Luxology Modo
- Native application(s): Engineering Format Application Template - Luxology Modo
- Interoperable applications: Engineering Format Application Template - N/A
Magic numbers: - N/A
Format(s): - N/A
Rights: - Proprietary license
Sustainability Factors: - Facts about the sustainability of this particular engineering format.
- Standardization: - Information regarding standardization attempts with this format.
- Adoption: - Information about how this format has been adopted by other organizations.
- Licensing and patent claims: - Any licenses or patent claims that the engineering format makes.
- Self-documentation: - Any self-documentation capabilities of the format.
- External dependencies: - Anything that the format depends on outside of its control to function.
- Technical protection considerations: - Any considerations that are necessary when it comes to technical protection.
Typical use: - VFX, Print CGI, CAD, Game Development
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: - Can the format support 2D raster data? Example: A format that can contain 2D pixelated data supports 2D raster data.
- Is Supported: - Yes
- Description: - This field is used to describe the support or lack of support of the feature.
- Raster data 3D: - Can the format support 3D raster data? Example: A format that can contain 2D pixelated data of a 3D model supports 3D raster data.
- Is Supported: - Yes
- Description: - This field is used to describe the support or lack of support of the feature.
- Geometric representation: - Section describes whether or not the engineering format supports geometric representations.
- Implicit representation: - Section describes whether or not the engineering format supports implicit representations.
- Implicit surfaces: - Can the format support implicit surfaces? Example: A format that can contain surfaces that are generated with mathematical equations that contain the independent variables x, y, and z, like x^2 + y^2 + z^2 * R^2 = 0, supports implicit surfaces.
- Is Supported: - Yes
- Description: - This field is used to describe the support or lack of support of the feature.
- 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: - Yes
- 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: - Yes
- Description: - This field is used to describe the support or lack of support of the feature.
- 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: - Yes
- 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: - Yes
- 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: - Yes
- Description: - This field is used to describe the support or lack of support of the feature.
- 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: - Yes
- 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: - Yes
- Description: - This field is used to describe the support or lack of support of the feature.
- Contour sets: - Can the format support contour sets?
- Is Supported: - Yes
- 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: - Yes
- Description: - This field is used to describe the support or lack of support of the feature.
- 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: - Yes
- 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: - Yes
- Description: - Supports animation.
- Assembly: - Can the format support assembly? Example: Does the format allow the assembly instructions to be explicitly specified with a model?
- Is Supported: - No
- 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: - Yes
- Description: - Supported for animation purposes
- 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: - Yes
- 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: - Yes
- 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: - Yes
- Description: - This field is used to describe the support or lack of support of the feature.
- Material transparency: - Can the format support transparency? Example: Does the format allow models to have a clear window in a car?
- Is Supported: - Yes
- Description: - This field is used to describe the support or lack of support of the feature.
References: -
http://www.luxology.com/whatismodo/techspecs.aspx http://www.luxology.com/whatismodo/markets.aspx
