FBX Custom property error #59202

New Issue

Jan Javůrek · 2018-12-11T19:01:43+01:00

Jan Javůrek commented

2018-12-11 19:01:43 +01:00

System Information
DxDiag.txt

Blender Version
Broken:
2.79.6 hash:642c315bae1
2.8 hash:d415b5c7b85

Short description of error

When I set any custom properties to an object, export the object to FBX, then import it back, on the imported model I get an error message when I wanna edit, add or delete custom properties.

Exact steps for others to reproduce the error

create a cube
in Properties/Object add Custom property (default is float prop=1.000)
export the cube to FBX with custom properties
import the FBX back
try do edit (click edit...not just drag the slider), add or remove custom properties and get error message

More description

untitled_binary.fbx untitled_ascii.fbx

I tried to create a box with the same property in 3ds Max...I imported similar box with the same property from Blender...in Max exported both boxes into ASCII and Binary fbx (ASCII property closeup in picture below). Then I imported the Binary version into Blender...box with property from Max is editable and Box from Blender is not.

Am I doing something wrong or is it a bug?
Thank you

**System Information** [DxDiag.txt](https://archive.blender.org/developer/F5924085/DxDiag.txt) **Blender Version** Broken: 2.79.6 hash:642c315bae1 2.8 hash:d415b5c7b85 **Short description of error** When I set any custom properties to an object, export the object to FBX, then import it back, on the imported model I get an error message when I wanna edit, add or delete custom properties. **Exact steps for others to reproduce the error** 1. create a cube 2. in Properties/Object add Custom property (default is float prop=1.000) 3. export the cube to FBX with custom properties 4. import the FBX back 5. try do edit (click edit...not just drag the slider), add or remove custom properties and get error message **More description** ![error_FBX_properties.jpg](https://archive.blender.org/developer/F5924138/error_FBX_properties.jpg) [untitled_binary.fbx](https://archive.blender.org/developer/F5924142/untitled_binary.fbx) [untitled_ascii.fbx](https://archive.blender.org/developer/F5924143/untitled_ascii.fbx) I tried to create a box with the same property in 3ds Max...I imported similar box with the same property from Blender...in Max exported both boxes into ASCII and Binary fbx (ASCII property closeup in picture below). Then I imported the Binary version into Blender...box with property from Max is editable and Box from Blender is not. Am I doing something wrong or is it a bug? Thank you

Jan Javůrek commented

2018-12-11 19:01:43 +01:00

Added subscriber: @skywalger

Pavel Křupala commented

2018-12-12 09:38:10 +01:00

Added subscribers: @mont29, @BlenderFreak

Pavel Křupala commented

2018-12-12 09:38:10 +01:00

@mont29 Hi Bastien, I can confirm this as a bug in latest stable 2.79, nightly 2.79 and 2.8 versions, and it looks like the _RNA_UI property is not serialized to a dictionary?

Philipp Oeser changed title from ~~Custom property error~~ to FBX Custom property error

2018-12-12 09:53:44 +01:00

Philipp Oeser commented

2018-12-12 11:03:26 +01:00

Added subscriber: @lichtwerk

Philipp Oeser self-assigned this 2018-12-12 11:03:26 +01:00

Philipp Oeser commented

2018-12-12 11:03:26 +01:00

Can also confirm.

on export fbx_data_element_custom_properties(props, bid) will include _RNA_UI and possibly other rna props...
(which probably should be exluded).

Will have a look...

Can also confirm. on export `fbx_data_element_custom_properties(props, bid)` will include `_RNA_UI` and possibly other rna props... (which probably should be exluded). Will have a look...

blender-admin commented

2018-12-12 11:20:15 +01:00

This issue was referenced by e4f4053de6

This issue was referenced by e4f4053de64eaa04b0199eea8f55a5f6b8b456dd

Bastien Montagne commented

2018-12-12 11:40:37 +01:00

@lichtwerk exporting _RNA_UI indeed sounds bad, I think a good thing to do would be to skip all props which name starts with _ (this is common convention in python to mark as 'private', think it would make sense to never export those)?

@lichtwerk exporting _RNA_UI indeed sounds bad, I think a good thing to do would be to skip all props which name starts with `_` (this is common convention in python to mark as 'private', think it would make sense to never export those)?

Philipp Oeser commented

2018-12-12 15:31:56 +01:00

Changed status from 'Open' to: 'Resolved'

Philipp Oeser closed this issue

2018-12-12 15:31:56 +01:00

Pavel Křupala commented

2018-12-13 10:23:21 +01:00

@lichtwerk Hi Philipp, can I ask you, will this be propagated also to 2.79 nightly build?