# 3D assets requirements
# File Format
List of options, plus their requirements:
glTF (recommended choice)
- Version 2.0 (see specification (opens new window) for details)
- Supported extensions
- Texture transforms (
- Unlit materials (
- Texture transforms (
- Separate texture files (not embed)
Blender 2.79b or later
- Materials have to be based on the Principled Shader node
Regardless of the format choice the scene units have to be Meters!
- Correct original size (in meters).
- Manifold meshes.
- Correct and consistent up- and forward-axis.
- Quads and triangles only.
- Keep the pivot/center point in the lower center of the object’s bounding box.
- Keep the root transform at the scene’s origin with no rotation or scaling applied.
- Back-facing polygons are culled (only one side is visible) keep that in mind.
- Objects can contain multiple materials and sub-objects in a hierarchy.
- Sub-objects of the same material should be merged/joined together to save draw calls at runtime.
# Detail variants and complexity limits
# General rule
Complexity/triangle count should be as low as possible, but as high as necessary. Parts which are not relevant and visible in the sales configuration should not be part of the 3D model.
We offer 2 different use cases:
# 1. 3D Viewer, 3D Material Configurator, 3D Product Configurator (Live 3D Rendering)
Purpose: browser-based sales visualization We have the same 3D requirements for all 3 product categories.
# 2. HD Renderings (Offline 3D Rendering)
Purpose: photo-realistic rendered product images for marketing & sales channels.
Automated high-quality product images (CGI) based on the Live 3D Data from Material Configurator or Product Configurator. Alternatively you can also upload and use a higher-quality 3D model for photo-realistic rendering results.
If you provide Configurator and assets for HD Renderings, keep the objects for the different profiles in separate source files.
These are the geometry detail profiles for our 2 use cases:
For 3D Viewer (Level 1), 3D Material Configurator (Level 2), 3D Product Configurator (Level 3) Used in real-time renderings in detail views and more powerful devices. Ideal quality specification for Roomle configurator high-quality product visualization.
For HD Renderings (High-quality offline Renderings) Used in offline (non-real-time) renderings like image previews and product renderings only.
All geometry will be converted to triangles, so triangles are our basis to measure complexity.
We distinguish between a soft and hard limit
Soft triangle count limit: Try to keep your triangle count below the soft limit if possible. You may occasionally have objects of big size and complexity, where keeping this limit and maintaining a good look is not possible. Only in that case you may exceed this limit.
Hard triangle count limit: Every object, no matter how big or complex, must have a triangle count below the hard limit.
The recommended/maximum triangle count depends on the object size and complexity/shape. For normally sized objects (like chairs, tables or couches) these are the limit guides (k means *1000, so 3k = 3000):
Soft Triangle Count Limit
Hard Triangle Count Limit
# UV mapping
- Whenever textures are applied, correct UV layouts have to be provided.
- For configurable objects the UVs must be scaled according to Rubens Configurator specifications
- If the object uses specular shaded materials, normal maps or reflections provide either custom tangents or a UV map to make sure the specular highlights are consistently correct.
UV requirements for the Rubens Configurator:
- In Roomle one UV unit equals to 1 mm on the model. To achieve this, lay out the UVs in a way that a texture map with a size of 1 x 1 mmis mapped onto the object in its correct size.
# UV requirements for the Static models
As no dynamic material changes (potentially using inconsistently scaled texture maps) will occur, such models need to be textured in a way so that the used texture map(s) are scaled correctly.
# Materials & Textures
You may provide textures for the following channels
- diffuse (with or without alpha channel)
- JPEG or PNG Images
- No special characters in (file) names (see Naming convention below)
- Make sure the texture file paths in the 3D file are relative and correct. Otherwise they are not guaranteed to be assigned.
We automatically optimize images for real-time rendering by scaling them down and limit the total number of textures.
|High-quality offline rendering|
|Max. resolution||2048x2048||no limit|
|Max number of textures||12||no limit|
Additional real-time notes:
- Images are scaled so that the pixel size is a power of two (eg. 32, 64, 128, 256, 512 or 1024 Pixel)
- A lossy image compression is applied
Keep the automatic down-scaling in mind when creating UV layouts! UV islands with a narrow distance might introduce bleeding artefacts.
Attention: Please deep dive further into our detailed Roomle texture requirements documentation.
# Naming convention
File names of 3D or texture files, object names, material names, etc. may only consist of alphanumeric characters (digits & letters) found in the ASCII standard supplemented by underscores
_ and dash