Blender 3.5 FBX fails to export materials on GN objects #106317

New Issue

Ludvik Koutny · 2023-03-30T16:07:11+02:00

Ludvik Koutny commented

2023-03-30 16:07:11 +02:00

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41

Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b
Worked: (newest version of Blender that worked as expected)

Short description of error
Blender FBX 3.5 fails to export materials on GN objects

Exact steps for others to reproduce the error

Open the attached .blend file
Select ExportCubes object and export it in the FBX file format
Import the ExportCubes FBX back into Blender
Result: Assigned materials are missing and the imported object has no material slots
Expected: The imported object contains the material slots which were supposed to be exported.

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41 **Blender Version** Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: `1be25cfff18b` Worked: (newest version of Blender that worked as expected) **Short description of error** Blender FBX 3.5 fails to export materials on GN objects **Exact steps for others to reproduce the error** 1. Open the attached .blend file 2. Select ExportCubes object and export it in the FBX file format 3. Import the ExportCubes FBX back into Blender Result: Assigned materials are missing and the imported object has no material slots Expected: The imported object contains the material slots which were supposed to be exported.

FBXMaterialExportBug.blend

751 KiB

Ludvik Koutny added the

labels 2023-03-30 16:07:12 +02:00

Pratik Borhade commented

2023-03-31 07:35:33 +02:00

hi, please move this report to add-ons repository: https://projects.blender.org/blender/blender-addons/issues

Pratik Borhade closed this issue

2023-03-31 07:35:39 +02:00

Blender Bot added

and removed

labels 2023-03-31 07:35:40 +02:00

Ludvik Koutny commented

2023-03-31 09:59:02 +02:00

hi, please move this report to add-ons repository: https://projects.blender.org/blender/blender-addons/issues

How was I supposed to know that, and how do I move the issue?

I am not experienced with Gitea yet, so I don't know how to move an issue to different repository. The Edit button only allows for change of the name.

Also, how is the user supposed to know which export formats are integral part of blender vs which ones are addons, given that I/O formats are usually something deeply tied to the core of the software in most cases.

All I did in Blender was click Help->Report a bug. On the page which opened, there is no choice to switch/select the project.

It's important to realize here that offloading responsibility to user for correctly categorizing project for things that are not clear whether they belong to core Blender or not is just not gonna work if the bug submission report form which opens when reporting a bug directly from Blender contains no information on how to determine which project the report belongs to.

For example, out of two most commonly used I/O formats, FBX is an addon, while OBJ is now a core part of Blender. You can't reasonably expect average users to be aware of those nuances and then also expect them to be familiar enough with Gitea UI to be able to move the issues themselves if they create them in a wrong project.

> hi, please move this report to add-ons repository: https://projects.blender.org/blender/blender-addons/issues How was I supposed to know that, and how do I move the issue? I am not experienced with Gitea yet, so I don't know how to move an issue to different repository. The Edit button only allows for change of the name. Also, how is the user supposed to know which export formats are integral part of blender vs which ones are addons, given that I/O formats are usually something deeply tied to the core of the software in most cases. All I did in Blender was click Help->Report a bug. On the page which opened, there is no choice to switch/select the project. It's important to realize here that offloading responsibility to user for correctly categorizing project for things that are not clear whether they belong to core Blender or not is just not gonna work if the bug submission report form which opens when reporting a bug directly from Blender contains no information on how to determine which project the report belongs to. For example, out of two most commonly used I/O formats, FBX is an addon, while OBJ is now a core part of Blender. You can't reasonably expect average users to be aware of those nuances and then also expect them to be familiar enough with Gitea UI to be able to move the issues themselves if they create them in a wrong project.

Ludvik Koutny reopened this issue

2023-03-31 09:59:04 +02:00

Blender Bot added

and removed

labels 2023-03-31 09:59:05 +02:00

Pratik Borhade commented

2023-03-31 11:45:07 +02:00

why did you close the report waiting for me to move it instead of moving it yourself?

Ok, submitted a new report: blender/blender-addons#104516

I am not experienced with Gitea yet, so I don't know how to move an issue to different repository. The Edit button only allows for change of the name.

There is no easy way so far. Always a new report need to be submitted. see: gitea feature request

Also, how is the user supposed to know which export formats are integral part of blender vs which ones are addons,

I agree its bit difficult for reporters to differentiate between bugs of vanilla blender and add-on.

