Pixyco-XYZ/openmesh
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

- add info about requesting standard properties and loading a mesh with options - refs #2512

Browse Source 
- add info about texture information in OBJ file format - closes #2369

git-svn-id: http://www.openmesh.org/svnrepo/OpenMesh/trunk@1306 fdac6126-5c0c-442c-9429-916003d36597
This commit is contained in:
Matthias Möller
2015-07-08 08:54:31 +00:00
parent fbda5f8687
commit bd895da3fc
1 changed files with 18 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
Doc/tutorial_08.docu
View File

@@ -22,12 +22,28 @@ distinguish between
- Options::VertexColor - Options::VertexColor
- Options::FaceNormal - Options::FaceNormal
- Options::FaceColor - Options::FaceColor
- Options::FaceTexCoord
- Options::ColorAlpha - Options::ColorAlpha
- Options::ColorFloat - Options::ColorFloat
- Options::Custom - Options::Custom
These bits have different effects when reading or writing. The file These bits have different effects when reading or writing. The file
format itself is selected by the extension of the filename. format itself is selected by the extension of the filename.
Please take into account, each mesh has to <b>request</b> the standard property <b>before loading</b> with the corresponding option.
For instance, if you enable Options::VertexNormal, your mesh has to request vertex normals. Otherwise, they will not be written into the mesh.
\note Face Tex Coords will not be saved as a property per face, but as a property per halfedge. Therefore, you have to request the "halfedge_texcoords2D" property
The OBJ-reader can also read information about the textures in the *.mtl file, if available.
These texture information (includes texturename and index) will be saved in the property of type:
\code OpenMesh::MPropHandleT< std::map< int, std::string > > \endcode
with the name:
\code "TextureMapping" \endcode
If you want to use the texture information, you have to request this custom property in your mesh
before loading it with the obj reader. There is no other option you have to define for reading texture information beside of the request of the property.
Below in the table you can see what options are suported by which reader/writer (it is possible that the data format can support more). Below in the table you can see what options are suported by which reader/writer (it is possible that the data format can support more).
ASCII is not a real option and will be selected, if binary was not defined. ASCII is not a real option and will be selected, if binary was not defined.
@@ -47,7 +63,7 @@ ASCII is not a real option and will be selected, if binary was not defined.
\li defined with vc (e.g. used by meshlab) \li defined with vc (e.g. used by meshlab)
\li colors encoded in a vertex line (v followed by 6 values) \li colors encoded in a vertex line (v followed by 6 values)
\**) only ascii version and only vertex and face properties with fundamental types \**) only ascii version and only vertex and face properties with fundamental types. Take into account, that you don't have to request these custom properties before loading.
\***) no reader exists \***) no reader exists