Weighted/Hardened normals not applied when exporting FBX #64743

Closed
opened 2019-05-17 05:29:05 +02:00 by John Porter · 7 comments

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.01

Blender Version
Broken: version: 2.80 (sub 68), branch: master, commit date: 2019-05-16 17:17, hash: blender/blender@3076544c8c

Short description of error
When exporting to FBX, weighted normals or hardened normals in modifiers are not applied.

Exact steps for others to reproduce the error

  1. Open this file which contains a cube with a bevel and weighted normal modifier on it.
    apply_modifier_export_bug.blend

  2. Export to fbx, keeping the "Apply Modifiers" checkbox on.

  3. Import the previously exported file and note that the custom normals are no longer there.

  4. Manually apply the modifiers in the stack and then export/import. Note that the normals are correctly preserved.

Note- I also tried this with .obj and it works correctly. Other formats untested.

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.01 **Blender Version** Broken: version: 2.80 (sub 68), branch: master, commit date: 2019-05-16 17:17, hash: `blender/blender@3076544c8c` **Short description of error** When exporting to FBX, weighted normals or hardened normals in modifiers are not applied. **Exact steps for others to reproduce the error** 1) Open this file which contains a cube with a bevel and weighted normal modifier on it. [apply_modifier_export_bug.blend](https://archive.blender.org/developer/F7042384/apply_modifier_export_bug.blend) 2) Export to fbx, keeping the "Apply Modifiers" checkbox on. 3) Import the previously exported file and note that the custom normals are no longer there. 4) Manually apply the modifiers in the stack and then export/import. Note that the normals are correctly preserved. Note- I also tried this with .obj and it works correctly. Other formats untested.
Author

Added subscriber: @John-Porter

Added subscriber: @John-Porter

blender/blender#64744 was marked as duplicate of this issue

blender/blender#64744 was marked as duplicate of this issue

Added subscribers: @MassimilianoPuliero, @Gvgeo-1

Added subscribers: @MassimilianoPuliero, @Gvgeo-1

blender/blender#64744 is same problem with modifiers, for sharp edges.

blender/blender#64744 is same problem with modifiers, for sharp edges.
Bastien Montagne was assigned by Brecht Van Lommel 2019-05-21 11:30:33 +02:00

I cannot reproduce this with current blender… This has probably been fixed in past days (along with other general object-to-mesh changes & fixes)?

I cannot reproduce this with current blender… This has probably been fixed in past days (along with other general object-to-mesh changes & fixes)?

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

Works fine now.

Works fine now.
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#64743
No description provided.