FBX exporter uses Mesh Datablock to name exported objects instead of object names #62663

New Issue

Ludvik Koutny · 2019-03-16T20:04:26+01:00

Ludvik Koutny commented

2019-03-16 20:04:26 +01:00

System Information
Operating system: Windows 10
Graphics card: GTX1080Ti

Blender Version
Broken: 2.8 latest master
Worked: Probably never

Short description of error
FBX exporter uses Mesh Datablock names to name exported objects instead of object names, so any application FBX from Blender is imported to has bad object names, such as sphere.001, cube.002,etc... This doesn't make any sense, especially since multiple objects can reference the same mesh datablock (instances), and people generally do not bother to name mesh datablocks. FBX exporter needs to use object names for naming, not mesh datablocks.

Exact steps for others to reproduce the error
1, In a new scene, create a few mesh objects.
2, Rename them in the outliner.
3, Export them using FBX.
4, Reimport them and notice wrong names.

Result: Names of objects in the exported FBX are wrong - named after mesh datablocks.

Expected: Names of the objects in the exported FBX match names of the objects in the scene.

**System Information** Operating system: Windows 10 Graphics card: GTX1080Ti **Blender Version** Broken: 2.8 latest master Worked: Probably never **Short description of error** FBX exporter uses Mesh Datablock names to name exported objects instead of object names, so any application FBX from Blender is imported to has bad object names, such as sphere.001, cube.002,etc... This doesn't make any sense, especially since multiple objects can reference the same mesh datablock (instances), and people generally do not bother to name mesh datablocks. FBX exporter needs to use object names for naming, not mesh datablocks. **Exact steps for others to reproduce the error** 1, In a new scene, create a few mesh objects. 2, Rename them in the outliner. 3, Export them using FBX. 4, Reimport them and notice wrong names. Result: Names of objects in the exported FBX are wrong - named after mesh datablocks. Expected: Names of the objects in the exported FBX match names of the objects in the scene.

Ludvik Koutny commented

2019-03-16 20:04:27 +01:00

Added subscriber: @Rawalanche

Bastien Montagne commented

2019-03-16 22:26:07 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2019-03-16 22:26:07 +01:00

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Cannot confirm here, and FBX code certainly uses Object name for the Model node, not its geometry…

Please follow our [submission template and guidelines](https:*developer.blender.org/maniphest/task/edit/form/1/), also read [these tips about bug reports](https:*wiki.blender.org/wiki/Process/Bug_Reports), and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, **small and simple** .blend and/or other files to do so if needed, etc. Cannot confirm here, and FBX code certainly uses Object name for the Model node, not its geometry…

Ludvik Koutny commented

2019-03-17 10:15:13 +01:00

In #62663#641901, @mont29 wrote:
Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Cannot confirm here, and FBX code certainly uses Object name for the Model node, not its geometry…

Uh, what? I think this is as valid bug reports as it gets. Maybe you are seeing something else than me?

> In #62663#641901, @mont29 wrote: > Please follow our [submission template and guidelines](https:*developer.blender.org/maniphest/task/edit/form/1/), also read [these tips about bug reports](https:*wiki.blender.org/wiki/Process/Bug_Reports), and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, **small and simple** .blend and/or other files to do so if needed, etc. > > Cannot confirm here, and FBX code certainly uses Object name for the Model node, not its geometry… Uh, what? I think this is as valid bug reports as it gets. Maybe you are seeing something else than me? ![image.png](https://archive.blender.org/developer/F6838257/image.png)

Ludvik Koutny commented

2019-03-17 10:21:39 +01:00

Anyway, this is a bit more complicated problem indeed. Blender has this unique weird concept of datablock being something user can explicitly name. It works in case of Blender:

But it doesn't work in case of Unreal Engine 4:

Anyway, this is a bit more complicated problem indeed. Blender has this unique weird concept of datablock being something user can explicitly name. It works in case of Blender: ![image.png](https://archive.blender.org/developer/F6838267/image.png) But it doesn't work in case of Unreal Engine 4: ![image.png](https://archive.blender.org/developer/F6838273/image.png)

Bastien Montagne commented

2019-03-17 15:14:26 +01:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2019-03-17 15:14:26 +01:00

Bastien Montagne self-assigned this 2019-03-17 15:14:26 +01:00

Bastien Montagne commented

2019-03-17 15:14:26 +01:00

Well, report was missing two crucial pieces actually:

A .blend file to reproduce the issue (given incomplete info I had, I though that it might have been a specific set-up triggering the issue).
More important than anything, complete info with detailed steps to reproduce it (since it's not reimporting FBX file into Blender that is the issue, it’s importing it into UE4).

Now am sorry, but if UE4 decides to use the geometry part of FBX data's name as its object name, we cannot do anything about it. Blender's FBX exporter export Model FBX nodes with object name, and Geometry FBX nodes with obdata (mesh) names, as it's expected.

Well, report was missing *two* crucial pieces actually: - A .blend file to reproduce the issue (given incomplete info I had, I though that it might have been a specific set-up triggering the issue). - More important than anything, complete info with detailed steps to reproduce it (since it's not *reimporting* FBX file into Blender that is the issue, it’s *importing* it into UE4). Now am sorry, but if UE4 decides to use the geometry part of FBX data's name as its object name, we cannot do anything about it. Blender's FBX exporter export `Model` FBX nodes with object name, and `Geometry` FBX nodes with obdata (mesh) names, as it's expected.

Ludvik Koutny commented

2019-03-17 18:38:27 +01:00

In #62663#642133, @mont29 wrote:
Well, report was missing two crucial pieces actually:

A .blend file to reproduce the issue (given incomplete info I had, I though that it might have been a specific set-up triggering the issue).

More important than anything, complete info with detailed steps to reproduce it (since it's not reimporting FBX file into Blender that is the issue, it’s importing it into UE4).

Now am sorry, but if UE4 decides to use the geometry part of FBX data's name as its object name, we cannot do anything about it. Blender's FBX exporter export Model FBX nodes with object name, and Geometry FBX nodes with obdata (mesh) names, as it's expected.

I guess that is a fair point, but in may DCC software packages, users can't even name the geometry data, so they probably share the name with object. Blender allows it, but that means user will now have to go through the entire scene and name every single mesh datablock using the object name, with further limitation that datablocks in blender can't share the identical name. Surely this can be handled better.

> In #62663#642133, @mont29 wrote: > Well, report was missing *two* crucial pieces actually: > # A .blend file to reproduce the issue (given incomplete info I had, I though that it might have been a specific set-up triggering the issue). > # More important than anything, complete info with detailed steps to reproduce it (since it's not *reimporting* FBX file into Blender that is the issue, it’s *importing* it into UE4). > > Now am sorry, but if UE4 decides to use the geometry part of FBX data's name as its object name, we cannot do anything about it. Blender's FBX exporter export `Model` FBX nodes with object name, and `Geometry` FBX nodes with obdata (mesh) names, as it's expected. I guess that is a fair point, but in may DCC software packages, users can't even name the geometry data, so they probably share the name with object. Blender allows it, but that means user will now have to go through the entire scene and name every single mesh datablock using the object name, with further limitation that datablocks in blender can't share the identical name. Surely this can be handled better.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

FBX exporter uses Mesh Datablock to name exported objects instead of object names #62663

A .blend file to reproduce the issue (given incomplete info I had, I though that it might have been a specific set-up triggering the issue).

More important than anything, complete info with detailed steps to reproduce it (since it's not reimporting FBX file into Blender that is the issue, it’s importing it into UE4).