FBX material export issues #53209

New Issue

Juri Unt · 2017-10-31T08:51:48+01:00

Juri Unt commented

2017-10-31 08:51:48 +01:00

While Render Engine is set to Cycles, Regardless of Material color or Viewport Color of the material, Materials do not export with Color information (FBX). They will only export if material "use_nodes" is set False. To do that artists needs to switch to Blender Render. It's very clunky and unpredictable workflow.
While exporting FBX Materials when use_nodes is enabled, GAMMA is not taken into account (2.2 needs to be applied). As a result target software loads it Darker.

Why is this important? When working with Game assets, colored materials are assigned to parts of highpoly mesh that is then baked onto LowPoly where Material colors become ID Masks (please google for more examples). 1) makes this task of exporting materials very clunky, wasteful, confusing and disappointing when bakes show blank. 2) creates very DARK materials which are very hard to color key and share in production between applications.

To summarize. Please consider small tweak to .fbx exporter to carry material color information regardless of render engine (e.g if Cycles, viewport_color should be exported). Also please apply Gamma fix (e.g obj.active_material.diffuse_color- [x] = math.pow(obj.active_material.diffuse_color- [x],1/2.2) )

B 2.79.

Thank You

1) While Render Engine is set to Cycles, Regardless of Material color or Viewport Color of the material, Materials do not export with Color information (FBX). They will only export if material "use_nodes" is set False. To do that artists needs to switch to Blender Render. It's very clunky and unpredictable workflow. 2) While exporting FBX Materials when use_nodes is enabled, GAMMA is not taken into account (2.2 needs to be applied). As a result target software loads it Darker. ![gamma_bug.png](https://archive.blender.org/developer/F1079022/gamma_bug.png) Why is this important? When working with Game assets, colored materials are assigned to parts of highpoly mesh that is then baked onto LowPoly where Material colors become [ID Masks ](https://support.allegorithmic.com/documentation/display/SD5/Color+Map+from+Mesh) (please google for more examples). 1) makes this task of exporting materials very clunky, wasteful, confusing and disappointing when bakes show blank. 2) creates very DARK materials which are very hard to color key and share in production between applications. To summarize. Please consider small tweak to .fbx exporter to carry material color information regardless of render engine (e.g if Cycles, viewport_color should be exported). Also please apply Gamma fix (e.g obj.active_material.diffuse_color- [x] = math.pow(obj.active_material.diffuse_color- [x],1/2.2) ) B 2.79. Thank You

Juri Unt commented

2017-10-31 08:51:48 +01:00

Changed status to: 'Open'

Juri Unt commented

2017-10-31 08:51:48 +01:00

Added subscriber: @JuriUnt

blender-admin commented

2017-10-31 08:51:48 +01:00

blender/blender-addons#93174 was marked as duplicate of this issue

Sergey Sharybin commented

2017-10-31 10:13:46 +01:00

Added subscribers: @mont29, @Sergey

Bastien Montagne was assigned by Sergey Sharybin

2017-10-31 10:13:46 +01:00

Sergey Sharybin commented

2017-10-31 10:13:46 +01:00

Please always attach .blend file to demonstrate the issue.

@mont29, is it enough information for you to do some bugfix already?

Please always attach .blend file to demonstrate the issue. @mont29, is it enough information for you to do some bugfix already?

Juri Unt commented

2017-10-31 10:45:23 +01:00

Blend file with embedded description attached fbx_materials_export.blend

To replicate issue of missing colors just export as .fbx, reimport it in Blender - all colors will be blank.
To replicate issue with Gamma, export fbx with materials (use_nodes=False), import in Maya/Max or some other program to see the issue ( Blender imports its own FBX correctly as well as FBX of other software)

Blend file with embedded description attached [fbx_materials_export.blend](https://archive.blender.org/developer/F1079193/fbx_materials_export.blend) - To replicate issue of missing colors just export as .fbx, reimport it in Blender - all colors will be blank. - To replicate issue with Gamma, export fbx with materials (use_nodes=False), import in Maya/Max or some other program to see the issue ( Blender imports its own FBX correctly as well as FBX of other software)

Bastien Montagne commented

2017-10-31 11:37:08 +01:00

Technically, this is not a bug at all, we have absolutely no Cycles material support at all in FBX exporter… So that’s a feature request. ;)

