Textured mesh

RIM-Nat enables the integration of 3D meshes into scenes, with optional texturing using images applied to their surfaces. This functionality is particularly suitable for scenes generated by photogrammetry, where realistic rendering is essential.

Supported Formats for Meshes

OBJ Format with Texture (OBJ + MTL + PNG/JPG)

The OBJ format is commonly used to represent 3D objects. It supports texturing through an associated MTL material file and a PNG or JPG image. To ensure proper import and optimal rendering quality, files must meet the following requirements:

• File Structure:

  • An OBJ file for the mesh geometry.
  • An MTL file to define materials and texture links.
  • A single texture file, either in PNG or JPG format.

• File Constraints:

  • All files must be compressed into a ZIP file for import.
  • No password protection should be applied to the ZIP file.
  • File Naming: The OBJ file name should not contain spaces or special characters.
  • Link Preservation: Retain the original names for the MTL and texture files (JPG/PNG) as generated by the production software to avoid breaking links between geometry and texture.

PLY Format (Polygon File Format)

The PLY format is another supported format for meshes in RIM-Nat, although it does not support textures. It is often used for mesh data where a single color per face is sufficient, such as data from 3D scans, CAD models, or numerical simulations.

• File Structure:

  • Files must be in binary format for compatibility with RIM-Nat.
  • If needed, use the free software CloudCompare to convert PLY files to binary format.

• File Constraints:

  • The PLY file can be uploaded alone or compressed into a ZIP file (no password protection).
  • File Naming: As with OBJ files, avoid spaces and special characters in the file name.
  • Size Limitation: The maximum file size is determined by the user’s subscription level.

For further assistance, please contact RIM-Nat technical support.