Non-existant/Hidden Custom property bug on .glb export #77

New Issue

Triager-bot · 2026-04-13T15:50:45Z

Triager-bot commented

2026-04-13 15:50:45 +00:00

Original bug report: https://projects.blender.org/blender/blender/issues/157282

System Information
Operating system: W11

Blender Version
5.1.0

Short description of error
Custom Properties magically appear on .glb re-import

Exact steps for others to reproduce the error
Download the .blend
Export the object from the .blend to .glb (in the export panel, Toggle Include -> Data -> Custom Properties)
Import the .glb into Blender, you will see Custom Properties in the Object Tab that weren't present/visible when exporting

Extras
I have also included the .glb if for some reason you couldn't reproduce.
The custom prop isn't even accessible using Python API: bpy.data.objects['sink_cylinder_ceramique']['op_bassin']
So it's likely not a UI bug but something else.

Original bug report: https://projects.blender.org/blender/blender/issues/157282 **System Information** Operating system: W11 **Blender Version** 5.1.0 **Short description of error** Custom Properties magically appear on .glb re-import **Exact steps for others to reproduce the error** Download the .blend Export the object from the .blend to .glb (in the export panel, Toggle Include -> Data -> Custom Properties) Import the .glb into Blender, you will see Custom Properties in the Object Tab that weren't present/visible when exporting **Extras** I have also included the .glb if for some reason you couldn't reproduce. The custom prop isn't even accessible using Python API: bpy.data.objects['sink_cylinder_ceramique']['op_bassin'] So it's likely not a UI bug but something else.

image.png

18 KiB

custom_prop_bug.glb

2.9 KiB

Triager-bot added the

Status

Needs review

label 2026-04-13 15:50:45 +00:00

Triager-bot commented

2026-04-13 15:50:55 +00:00

Report is clear

LLM Reasoning

Got it, let's see. The question is whether the bug report clearly describes the issue. Let's check the elements: title, short description, steps to reproduce.

The title mentions "Non-existant/Hidden Custom property bug on .glb export". The body has a short description saying custom properties appear on re-import that weren't there when exporting. Then exact steps: download blend, export to glb with include custom props, import and see them. Also extras mention the Python API issue.

So the steps are clear, the description is concise. Even though there's system info, we ignore that. The clarity of the text and steps—yes, it's clear. So the answer should be Yes.

JSON Data

{
"llm_judgement": true,
"processing_time": 8.89838
}

### Report is clear <details> <summary>LLM Reasoning</summary> Got it, let's see. The question is whether the bug report clearly describes the issue. Let's check the elements: title, short description, steps to reproduce. The title mentions "Non-existant/Hidden Custom property bug on .glb export". The body has a short description saying custom properties appear on re-import that weren't there when exporting. Then exact steps: download blend, export to glb with include custom props, import and see them. Also extras mention the Python API issue. So the steps are clear, the description is concise. Even though there's system info, we ignore that. The clarity of the text and steps—yes, it's clear. So the answer should be Yes. </details> <details> <summary>JSON Data</summary> { "llm_judgement": true, "processing_time": 8.89838 } </details>

Triager-bot commented

2026-04-13 15:51:03 +00:00

Report is specific

LLM Reasoning

Got it, let's analyze this. The bug report has a specific title about a non-existent/hidden custom property on .glb export. The steps to reproduce are detailed: download the blend file, export with specific settings, import and see the issue. It mentions exact steps and even includes an example of a Python API issue related to it. So this is a specific issue because it's about a particular problem (custom properties appearing on re-import) with clear reproduction steps. The answer should be 'Specific'.

JSON Data

{
"llm_judgement": true,
"processing_time": 7.147767
}

