This article is dedicated to 3D artists and designers who would like to create and customise a 3D Room optimised for Wonda VR Spaces in third party programs like Blender or Unity.

(For a general overview of the process of importing a room in Wonda VR Spaces, please read this article)

About Rendering and glTF format

Wonda VR Spaces is relying on three.js which is a JavaScript library and application programming interface (API) used to create and display animated 3D computer graphics in a web browser using WebGL.

We mostly support glTF that allow storing 3D scenes and models using the JSON standard.

General Recommendation

  • Max Poly count: 50k (decimate the model if needed. See how to do with Blender)

  • Max different Texture count: 25

  • Max Texture Resolution: 4K. For a better global Room resolution, split the Room mesh in multiple parts, each of them can have one distinct material with one 4K texture.

  • Material number: Each exported material will create a draw call in the runtime renderer. We want to reduce the number of material as much as possible

Material in glTF

glTF shader in Wonda VR Spaces

The core material system in glTF supports a metal/rough PBR workflow with the following channels of information:

  • Base Color

  • Metallic

  • Roughness

  • Baked Ambient Occlusion

  • Normal Map

  • Emissive

Lightmaps and ambient occlusion require a second set of UVs (uv1) to be correctly interpreted by three.js.

Rendering Recommendations

  • To have the best rendering quality in Wonda VR Spaces, materials should be defined with KHR_materials_unlit extension which ensures the best performance and quality (lots of map supports)

  • If baking lightmap/ambient occlusion map is in a different map than the diffuse, you need to make them use a second set of UVs (a different than the diffuse)

Useful information about gltf/glb in Blender documentation:

Did this answer your question?