diff options
| author | Aras Pranckevicius <aras_p> | 2022-03-20 15:59:16 +0300 |
|---|---|---|
| committer | Aras Pranckevicius <aras@nesnausk.org> | 2022-03-23 14:08:17 +0300 |
| commit | 1781c6002ae935af9c611dc90e12a56faaa6ed68 (patch) | |
| tree | 4b4a22fae2ff09dcd05dd3aaf0c4e0bf85423d2a /source/blender/editors | |
| parent | 9ed566efb67a20c66e6d8c2965546b89bdd9764e (diff) | |
Fix T96470 new obj exporter writing material groups
The logic in the code was _completely different_ from the documentation
and what the python exporter in 3.0 did. The new code assumed that
"export material groups" meant "append material name to the object name",
and was only ever kicking in when the "export object groups" option was
also checked. But the proper behavior (as in 3.0 exporter & the online docs),
is to emit g objectname_materialname before each usemtl line. Which is something entirely else.
Cherry picked from b9123b806fc4 (D14349) with minor conflict fixes.
Diffstat (limited to 'source/blender/editors')
| -rw-r--r-- | source/blender/editors/io/io_obj.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/source/blender/editors/io/io_obj.c b/source/blender/editors/io/io_obj.c index 3262397bf63..428ace6cfe5 100644 --- a/source/blender/editors/io/io_obj.c +++ b/source/blender/editors/io/io_obj.c @@ -359,7 +359,7 @@ void WM_OT_obj_export(struct wmOperatorType *ot) "export_material_groups", false, "Export Material Groups", - "Append mesh name and material name to object name, separated by a '_'"); + "Generate an OBJ group for each part of a geometry using a different material"); RNA_def_boolean( ot->srna, "export_vertex_groups", |