3D Modeler Documentation

Establishing the terminology that will be used to explain the platform's requirements.

Geometry/polygon mesh is a collection of vertices, edges and faces that make up the shape of 3D object. This can be a bottle, cream, furniture, jewellery, car, etc.

Vertices: Plural noun for the vertex. These are the points that make up the surface of a 3D object.

Edges: Edge is what you get when you connect 2 vertices with a straight line.

Polygon: 4 vertices connected to each other by 4 edges then become a polygon. This is sometimes also referred as a face. We strongly advice our users to create quads (a 4 sided polygons) when modelling instead of triangles (3 sided polygons) or ngons (5 or more side polygons).

Element/Object/Mesh: Number of polygons joined and closed together from the element. This is sometimes also referred as an object.

*Depending on the needs and complexity of your 3D model we recommend following our rule for Maximum number of polygons.

If you are just starting with modelling a 3D model that will end up on Unlimited3D, we strongly advise you to read our modelling guidelines to prepare your model for most optimal use of our software.

Real-world scale modelling

We strongly recommend modeling the object in it’s realistic measures.

Isolated vertices

During modelling, it is possible to create a vertex that is not part of any face. It is necessary to remove all of these vertices.

Coincident vertices

Remove/Weld separate vertices that occupy the same location.

Overlapping faces

When two or more faces or polygons occupy the same space, rendering can be invalid due to Z-fighting. You should check for and remove all overlapping faces.

Face orientation

Front of a polygon’s face is graphically represented using a directional vector that is perpendicular to the face. Make sure that face normals point outward.

Model position

Center model at scene origin x/y/z - 0/0/0

Pivot point

Each mesh/object or transformation node can have only one pivot point. The model can be scaled or rotated around this point. We suggest a center pivot point to each respective object.

Transforms reset

Resets the transform values. The object's rotation values will be set to 0, and the scale to 1. This is necessary if you were scaling, rotating or mirroring the whole object during your workflow.

Vertex Normals

Vertex normals determine the visual softness/hardness between polygons. They are determining how the model should shade under the light. Custom vertex normals are supported.

Instances

The usage of instances is encouraged wherever possible.

Naming

Assign unique names for meshes, groups and materials. If the names are not unique, they will be automatically generated. This can cause a discontinuity to model update. Avoid special characters when naming.

Textures

Textures are 2D images mapped to the model surface. Textures work in conjunction with Shaders and Materials to produce the final rendering. You can upload/delete multiple assets in inventory or add them during the work. For optimal results while using Unlimited3D see recommended maximum textures sizes.

Image formats

At the moment supported formats are .jpg, .png and .hdr.

Channels

For AO map, Global AO map and Lightmap you need to unwrap UV channel 2. All other maps are assigned to channel 1.

Channel Packing

You may combine b/w images RMA (Roughness + Metallic + Ambient occlusion) to the RGBA channels in PBR workflow. Alpha channel is optional.

Resolution

Texture resolution should use the “power of two” rule. In short, the power of two is a set of simple criteria ensuring 2D image assets conform to regulated sizes and dimensions, which typically manifest as; 1) width/height being divisible by "8", and/or 2) width/height that can be doubled-up or divided-down by "2". In other words any image that is "8", "16", "32", "64", "128", "256", "512", "1024", "2048" will work good.

Aspect

Recommended aspect is 1:1 or 1:2.

Optimizing UV

Make unwrapping more compact in order to effectively use texture space. That way you will be able to use smaller resolution maps. Keep a low number of UV shells. Hide UV seams.

Multi maps

If you need more resolution you can use multiple texture sets.

Clean UV

Remove all unused UV channels.

Materials

While using the Unlimited3D platform you should be aware of few rules regarding materials:

1. We support multiple materials and shaders.
2. You can mix different shaders in the same scene.
3. For best performances (fewer draw calls), join all meshes/elements with the same material if it’s possible.
4. Multi materials are counted as separate meshes.
5. It is always more optimal to have less different materials in the scene.
6. Keep in mind that as you add more materials it becomes heavier in terms of processing. Opaque materials are faster, transparent materials are slower.

Transparency

Turn on transparency and lower opacity slider to set the effect. You can also use map in alpha map or use the alpha channel from the diffuse map. For transparent objects, you have blending modes available.