### Report is specific <details> <summary>LLM Reasoning</summary> Got it, let's analyze this. The bug report has a specific title about a non-existent/hidden custom property on .glb export. The steps to reproduce are detailed: download the blend file, export with specific settings, import and see the issue. It mentions exact steps and even includes an example of a Python API issue related to it. So this is a specific issue because it's about a particular problem (custom properties appearing on re-import) with clear reproduction steps. The answer should be 'Specific'. </details> <details> <summary>JSON Data</summary> { "llm_judgement": true, "processing_time": 7.147767 } </details>

Triager-bot commented

2026-04-13 15:51:19 +00:00

Report flagged as NOT a duplicate by LLM

GLB/GLTF Export Excludes Image Properties

https://projects.blender.org/blender/blender/issues/153907

System Information
Operating system: Windows 11
Graphics card: RTX 3060 Ti

Blender Version
Broken: 5.0.1
Worked: Never

Short description of error
Blender's GLB import/export supports Custom Properties as "extras":

However, custom image properties are not being serialized to the GLB/GLTF JSON:

...
"nodes": [
  {
    "extras": {
      "object_prop": 1434
    },
    ...
  }
],
"materials": [
  {
    "extras": {
      "material_prop": 1434
    },
    ...
  }
],
"meshes": [
  {
    "extras": {
      "mesh_prop": 1434
    },
    ...
  }
],
...
"images": [
  {
    "bufferView": 4,
    "mimeType": "image/png",
    "name": "Test Image"
  }
],

Script used to add the properties (in attached .blend):

import bpy

object   = bpy.data.objects['Cube']
mesh     = object.data
material = mesh.materials[0]
image    = bpy.data.images['Test Image']

object['object_prop']     = 1434
mesh['mesh_prop']         = 1434
material['material_prop'] = 1434
image['image_prop']       = 1434

Exact steps for others to reproduce the error

Open the provided GLB Custom Property Test.blend
Export .GLB with the export settings already saved in the blend file
Examine the exported GLB Custom Property Test.glb JSON

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.

Bug report 1 is about custom properties appearing on .glb re-import when they weren't present during export. The user exports with "Include -> Data -> Custom Properties" toggled, then imports and sees extra props that weren't there before. Also mentions Python API can't access them, so not a UI bug.

Bug report 2 is about GLB/GLTF export excluding image properties. The steps involve adding custom properties to object, mesh, material, image, exporting, and checking the JSON—finding that image properties aren't serialized. The title says "Excludes Image Properties", and the description talks about extras not including image props.

So the first report is about unexpected appearance of custom props on import (maybe a bug in export/import handling), while the second is about missing image custom properties during export. These are different issues: one is about extra props appearing, the other about missing props (specifically images) during export. So they aren't duplicates.

JSON Data

{
"llm_judgement": false,
"processing_time": 15.396585,
"duplicate_report_number": "153907"
}

### Report flagged as NOT a duplicate by LLM <details> <summary>GLB/GLTF Export Excludes Image Properties</summary> https://projects.blender.org/blender/blender/issues/153907 **System Information** Operating system: Windows 11 Graphics card: RTX 3060 Ti **Blender Version** Broken: 5.0.1 Worked: Never **Short description of error** Blender's GLB import/export supports `Custom Properties` as `"extras"`: <img width="174" alt="image.png" src="attachments/b3e57f60-de4e-4939-84dc-1cfb359abe43"> However, custom image properties are not being serialized to the GLB/GLTF JSON: ```JS ... "nodes": [ { "extras": { "object_prop": 1434 }, ... } ], "materials": [ { "extras": { "material_prop": 1434 }, ... } ], "meshes": [ { "extras": { "mesh_prop": 1434 }, ... } ], ... "images": [ { "bufferView": 4, "mimeType": "image/png", "name": "Test Image" } ], ``` Script used to add the properties (in attached .blend): ```Py import bpy object = bpy.data.objects['Cube'] mesh = object.data material = mesh.materials[0] image = bpy.data.images['Test Image'] object['object_prop'] = 1434 mesh['mesh_prop'] = 1434 material['material_prop'] = 1434 image['image_prop'] = 1434 ``` **Exact steps for others to reproduce the error** 1. Open the provided [GLB Custom Property Test.blend](/attachments/7354f481-9b24-4196-a04a-023f1148ef96) 2. Export .GLB with the export settings already saved in the blend file 3. Examine the exported [GLB Custom Property Test.glb](/attachments/0b84e1f5-5df8-48ad-9b31-aec8cf818d5d) JSON </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce. Bug report 1 is about custom properties appearing on .glb re-import when they weren't present during export. The user exports with "Include -> Data -> Custom Properties" toggled, then imports and sees extra props that weren't there before. Also mentions Python API can't access them, so not a UI bug. Bug report 2 is about GLB/GLTF export excluding image properties. The steps involve adding custom properties to object, mesh, material, image, exporting, and checking the JSON—finding that image properties aren't serialized. The title says "Excludes Image Properties", and the description talks about extras not including image props. So the first report is about unexpected appearance of custom props on import (maybe a bug in export/import handling), while the second is about missing image custom properties during export. These are different issues: one is about extra props appearing, the other about missing props (specifically images) during export. So they aren't duplicates. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 15.396585, "duplicate_report_number": "153907" } </details>

