Import and export >
Troubleshoot file import and export

The following table lists common problems and possible solutions related to file import.

Problem/Error Message | Possible Solution
--- | ---
The following message appears when importing a model: You are importing a high resolution mesh directly into Mudbox, which may not yield optimal performance. To get high resolution detail into Mudbox and achieve optimal performance, consider using Import as Layer or Mesh Displace with a subdivided low resolution mesh. | The message indicates that the model being imported has a polygon count greater 150,000 which may degrade interactive performance (tumble, track, and dolly) if it is used as the base mesh and then subdivided further. Mudbox has proprietary features for optimizing the display and interactive performance when working with high resolution models but these features work best when the model imported as the base level has a lower polygon count. The features described in this message can be used to recreate the subdivision level structure using a lower resolution mesh. For more information, see Import a model from ZBrush and Sculpt using a displacement map.
The following message appears when using the Send To Maya feature: Mudbox cannot find Maya.Please set the location of Maya in the 'Path' section of the Preferences window, then try again. | The message indicates that the receiving application cannot be found for launching at the default directory location as expected. Confirm that the Maya path is set correctly in the Paths section of the Preferences window or edit as required. For more information, see Paths.
The following message appears when importing a model: Problems were encountered, see the Log file. | Mudbox has encountered some problem with the file being imported. In most situations a description of the problem will appear in the Log file (Windows >Log) . For example, If a model is imported containing a UV set that crosses a UV tile boundary, it will result in poor interactive performance or worse affect the stability of the application. An error message will appear in the Log file indicating this situation when it occurs. For best results remove or edit the UV set to correct the situation and import the mesh again.
Imported OBJ file from another 3D application cannot be sculpted or subdivided. | The polygon topology on the model may not be supported by Mudbox. For more information, see Prepare a model for sculpting. Check that the model does not contain any non-manifold topology that would cause problems for Mudbox by loading it into the originating modeling application. Some 3D modeling applications have features for checking and fixing non-manifold conditions and degenerate edges.
Importing OBJ file from another 3D application causes Mudbox to exit with an Unknown error has occurred message. | Attempt to import and save the same OBJ file into another 3D application such as Maya and see if the problem is still present when importing the second version of the OBJ file. If the problem still persists, it may indicate that the original OBJ file is corrupt.
Shading materials on a model exported as an OBJ format file from another 3D modeling application do not appear on the model when imported to Mudbox. | Shading materials from other 3D applications do not get transferred with an OBJ file. The OBJ file format is a simple data format that represents 3D geometry alone: the position of each vertex, the UV texture coordinate associated with a vertex, the normal at each vertex, and the faces that get combined to make a model. While some 3D applications can export an MTL file with an OBJ file to include basic material information, this is not supported by Mudbox currently. The CgFX shading specification can be used as a common shading material format between 3D applications (if they support it) and Mudbox.
Mudbox file (.mud) loads successfully but image texture maps are missing. | The directory location that Mudbox is expecting to source the files for the texture maps may have changed or the files may be missing or have had their file names changed. Mudbox will load a .mud file despite missing image maps. Check the file locations, names, and so on and correct as required. For more information on what failed to load, review the log file by selecting Windows > Log.
Imported texture map does not appear correct on the model. It appears jumbled, distorted, or mismatched in relation to the object. | A texture map is applied to a polygonal model based on the layout of the model’s UV texture coordinates. If these have not been taken into consideration and laid out prior to painting or importing a map, or the map was created for a model with a different UV layout, it is unlikely the image map will appear correct when applied to the model. For more information, see UVs overview and Prepare a model for painting.
Some of the entities in my Mudbox file did not transfer as expected when I exported it to another 3D application I’m using. | Some file formats support only a small subset of entities. Some 3D applications only support a small number of file formats. For information on the file formats that Mudbox can read and write, see, Model file formats. FBX supports the largest number of entities when transferring your Mudbox work between 3D applications. For more information, see Export using FBX.
The following message appears when importing a TARGA format file into the File Browser: TGA Image <filename> has an unsupported pixel size (<n> bits) -- Mudbox supports 8, 24, and 32 bits per pixel. | In some software applications, TARGA format files can be produced with different pixel size values. Mudbox only supports TARGA files that are 8 , 24, or 32 bits per pixel. importing and then saving the TGA format file using an image editing application such as Photoshop may be successful in making the file compatible within Mudbox or saving the file in a different file format that is supported by Mudbox. For more information, see Image file formats.
The model appears garbled or messed up when its imported to Mudbox from another modeling application and the Import As Layer... option was used. | If the vertex IDs do not match exactly between the two models the vertices will appear in the wrong locations when the model is imported when the Match by: Vertex ID option is selected as the import option. If the vertex positions match, but vertex ids are suspect, use the Match by: UV Position option instead.
Joint positions do not match the imported model’s current position when it is imported to Mudbox. | In some situations, a model may have to be placed into its bind pose position prior to export as an FBX file before importing to Mudbox. The model can subsequently be posed using the importedjoints and weight settings once it is in Mudbox.