We could use that viewport_color as diffuse one for Cycles materials, this one would sound like a reasonable hack, but… I don’t think we have any such thing currently??? Cycles seems to just use the regular diffuse color of the material in solid view, afaict.

Colors space is another topic, quoting official docs, « The FBX file format does not support Color space information. » And going to screen space from linear one by a mere 'random' gamma correction is not the way to go here anyway, that would have to be applied to all colors (not to mention other 'magic' conversions that could break…). That sounds like a whole big fat TODO topic that would need serious investigation first etc. Totally outside of bug tracker scope am afraid.

Technically, this is not a bug at all, we have absolutely no Cycles material support at all in FBX exporter… So that’s a feature request. ;) We could use that `viewport_color` as diffuse one for Cycles materials, this one would sound like a reasonable hack, but… I don’t think we have any such thing currently??? Cycles seems to just use the regular diffuse color of the material in solid view, afaict. Colors space is another topic, quoting [official docs](https://knowledge.autodesk.com/support/maya/learn-explore/caas/CloudHelp/cloudhelp/2016/ENU/Maya/files/GUID-AA3B8EA4-DDFB-4B0F-9654-2BF6B8781AE7-htm.html), « The FBX file format does not support Color space information. » And going to screen space from linear one by a mere 'random' gamma correction is not the way to go here anyway, that would have to be applied to all colors (not to mention other 'magic' conversions that could break…). That sounds like a whole big fat TODO topic that would need serious investigation first etc. Totally outside of bug tracker scope am afraid.

Juri Unt commented

2017-10-31 14:50:37 +01:00

Thank You for the insight!

viewport_color - Cycles seems to use viewport_color, not anything from nodes ( http://cgstrive.com/SS/2_10312017_83db.png ). So having this referenced upon export would already be a victory.
gamma/color space - In production max<->maya<->substance painter/designer transfer colors among one another identically. I suspect some issue with way Blender deals with it (bug?). I resolved my problem with pow(color, 1/2.2) matching Maya, Max as expected using custom python based export routine. Color IDs play pivotal role in texturing pipeline (SP, SD) so having them near black is a bit of an issue for artist using Blender in gamedev pipeline.

I hoped it would be an easy, fast fix. Certainly not a priority. I understand there are more urgent things to do, just thought might be worth noting. Thank You!

Thank You for the insight! - viewport_color - Cycles seems to use viewport_color, not anything from nodes ( http://cgstrive.com/SS/2_10312017_83db.png ). So having this referenced upon export would already be a victory. - gamma/color space - In production max<->maya<->substance painter/designer transfer colors among one another **identically**. I suspect some issue with way Blender deals with it (bug?). I resolved my problem with pow(color, 1/2.2) matching Maya, Max as expected using custom python based export routine. Color IDs play pivotal role in texturing pipeline (SP, SD) so having them near black is a bit of an issue for artist using Blender in gamedev pipeline. I hoped it would be an easy, fast fix. Certainly not a priority. I understand there are more urgent things to do, just thought might be worth noting. Thank You!

Bastien Montagne commented

2017-10-31 15:14:50 +01:00

Ah ok, so 'viewport color' is actually just the regular diffuse color from materials… that I can add, remaining will be considered as TODO.

blender-admin commented

2017-10-31 15:24:57 +01:00

This issue was referenced by blender/blender-addons@3e29cb17a7

This issue was referenced by blender/blender-addons@3e29cb17a7a0964259b44e5053c7ae925d2874ec

Bastien Montagne commented

2017-10-31 15:26:52 +01:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2017-10-31 15:26:52 +01:00

Linda Capito commented

2019-07-05 08:42:29 +02:00

Added subscriber: @lijecaru

Linda Capito commented

2019-07-05 08:42:29 +02:00

Hello, any news regarding development to export .fbx from cycles render? I found a post from 2015 also asking for this feature. Is there a workaround?

Omar Emara commented

2022-03-08 11:29:47 +01:00

Added subscriber: @herbst

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 material export issues #53209