Export .FBX with Cycles Render Engine #45126
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#45126
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Windows 8.1 , graphic card Nvidia GTS250
Blender Version
2.74 000dfc0
Blender on Cycles Render Engine cannot export FBX files with user assigned material color information - as diffuse/glossy/emission nor assigned images textures. Objects get imported grey. Tested on two different software packages.
Works (though not perfectly) with Blender Render Engine. I wish it would work with Cycles too. At least if simple nodes would work for the important shaders: diffuse, glossy-specular, emissive, and ambient occlusion) and the attached image texture of the model, it will be great also.
Changed status to: 'Open'
Added subscriber: @AlexDoso
maybe an upgrade of the plugin to ASCII 7.5.0. could export materials properly ?
I saw that 3Ds max 2016 exports 7.5.0 ascii files now.
Added subscriber: @mont29
Changed status from 'Open' to: 'Archived'
Thanks for the report, but this is a feature request, which is not accepted on this tracker. Further more, supporting the conversion of a complex nodal shading system to the very limited shading of FBX is practically impossible (outside of some very simple and limited cases), and not considered as a goal currently.
I imported a model from 3ds max to blender in Cycles Engine and the materials imported with the same colour and applied texture (fbx binary). I am wondering why doesn't it work the other way around ?
Converting simple (static pipeline) shading to nodal one is rather simple and straightforward, the reversed operation is… hairy.
I wish the FBX export plugin at least could convert out of Cycles simple materials to have a diffuse, a glossy, an ambient occlusion, and an emitter node - as this is the information than can be transferred via FBX between software
And not forget a single attached texture to be able to export and that would be just fine and workable. Curently Cycles export no information of the material of the model.
Can this be done?
Even though I have no coding (nor Python) skills I wanna do it myself, but i need some guidance since I don't know what code to modify. So please help :)