Triager-bot commented

2026-04-13 15:51:32 +00:00

Report flagged as NOT a duplicate by LLM

Alembic export doesn't take 'Custom Properties', as alembic non-standard data.

https://projects.blender.org/blender/blender/issues/50725

System Information
Opensuse Leap 42.1 Linux, ATI graphics card

Blender Version
Blender 2.78b

Short description of error
If i add an custom properties, manually or by python api. Alembic export doesn't take care of them (custom properties).
If the alembic file is reloading in blender the custom properties are disappeared. Same for an extra 3d software (maya , guerilla...)
By exemple all 'extra attr' in maya are exported in native alembic export.
In a robust pipeline the absence of this 'custom properties' is a really problems.

Exact steps for others to reproduce the error

Select cube
type : pby.context.object["MyCustomProps"] = "foo"
or add it manually in properties panel.
file > export alembic
file > import alembic

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the key sections: description and steps to reproduce.

Bug report 1 is about .glb export where custom properties appear on re-import even if they weren't there before. The steps involve exporting a .blend to .glb with custom properties included, then importing back and seeing them. Also mentions Python API can't access the prop, so it's not UI.

Bug report 2 is about Alembic export not taking custom properties (non-standard data). Steps: add custom props via Python or manually, export as Alembic, import back, and they disappear. Also mentions other software like Maya has this issue.

The issues are different: one is .glb export adding unexpected custom props on re-import, the other is Alembic export not preserving custom props (they disappear). The file formats are different (.glb vs Alembic), and the problems are opposite in a way—1 has extra props appearing, 2 has props disappearing. So they're not the same issue.

JSON Data

{
"llm_judgement": false,
"processing_time": 12.953069,
"duplicate_report_number": "50725"
}

### Report flagged as NOT a duplicate by LLM <details> <summary>Alembic export doesn't take 'Custom Properties', as alembic non-standard data.</summary> https://projects.blender.org/blender/blender/issues/50725 **System Information** Opensuse Leap 42.1 Linux, ATI graphics card **Blender Version** Blender 2.78b **Short description of error** If i add an custom properties, manually or by python api. Alembic export doesn't take care of them (custom properties). If the alembic file is reloading in blender the custom properties are disappeared. Same for an extra 3d software (maya , guerilla...) By exemple all 'extra attr' in maya are exported in native alembic export. In a robust pipeline the absence of this 'custom properties' is a really problems. **Exact steps for others to reproduce the error** - Select cube - type : pby.context.object["MyCustomProps"] = "foo" or add it manually in properties panel. - file > export alembic - file > import alembic </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the key sections: description and steps to reproduce. Bug report 1 is about .glb export where custom properties appear on re-import even if they weren't there before. The steps involve exporting a .blend to .glb with custom properties included, then importing back and seeing them. Also mentions Python API can't access the prop, so it's not UI. Bug report 2 is about Alembic export not taking custom properties (non-standard data). Steps: add custom props via Python or manually, export as Alembic, import back, and they disappear. Also mentions other software like Maya has this issue. The issues are different: one is .glb export adding unexpected custom props on re-import, the other is Alembic export not preserving custom props (they disappear). The file formats are different (.glb vs Alembic), and the problems are opposite in a way—1 has extra props appearing, 2 has props disappearing. So they're not the same issue. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 12.953069, "duplicate_report_number": "50725" } </details>

