OBJ/MTL import: behavior changed for missing texture files #99502

New Issue

Scurest · 2022-07-06T23:15:57+02:00

Scurest commented

2022-07-06 23:15:57 +02:00

System Information
Operating system: Linux

Blender Version
Broken: blender-3.3.0-alpha+master.e6e9f1ac5a2d (from June 15th)

Short description of error
The C++ OBJ importer behaves differently than the Python importer when it finds a missing texture file.

The Python importer creates a "placeholder" image pointing to where the file should be and hooks it up like usual. This produces the characteristic eye-bleed magenta signaling a missing texture. The missing file is reported with File > External Data > Report Missing Files. You can slot the missing image in after the fact to repair it.

The C++ importer does not create an image. It creates an Image Texture node but doesn't hook it up. No magenta signalling a file is missing, no way to know what the texture should have been.

I don't know if you consider this a bug, but the old way seems better. The meaning "pink material = missing textures" is well known (eg. on stackexchange). The glTF importer also got a request for, and changed to have, the old OBJ behavior.

Exact steps for others to reproduce the error
Import a .mtl with a line like map_Kd this_file_does_not_exist.png.

**System Information** Operating system: Linux **Blender Version** Broken: blender-3.3.0-alpha+master.e6e9f1ac5a2d (from June 15th) **Short description of error** The C++ OBJ importer behaves differently than the Python importer when it finds a missing texture file. The Python importer creates a ["placeholder" image](https://github.com/dfelinto/blender/blob/87a0770bb969ce37d9a41a04c1658ea09c63933a/release/scripts/modules/bpy_extras/image_utils.py#L74-L77) pointing to where the file should be and hooks it up like usual. This produces the characteristic eye-bleed magenta signaling a missing texture. The missing file is reported with File > External Data > Report Missing Files. You can slot the missing image in after the fact to repair it. ![old.png](https://archive.blender.org/developer/F13263738/old.png) The C++ importer does not create an image. It creates an Image Texture node but doesn't hook it up. No magenta signalling a file is missing, no way to know what the texture should have been. ![new.png](https://archive.blender.org/developer/F13263758/new.png) I don't know if you consider this a bug, but the old way seems better. The meaning "pink material = missing textures" is well known (eg. on stackexchange). The glTF importer also got a [request for](https://github.com/KhronosGroup/glTF-Blender-IO/issues/1296), and changed to have, the old OBJ behavior. **Exact steps for others to reproduce the error** Import a .mtl with a line like `map_Kd this_file_does_not_exist.png`.

Scurest commented

2022-07-06 23:15:57 +02:00

Added subscriber: @scurest

Scurest changed title from ~~OBJ/MTL import: beahvior changed for missing texture files~~ to OBJ/MTL import: behavior changed for missing texture files

2022-07-07 00:43:04 +02:00

Omar Emara commented

2022-07-07 08:51:01 +02:00

Added subscriber: @OmarEmaraDev