Alpha Blending

You can use blend modes from the Blending dropdown list inside the shader.

Alpha Clipping

You can adjust Alpha Test slider which is located in shaders advanced options.

PBR - Physically Based Rendering

To create PBR (Physically Based Rendering) scene, use MeshPhysicalMaterial combined with HDRI lighting.

Lights

Limit the number of lights only to necessary ones. In most cases default lights are sufficient. You can choose from Point, Spot, Directional, Hemisphere or RectArea.

Simple environment reflections

Use any small size .jpg or .png to add global or/and individual reflections.

HDRI

To improve the performances, you can lighten your scene by an HDR image only, without using any other light sources. Keep HDR file size under 1.5MB. You can have global or separate HDR on material, but try to avoid that to save on size.

Shadows

If your object is static, for best performance, you may bake shadow and ambient occlusion maps and apply them to the plane under the object.

Due to current technology limitations, we are forced to ask our clients to follow a specific set of rules with the common goal of achieving the best possible experience of using Unlimit3D software.

Maximum size of input files

Input files can include but are not limited to textures, optional parts, etc. We divided our most common 3D products into simple categories. Please note that these file sizes are for optimal experiences but not a must-have. In the web 3D, all resources are taken into account. While the model can work on your previewing device, on someone with weaker configuration it may not, so we encourage you to be as optimal as possible.

Simple complexity products: 1MB

Advanced complexity products: 3MB

High complexity products: 5MB

Extreme complexity products: 30MB

For 3D ads: 1.7MB

*Note for 3D ads: We recommend 1.7MB as most DSPs have 2.4MB total ad file size restriction. However, if a user prepares an ad for direct publishing or premium ads, the file size can be higher.

Maximum number of polygons

The goal is to have as few polygons/triangles/vertices as possible. That will reduce download time and improve performances while using Unlimited3D.

Simple complexity products: 2.000

Advanced complexity products: 20.000

High complexity products: 50.000

Extreme complexity products: 400.000

For 3D ads: As low as possible

3D file formats

Unlimited3D software supports the following file formats: .fbx, .obj, .glb

Maximum textures size

For all types of 3D projects on Unlimited3D (except for 3D for mobile devices), we recommend using textures with a maximum size of 2048px. Depending on the model complexity, a size of 4096px is also a possibility but only if it’s necessary.

UV mapping

For the most aesthetically pleasing 3D solution we recommend using a specific UV map or seamless UV map.

Unwrapped UV's

Unlimited3D software supports Unwrapped UV maps, however, in case of extreme complexity 3D, we advise using Unwrap only if necessary.

Low, Mid or High-poly

If you were reading through all of our documentation, you probably got the right idea when to use low, mid or high-poly modelling. Just in case we will propose what we consider is the best practice corresponding to the previously mentioned types of models.

1. For Simple complexity products: Mid-poly or low baked optionally
2. For Advanced complexity products: Mid-poly or low baked optionally
3. For High complexity products: Mid-poly or low baked optionally
4. For Extreme complexity products: High-poly for some parts (not recommended, but if the product requires that level of detail to achieve an aesthetically pleasing look than you should use high-poly), Mid-poly or Low baked optionally
5. For 3D ads: Low-poly

AR optimization

ARcore (Android compatible) .glb file format and ARKit (iOS compatible) .usdz file format For more detailed instructions we advise our users to check official google and apple guidelines for optimal AR experience:

https://developers.google.com/ar/design ,

https://developer.apple.com/design/human-interface-guidelines/ios/system-capabilities/augmented-reality/

Due to current technology limitations and the nature of 3D models that are viewed on mobile devices, we are strongly recommending our users to read the following guidelines.

Rules to follow for solutions that will be viewed on mobile:

1. Before starting a project on Unlimited3D, consider having a special solution of the same product for a desktop version and a mobile version.
2. When working on a 3D model for a mobile device, please work with textures that are 1K or less. As the average screen size of the mobile devices is pretty low compared to desktop, the model will still look aesthetically pleasing but the performances will not be compromised.
3. Avoid using HDR maps when the model is intended.

If you need a 3D Configurator (you want to show different types of the same model, for example: different tires on a car model, different wrists on a watch or different laces on a shoe, etc), then you need to additionally prepare your model before uploading.