Triager-bot commented

2026-04-13 15:51:48 +00:00

Report flagged as NOT a duplicate by LLM

PointerProperty not showing under Scene Properties > Custom Properties

https://projects.blender.org/blender/blender/issues/153105

System Information
Operating system: Windows-10-10.0.26220-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 591.59 Opengl Backend

Blender Version
Broken: version: 5.0.1, branch: blender-v5.0-release, commit date: 2025-12-15 16:36, hash: a3db93c5b259
Worked: (newest version of Blender that worked as expected)

Short description of error
Im not sure if this is related to these changes, https://projects.blender.org/blender/blender/issues/141042

I was trying to fix an addon when i noticed my PointerProperties does exist under bpy.context.scene, but they doesnt show under the Scene Properties > Custom Properties panel like before.

Exact steps for others to reproduce the error

open attached file ending with bl5 in blender 5.0.1
Run the script
Notice that the property does exist, but doesnt show under Scene Properties > Custom Properties
open attached file ending with bl4.5 in blender 4.5
Run the script
Notice the custom property does show in the Scene Properties > Custom Properties

Example code comes from Blenders Api, not actual code from my addon. This is just to show simple showcase
Source: https://docs.blender.org/api/current/bpy.props.html#collection-example

LLM Reasoning

Got it, let's analyze the two bug reports. First, look at the description and steps for each.

Bug Report 1 is about custom properties appearing on .glb re-import when they weren't there before. The steps involve exporting to glb with custom properties included, then importing back and seeing them appear. The issue is that custom props are magically present after import.

Bug Report 2 is about PointerProperties not showing under Scene Properties > Custom Properties in Blender 5.0.1, but they do show in 4.5. The steps involve opening files in different versions, running a script, and checking the UI panel. The problem here is visibility of custom properties (specifically PointerProperties) in the UI.

The key differences: Report 1 is about .glb export/import causing unexpected custom props to appear, while Report 2 is about custom properties (PointerProperties) not showing in the Scene Properties panel in a specific version. The issues are different—one is about import/export behavior leading to extra props, the other is about UI visibility of existing props. So they're not the same issue.

JSON Data

{
"llm_judgement": false,
"processing_time": 15.292867999999999,
"duplicate_report_number": "153105"
}

### Report flagged as NOT a duplicate by LLM <details> <summary>PointerProperty not showing under Scene Properties > Custom Properties</summary> https://projects.blender.org/blender/blender/issues/153105 **System Information** Operating system: Windows-10-10.0.26220-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 591.59 Opengl Backend **Blender Version** Broken: version: 5.0.1, branch: blender-v5.0-release, commit date: 2025-12-15 16:36, hash: `a3db93c5b259` Worked: (newest version of Blender that worked as expected) **Short description of error** Im not sure if this is related to these changes, https://projects.blender.org/blender/blender/issues/141042 I was trying to fix an addon when i noticed my PointerProperties does exist under bpy.context.scene, but they doesnt show under the Scene Properties > Custom Properties panel like before. **Exact steps for others to reproduce the error** 1. open attached file ending with bl5 in blender 5.0.1 2. Run the script 3. Notice that the property does exist, but doesnt show under Scene Properties > Custom Properties 4. open attached file ending with bl4.5 in blender 4.5 5. Run the script 6. Notice the custom property does show in the Scene Properties > Custom Properties Example code comes from Blenders Api, not actual code from my addon. This is just to show simple showcase Source: https://docs.blender.org/api/current/bpy.props.html#collection-example </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze the two bug reports. First, look at the description and steps for each. Bug Report 1 is about custom properties appearing on .glb re-import when they weren't there before. The steps involve exporting to glb with custom properties included, then importing back and seeing them appear. The issue is that custom props are magically present after import. Bug Report 2 is about PointerProperties not showing under Scene Properties > Custom Properties in Blender 5.0.1, but they do show in 4.5. The steps involve opening files in different versions, running a script, and checking the UI panel. The problem here is visibility of custom properties (specifically PointerProperties) in the UI. The key differences: Report 1 is about .glb export/import causing unexpected custom props to appear, while Report 2 is about custom properties (PointerProperties) not showing in the Scene Properties panel in a specific version. The issues are different—one is about import/export behavior leading to extra props, the other is about UI visibility of existing props. So they're not the same issue. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 15.292867999999999, "duplicate_report_number": "153105" } </details>

