Asset Preparation
When working with Web3D, it is of utmost importance to be mindful of the optimal size range of the modeled end-result, as highly detailed designs can greatly hinder the real-time performance.
Threedium Platform is built to support Web3D in big capacities, and in the majority of known formats, but some guidelines need to be established. Even then, the Platform packs numerous optimization options to help the users streamline their workflow and adjust accordingly.
Software
It is important to note that all formative design work is performed locally, in a user's preferred software. The Platform offers numerous editing and post-production tools and features,but not core modeling options. With this in hand, updating an already uploaded model with new changes is made easy with the “Update” feature.
There are numerous pieces of software that are compatible with the Platform. The most common one is Blender, but 3ds Max, Maya, Substance Painter are all a part of a staple workflow.
File Formats
Threedium Platform supports file formats that are based on polygonal geometric data such as:
- GL Transmission Format (.glTF and .glb)
- FBX files (.fbx)
- OBJ files (.obj)
And USD/USDZ (Universal Scene Descriptor) files for Augmented Reality apps and features on Apple Devices.
It is also worth noting that the Platform’s Optimizer isn’t always fond of the .fbx format when it packs more than just Modeling data. For purposes of Optimizer, conversion to .glb file type is always the safe route.
Polycount and Size
The recommended number of Meshes in the scene is up to 30, but the User experience has proven that the number of possible model parts in a Single Workspace exceeds that greatly.
Recommended Polygon number is up to 80 000 polygons, but workspaces with up to 200 000 polygons have been found to perform nicely, if all other criteria are met.
It is greatly recommended to model all assets in their real-life size, as those can later be faithfully translated to Augmented Reality. The default unit of the Platform is centimeters (cm).
Textures and UV
Optimal Texture size is 1K and below (1024x1024 px), but 2K Textures (2048x2048 px) can also perform nicely in most scenarios. To preserve the texture-obtained level of details, the Threedium Platform offers integrated KTX compression, a lightweight container whose encoding ensures efficient texture transmission.
Ambient Occlusion Textures can be optimized into a single Global Ambient Occlusion map that is by practise baked on a second UV channel, also supported by the Platform.
UV unwrap is performed on a first UV channel, and is a requirement for Models that want to make use of certain PBR features and Overlays.
Parenting and Nodes
When establishing a Scene hierarchy all meshes should be parented to an Empty node, single or multiple, depending on what Action requirements a model needs to fulfill, if there are any.
It is strongly advised not to parent meshes to other meshes, as this can create unexpected outcomes in the production process. The reparenting can only be done on a native software, and by that extension, this can pose a predicament.
Transforms and Size
Lastly, before uploading the workspace, it is important to have all the Transform parameters (Location, Rotation, Scale) applied, for the same reason one would want them applied in their native software anyways.
Threedium Platform is capable of processing models that do not adhere to the outlined suggestions — such as those with extensive polygon counts, larger textures, or oversized files — however, we encourage users to respect these guidelines. Ignoring the recommended asset preparation practices may result in suboptimal performance and a compromised user experience across your 3D workspaces. It is essential to balance quality and complexity to achieve the best results for end-users.
Learn More
While desktop systems typically have more powerful hardware and can handle larger files and more complex models with relative ease, the mobile experience is a different scenario altogether. Users often interact with web content through their smartphones, which have less processing power and graphical capabilities. As a result, heavy or unoptimized 3D assets can lead to significant performance issues on these devices, such as slow loading times, stuttering interactions, and even application crashes.
Therefore, it's crucial to optimize your 3D workspaces, not just for the sake of desktop users, but especially for those on mobile devices. By following the recommended asset guidelines—keeping file sizes small, polygon counts low, and textures appropriately scaled—you ensure that your content is accessible and runs smoothly on the wide range of devices that users might employ to engage with your 3D content. This approach guarantees a more consistent and positive experience for all users, regardless of their device's capabilities.