FBX lost custom vertex normals after import to 3dsMax #57673
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#57673
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 system-info.txt
Win 10 Home and graphics card Geforce 970
Blender Version
Broken: 2.79, hash: 5bd8ac9; 2.80. Alpha 2, hash:
b4dfe00fd6
Worked: none I think
Short description of error
FBX exported from both Blender 2.79 and 2.8 Alpha 2 into 3dsMax 2016+ do not preserve custom vertex normals
box_to_max.fbx
Blender
3dsMax
Exact steps for others to reproduce the error
note: importing the mesh without checked smoothing groups results in seemingly correct vertex normals and smoothnig, but reality is that the mesh has all edges as hard/flat now, the normals are just locked in correct directions (try Edit normals/reset to see it), thus there are much more vertex normals than is needed
I guess that the 3dsMax can't read the custom vertex normal and hard/soft edges correctly from the Blender FBX. The question is, what needs to be fixed? Blender exporter or Max importer?
This might be related to this bug report https://developer.blender.org/T57663
Added subscriber: @skywalger
Added subscriber: @brecht
@brecht can you look into this bug pls? You have been helpful in answering similar issue https://developer.blender.org/T57663 Probably it will be again mistake on side of 3dsMax...I just wanna be sure. Thank you.
Added subscriber: @mont29
This is one for @mont29, I don't know how custom normals work in FBX.
Changed status from 'Open' to: 'Archived'
Nobody officially knows anything about FBX, since there are no public specifications… even worse when it comes to 3DSMax and Maya, as those add their own 'FBX flavor' through custom namespaced data.
Bottom line: afaik custom normals are correctly exported from Blender (FBX has direct support for such data). What Max does with them is not really in our realm of knowledge and action. So am afraid answer will be the same as with smooth groups: that is probably something wrong on 3DSMax side, we cannot do much about it.
Thank you for explanation...I will go bother Autodesk so they fix their software...wish me good luck :D