Triager-bot commented

2026-04-13 15:52:05 +00:00

Report flagged as NOT a duplicate by LLM

Custom properties for child bones in parent-child relationships created in Blender 4.5 disappear in Blender 5.0 Beta

https://projects.blender.org/blender/blender/issues/147978

System Information
Operating system: Windows-10-10.0.26100-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 577.00 Opengl Backend

Blender Version
Broken: version: 5.0.0 Beta, branch: blender-v5.0-release, commit date: 2025-10-13 07:06, hash: d510baa4b8fc
Worked: 4.5.3

Short description of error

Define custom properties for the bone class in Blender 4.5, set values for each child bone's custom properties within the parent-child relationship, and save the .blend file. When opening this file in Blender 5.0 Beta, the child bones' custom properties are disappeared.

Exact steps for others to reproduce the error

In Blender 4.5.3 LTS, run the following script to set custom properties on parent-child bones and save the file to your home folder.

from pathlib import Path
import bpy
from bpy.types import Bone
from bpy.props import StringProperty

context = bpy.context

Bone.my_custom_string = StringProperty()

bpy.ops.object.add(type="ARMATURE", location=(0, 0, 0))
armature = context.object

bpy.ops.object.mode_set(mode="EDIT")
edit_bone1 = armature.data.edit_bones.new("bone1")
edit_bone1.head = (0, 0, 0)
edit_bone1.tail = (0, 0, 1)
edit_bone2 = armature.data.edit_bones.new("bone2")
edit_bone2.head = (1, 0, 0)
edit_bone2.tail = (1, 0, 1)
edit_bone2.parent = edit_bone1
bpy.ops.object.mode_set(mode="OBJECT")

bone1 = armature.data.bones["bone1"]
bone1.my_custom_string = "Hello, Bone1"
bone2 = armature.data.bones["bone2"]
bone2.my_custom_string = "Hello, Bone2"

bpy.ops.wm.save_as_mainfile(
    filepath=str(Path.home() / "bone_props_migration_debug_20251013.blend")
)

Running the following script in Blender 5.0 opens the file saved in the home folder and confirms that the child bones' custom properties are missing.

from pathlib import Path
import bpy
from bpy.types import Bone
from bpy.props import StringProperty

Bone.my_custom_string = StringProperty()

bpy.ops.wm.open_mainfile(
    filepath=str(Path.home() / "bone_props_migration_debug_20251013.blend")
)
armature_data = bpy.data.armatures[0]
print("bone1: <" + armature_data.bones["bone1"].my_custom_string + ">")
print("bone2: <" + armature_data.bones["bone2"].my_custom_string + ">")

expected output:

bone1: <Hello, Bone1>
bone2: <Hello, Bone2>

actual output:

bone1: <Hello, Bone1>
bone2: <>

LLM Reasoning

Got it, let's analyze the two bug reports. First, look at the descriptions and steps to reproduce.

