English
Deutsch
日本語
简体中文
Français
An import brings in what the file happens to carry, and most surprises come from that: a unit the file does not state, a texture the exporter left somewhere else, or a channel the file uses the other way round. This page goes through the symptoms one at a time.
Applies to BASIC, STUDIO, CINEMA · Needs the 3D Import add-on (the licence screen calls it 3D Importer, included in the CINEMA trial) · You need: the importer open on a file.
The object is far too large or far too small
Cause. The importer has to guess the unit of a file that does not state one, and its guess can be wrong. When the result is implausible — under a centimetre, or more than about 20 metres from its own centre to its corner — it asks first: Warning with The 3D object is very large! Are you sure the scale is correct? (or …very small!) and the choice Continue or Cancel. The usual right answer is Cancel. The test is on that distance from the centre, so a room-sized box can still pass it.
What to do. Press the unit the file was modelled in — the row offers mm, cm, m, in, ft and yd — and read Object Size again; correct what is left with Scale Factor. A unit-less format such as glTF or .glb is guessed, and the guess can be a factor of 100 out, so check it against a dimension you know. See Import a 3D object.
It has no texture, or the wrong one
Cause. The importer looks for the texture files in a small number of places relative to the model. A lookup that finds nothing is only written to the log, not reported, so the object arrives untextured. A slot can also be filled with the wrong kind of map, because the file names a texture the importer takes at its word.
What to do. Assign the maps by hand in the importer’s material list. The picker filters by the slot you are filling, so pick the slot first and then the file. Where the importer looks and what each slot expects is in Shaders and textures of an imported object.
The gloss is inverted
Cause. Roughness and glossiness are the same information the other way round, and the file does not always say which one it carries.
What to do. Switch Texture Type for that map. Nothing else has to change.
My material fix did not show up in an old set
Cause. An object that is already standing in a set keeps its own colour and surface overrides. Changing the material of the library entry does not reach into a set that was saved before.
What to do. Change the material on the object in the set, or delete the object and place it again from the library.
Re-importing the archive changes nothing
You import the archive again and get a success title over a nothing-happened message: 3D Object Import Succeeded — No 3D objects were imported. All 3D objects are already up to date.
Cause. The importer compares revisions and skips an object whose revision is not newer than your copy’s. The archive really does hold the same revision — the sender exported it without writing the entry again, so nothing about it is newer than what you have.
What to do. Ask the sender to open the object with Edit 3D Object and press Apply once (that raises the revision), then export again. With a newer revision in the archive the import takes the update route: Duplicated 3D Object appears, counts how many of the objects you already have and how many are new, and offers Overwrite Existing, New Only and Cancel. Overwrite Existing replaces your copy in place, for every setup that uses it. Deleting your copy before the import works too. See Share, update and back up your 3D objects.
The animation moves differently than it did in Blender
Cause. Imported animation is played back linearly. Easing you built into the curves of the source file is not reproduced.
What to do. Bake the easing into more keyframes in the source file, or rebuild the motion in the animation editor. See Pose and animate an imported object.
My 3D library is empty, or every object shows a warning marker
Cause. The library reads from one folder, and its textures live in a subfolder of that folder. If the path points somewhere else — a drive that is not mounted, a synchronised folder that has not finished, a path you changed — the objects or their textures are not found. A missing object is drawn as a marker in the studio view and keeps its row in the set list.
What to do. Check the 3D-objects path in the App Manager under Library Settings. Changing the path does not move any files, so set the path on a destination that already holds your objects, or copy the files first and change the path afterwards. Your folder structure stays with the library you leave and the new one brings its own, so a destination you have not filled yet shows an empty library rather than empty groups. A synchronised folder has to have finished syncing before you start the program.
The import failed
| Message | Cause | What to do |
|---|---|---|
| Error — Failed to Load Model | The file could not be read | Check the format against 3D import: what the add-on reads and re-export it |
| Error — Model contains no meshes | The file was read but holds no geometry | Export the geometry, not only lights, cameras or empties |
| Error — Image is too large or Image is not supported or corrupt | A texture could not be used | Re-export the texture as JPG or PNG, no larger than 8192 pixels on an edge |
| Failed to Save Resource — Disk is full… or File is in use by another process | The object could not be written into your library | Free space, or close whatever holds the file, then import again |
| Error — Importing 3D objects has failed | An archive import broke off | Import again; a partially imported archive can leave single objects behind, so check your library afterwards |
| Failed to Export 3D Objects | The archive could not be written | Check the target folder, and that the file is not open elsewhere |
Cancelling an import can leave texture files behind in your library folder. They are harmless, and you can delete them.
Not a bug
- Warning — You are about to overwrite this 3D object. This operation cannot be undone! is exactly what it says. There is no undo for it.
- What arrives from a file depends on the file and on the program that wrote it. Two exports of the same model from different tools do not have to behave alike; try it before you plan a shoot around it.
- A heavy imported object slows down the studio view and the render of the whole set, not only itself. Geometry problems are much cheaper to fix before the import than after.
- The shader picker of a material is titled Select Shader and lists the five shaders; it replaces nothing else about the material.