Logical grouping of elements that will be configured

Let’s take an example of a car model. Let’s say you finished modeling a car or you purchased a model of one. If you modeled the product from the scratch, depending on your workflow, you will most likely have more objects/entities in the scene at the end of the modeling process. If you purchased the model it usually comes with separated objects/entities, so you will have to merge it in the first step.

The first step you should do is decide, what parts you will want to change in your 3D Configurator. For this example, we will say we want to change the tires. So, in that case, we have to combine tires into a single separate entity/element, and the rest of the car into a single separate entity/element. So that will leave us with 2 different entities/elements, the tires and the rest of the car.

Now that we made sure the car is divided the way we want, we want to get the new type of tires and prepare them the same way we did with the previous ones.

Now that we prepared the tires, we need to place them in the same place as the original ones. They are currently overlapping, but we will have the option of turning them off on the Unlimited3D platform. This preparation will allow you to make a 3D Configurator of switching between these two types of tyres.

With the same preparation, you can choose any other parts of your product that you wish to present in different versions.

Specific requirements of model upload for semi 3D Configurator w/ annotations

An annotation is extra information associated with a particular point in a 3D model or another piece of information. It can be a note that includes a comment or explanation, it can be a trigger button that activates the animation of your 3D product or similar. We offer our clients the possibility to add annotations in their 3D projects. Depending on your needs there are few guidelines you should follow. Example of annotation from our clients that you can see for yourself at https://threedium.co.uk/features.

Specific_requirements_of_model_upload_for_semi_3D_configurator

Annotation image preparation

The background of annotation should never be on 0% opacity. When creating a png. image of your annotation, make sure to provide a picture with at least 1% opacity, as the clickable area will be larger.

Annotation possibilities

Depending on your needs, you might have to include someone with some medior level of knowledge in programming to implement the idea on your website. The things you can achieve by yourself are following:

1. Transformation of object: Once the user clicks on an annotation, the object can be transformed as you wish it to be transformed.
2. Object hiding: Once the user clicks on an annotation, the object will be hidden, and a new one can appear. In this case, the model should be prepared the same way as described in the section about the Logical grouping of elements that will be configured.
3. Camera control: Once the user clicks on an annotation, the camera can change position to some other angle of your product.
4. Lighting: Once the user clicks on an annotation, the lighting can be increased, decreased, turned off or additional light can be turned on.

Model preparation for annotations with animation

In case you wish for an animation to happen with your object when clicking on an annotation you need to prepare the model before uploading. The animated part of the model should have a corresponding Gizmo. To explain better we will take the example of a car and the door being the interactive part. Firstly we prepare all the objects that will have the animation, in this case, the right door on a sample car should be detached from the rest of the model and form a single entity/object.

After that, we need to adjust the gizmo to the most logical place so that when we simulate the door opening, it looks as natural as possible.

If the gizmo is placed in the correct position then the animation of the object with the rotate command will look smooth and natural.

Some software requires you to specifically bake the gizmo/pivot on the needed location.

If you have a jewellery model that you wish to publish on our platform there are several guidelines you need to follow.

Best modelling practice when using Unlimited3D shader/decoration

If you intend to make most of our shader we recommend the following guidelines. Diamond should be modelled as a single geometry with faces pointing outwards. The diamond should not have overlapping geometry.

Faces should be pointing outwards.

Model should be made of single faces with no overlapping geometry.

Number of faces/polygons

As was the case with every model that goes on our platform, we want to have the as least possible amount of faces. While we have successfully published projects of jewellery with up to 300K polygons, we advise you to try to be as responsible as possible with the number of faces.

Decoration entry / Custom Unlimited3D Shader

For the needs of diamond models, we developed a custom Shader to help you present your jewellery models in the most aesthetically pleasing way possible. Through our example, we will show you how to edit the values and reach the best result.

Every piece of diamond has to be a single entity/object

For our Shader to individually apply the Environment Map and create the most realistic result, every piece of the diamond needs to be individually detached.

Size of an Environment Map

Depending on the level of detail and the number of diamonds, you should consider the size of the Environment Map. If there is only a single diamond you can use the size of 512x512px. If there is more than one we advise using a 256px or even 128px size Environment Map.