Bug report 1 is about custom properties appearing on .glb re-import when they weren't there during export. The issue is with exporting to glb and then importing back—properties show up that weren't visible before. The steps involve exporting a .blend to .glb (with custom props included) and re-importing, seeing unexpected props.

Bug report 2 is about custom properties on child bones disappearing when opening in Blender 5.0 Beta compared to 4.5.3. The steps are creating custom props on parent-child bones in 4.5.3, saving, then opening in 5.0 and checking—child bone props are missing.

The key here is the nature of the issue: report 1 is about glb export/import causing unexpected properties to appear, while report 2 is about child bone custom props disappearing during version migration (4.5 to 5.0). These are different scenarios—one involves file format export/import, the other involves version compatibility with armature bones' custom props. So they're not the same issue.

JSON Data

{
"llm_judgement": false,
"processing_time": 17.371284,
"duplicate_report_number": "147978"
}

### Report flagged as NOT a duplicate by LLM <details> <summary>Custom properties for child bones in parent-child relationships created in Blender 4.5 disappear in Blender 5.0 Beta</summary> https://projects.blender.org/blender/blender/issues/147978 **System Information** Operating system: Windows-10-10.0.26100-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 577.00 Opengl Backend **Blender Version** Broken: version: 5.0.0 Beta, branch: blender-v5.0-release, commit date: 2025-10-13 07:06, hash: `d510baa4b8fc` Worked: 4.5.3 **Short description of error** Define custom properties for the bone class in Blender 4.5, set values for each child bone's custom properties within the parent-child relationship, and save the .blend file. When opening this file in Blender 5.0 Beta, the child bones' custom properties are disappeared. **Exact steps for others to reproduce the error** In Blender 4.5.3 LTS, run the following script to set custom properties on parent-child bones and save the file to your home folder. ```python from pathlib import Path import bpy from bpy.types import Bone from bpy.props import StringProperty context = bpy.context Bone.my_custom_string = StringProperty() bpy.ops.object.add(type="ARMATURE", location=(0, 0, 0)) armature = context.object bpy.ops.object.mode_set(mode="EDIT") edit_bone1 = armature.data.edit_bones.new("bone1") edit_bone1.head = (0, 0, 0) edit_bone1.tail = (0, 0, 1) edit_bone2 = armature.data.edit_bones.new("bone2") edit_bone2.head = (1, 0, 0) edit_bone2.tail = (1, 0, 1) edit_bone2.parent = edit_bone1 bpy.ops.object.mode_set(mode="OBJECT") bone1 = armature.data.bones["bone1"] bone1.my_custom_string = "Hello, Bone1" bone2 = armature.data.bones["bone2"] bone2.my_custom_string = "Hello, Bone2" bpy.ops.wm.save_as_mainfile( filepath=str(Path.home() / "bone_props_migration_debug_20251013.blend") ) ``` Running the following script in Blender 5.0 opens the file saved in the home folder and confirms that the child bones' custom properties are missing. ```python from pathlib import Path import bpy from bpy.types import Bone from bpy.props import StringProperty Bone.my_custom_string = StringProperty() bpy.ops.wm.open_mainfile( filepath=str(Path.home() / "bone_props_migration_debug_20251013.blend") ) armature_data = bpy.data.armatures[0] print("bone1: <" + armature_data.bones["bone1"].my_custom_string + ">") print("bone2: <" + armature_data.bones["bone2"].my_custom_string + ">") ``` expected output: ``` bone1: <Hello, Bone1> bone2: <Hello, Bone2> ``` actual output: ``` bone1: <Hello, Bone1> bone2: <> ``` </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze the two bug reports. First, look at the descriptions and steps to reproduce. Bug report 1 is about custom properties appearing on .glb re-import when they weren't there during export. The issue is with exporting to glb and then importing back—properties show up that weren't visible before. The steps involve exporting a .blend to .glb (with custom props included) and re-importing, seeing unexpected props. Bug report 2 is about custom properties on child bones disappearing when opening in Blender 5.0 Beta compared to 4.5.3. The steps are creating custom props on parent-child bones in 4.5.3, saving, then opening in 5.0 and checking—child bone props are missing. The key here is the nature of the issue: report 1 is about glb export/import causing unexpected properties to appear, while report 2 is about child bone custom props disappearing during version migration (4.5 to 5.0). These are different scenarios—one involves file format export/import, the other involves version compatibility with armature bones' custom props. So they're not the same issue. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 17.371284, "duplicate_report_number": "147978" } </details>