It's important to realize here that offloading responsibility to user for correctly categorizing project for things that are not clear whether they belong to core Blender or not
is just not gonna work if the bug submission report form which opens when reporting a bug directly from Blender contains no information on how to determine which project the report belongs to.

This can be improved in future (Roughly a month or two since we moved to Gitea).
Earlier, all reports were part of single list so it was easy for triagers and users to move reports by just changing the tags (BF blender -> addon)

> why did you close the report waiting for me to move it instead of moving it yourself? Ok, submitted a new report: https://projects.blender.org/blender/blender-addons/issues/104516 > I am not experienced with Gitea yet, so I don't know how to move an issue to different repository. The Edit button only allows for change of the name. There is no easy way so far. Always a new report need to be submitted. see: [gitea feature request](https://projects.blender.org/infrastructure/blender-projects-platform/issues/12#:~:text=Can%27t%20move%20reports%20across%20repos%2C%20in%20particular%20between%20blender%2C%20addons%20and%20documentation.%20(wait%20and%20see%20how%20important%2C%20especially%20with%20upcoming%20extensions%20platform)) > Also, how is the user supposed to know which export formats are integral part of blender vs which ones are addons, I agree its bit difficult for reporters to differentiate between bugs of vanilla blender and add-on. > It's important to realize here that offloading responsibility to user for correctly categorizing project for things that are not clear whether they belong to core Blender or not is just not gonna work if the bug submission report form which opens when reporting a bug directly from Blender contains no information on how to determine which project the report belongs to. This can be improved in future (Roughly a month or two since we moved to Gitea). Earlier, all reports were part of single list so it was easy for triagers and users to move reports by just changing the tags (`BF blender -> addon`)

Ludvik Koutny commented

2023-03-31 11:46:48 +02:00

why did you close the report waiting for me to move it instead of moving it yourself?

Ok, submitted a new report: blender/blender-addons#104516

I am not experienced with Gitea yet, so I don't know how to move an issue to different repository. The Edit button only allows for change of the name.

There is no easy way so far. Always a new report need to be submitted. see: gitea feature request

Also, how is the user supposed to know which export formats are integral part of blender vs which ones are addons,

I agree its bit difficult for reporters to differentiate between bugs of vanilla blender and add-on.

It's important to realize here that offloading responsibility to user for correctly categorizing project for things that are not clear whether they belong to core Blender or not
is just not gonna work if the bug submission report form which opens when reporting a bug directly from Blender contains no information on how to determine which project the report belongs to.

This can be improved in future (Roughly a month or two since we moved to Gitea).
Earlier, all reports were part of single list so it was easy for triagers and users to move reports by just changing the tags (BF blender -> addon)

Oh, so I misunderstood. When you said move, I assumed there was a some way to move it. So by moving you meant simply creating a new one. I will try to remember that.

> > why did you close the report waiting for me to move it instead of moving it yourself? > > Ok, submitted a new report: https://projects.blender.org/blender/blender-addons/issues/104516 > > > I am not experienced with Gitea yet, so I don't know how to move an issue to different repository. The Edit button only allows for change of the name. > > There is no easy way so far. Always a new report need to be submitted. see: [gitea feature request](https://projects.blender.org/infrastructure/blender-projects-platform/issues/12#:~:text=Can%27t%20move%20reports%20across%20repos%2C%20in%20particular%20between%20blender%2C%20addons%20and%20documentation.%20(wait%20and%20see%20how%20important%2C%20especially%20with%20upcoming%20extensions%20platform)) > > > Also, how is the user supposed to know which export formats are integral part of blender vs which ones are addons, > > I agree its bit difficult for reporters to differentiate between bugs of vanilla blender and add-on. > > > It's important to realize here that offloading responsibility to user for correctly categorizing project for things that are not clear whether they belong to core Blender or not > is just not gonna work if the bug submission report form which opens when reporting a bug directly from Blender contains no information on how to determine which project the report belongs to. > > This can be improved in future (Roughly a month or two since we moved to Gitea). > Earlier, all reports were part of single list so it was easy for triagers and users to move reports by just changing the tags (`BF blender -> addon`) Oh, so I misunderstood. When you said move, I assumed there was a some way to move it. So by moving you meant simply creating a new one. I will try to remember that.

Pratik Borhade commented

2023-04-01 05:43:00 +02:00

That's fine. Will close this report.

Pratik Borhade closed this issue

2023-04-01 05:43:02 +02:00

Blender Bot added

and removed

labels 2023-04-01 05:43:03 +02:00