Triager-bot commented

2026-04-13 15:52:18 +00:00

Report flagged as NOT a duplicate by LLM

Import/Export FBX - Animated Custom properties

https://projects.blender.org/blender/blender/issues/105074

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98

Blender Version
Broken: version: 3.4.0, branch: blender-v3.4-release, commit date: 2022-12-06 18:46, hash: rBa95bf1ac01be
Worked: (newest version of Blender that worked as expected)

Short description of error
The FBX importer/exporter does not import/export the animated custom properties, nor the visibility of the objects.

Exact steps for others to reproduce the error
For example, if I export to FBX from blender and import it back into blender, the custom property appears but not the animation. The same thing if I import an FBX generated in Maya, the custom property appears but not its animation.
From Unity the custom properties of a file generated in blender do not appear either.
So I understand there is a problem with importing and exporting animated custom properties to FBX. And the same with the visibility property.

I'm attaching a blender file with an animated cube and with an animated custom property and animated visibility.

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the key sections: description and steps to reproduce.

Bug report 1 is about .glb export where custom properties appear on re-import that weren't there before. The steps involve exporting a .blend to .glb with custom properties included, then importing back and seeing unexpected props.

Bug report 2 is about FBX import/export not handling animated custom properties or visibility. Steps include exporting/importing FBX (Blender to Blender, Maya to Blender, Unity) and noticing animation of custom props isn't preserved.

The issues are different: one is .glb with unexpected custom props appearing, the other is FBX failing to export/import animated custom props. The file formats and specific problems (unexpected presence vs. missing animation) are distinct. So they're not the same issue.

JSON Data

{
"llm_judgement": false,
"processing_time": 12.531688,
"duplicate_report_number": "105074"
}

### Report flagged as NOT a duplicate by LLM <details> <summary>Import/Export FBX - Animated Custom properties</summary> https://projects.blender.org/blender/blender/issues/105074 **System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98 **Blender Version** Broken: version: 3.4.0, branch: blender-v3.4-release, commit date: 2022-12-06 18:46, hash: `rBa95bf1ac01be` Worked: (newest version of Blender that worked as expected) **Short description of error** The FBX importer/exporter does not import/export the animated custom properties, nor the visibility of the objects. **Exact steps for others to reproduce the error** For example, if I export to FBX from blender and import it back into blender, the custom property appears but not the animation. The same thing if I import an FBX generated in Maya, the custom property appears but not its animation. From Unity the custom properties of a file generated in blender do not appear either. So I understand there is a problem with importing and exporting animated custom properties to FBX. And the same with the visibility property. I'm attaching a blender file with an animated cube and with an animated custom property and animated visibility. </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the key sections: description and steps to reproduce. Bug report 1 is about .glb export where custom properties appear on re-import that weren't there before. The steps involve exporting a .blend to .glb with custom properties included, then importing back and seeing unexpected props. Bug report 2 is about FBX import/export not handling animated custom properties or visibility. Steps include exporting/importing FBX (Blender to Blender, Maya to Blender, Unity) and noticing animation of custom props isn't preserved. The issues are different: one is .glb with unexpected custom props appearing, the other is FBX failing to export/import animated custom props. The file formats and specific problems (unexpected presence vs. missing animation) are distinct. So they're not the same issue. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 12.531688, "duplicate_report_number": "105074" } </details>

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Triager-bot/blender-bug-reports#77