Vertex-per-face normals generated by auto-smooth are not exported by collada exporter. #44900

Closed
opened 2015-05-30 23:12:35 +02:00 by Drongle McMahon · 6 comments

System: windows 7, gtx670
Blendr version: 2.74 dc15860 (and earlier) win64

Description: Vertex-per-face normals generated by auto-smooth are not exported by collada exporter.

Reproduction: File auto_smooth_export.blend: Make an 8-sided cylinder with triangle fan caps, with smooth shading, with auto-smooth active and with auto-smooth angle set to 80 degrees. This produces a smooth shaded cylinder with sharp edges around the caps. Duplicate the cylinder and name them "Source" and "Target". Add a Data Transfer modifier to "Target", using "source" as the source with evaluation in object spaces, transferring (replace) custom normals from "Nearest corner and Best Matching Face normal". Note that the vertex-per face normals displayed in the 3D view appear identical in "Target" and source both before and after adding the modifier. They are all either parallel with or perpendicular to the Z axis. Export each object separately with the Collada exporter checking only "Apply Modifier" and "Selection Only" options.

The file exported from "Source" has the smooth shading vertex normals unaffected by auto-smooth (i.e. those in the blue line vertex normal display). The file exporter from "Target" has the Vertex-per-face normals (purple lines). "Target" still has the transferred custom normals if its auto-smooth angle is set to 180 degrees. The distinction is immediately clear by inspecting the Z components of the normals, and can be visualised by importing into other software.

I don't know whether the internal representation of the "vertex-per-face normals" generated by auto-smooth is the same as that of the "custom normals" transferred by the Data Transfer modifier. Therefore I don't really know whether the fact that they are not exported is intended or is a bug. However, I did expect them to be exported, given their similar representation in the UI, and it would certainly be useful if they were. There is, however, the work-around by copying the normals from the duplicate, as illustrated here. So whether this is something that needs to be corrected or not is entirely up to the developers, depending on intent and practicability. I offer my apologies if this should be condidered as a feature request rather than as a bug.

auto_smooth_export.blend

System: windows 7, gtx670 Blendr version: 2.74 dc15860 (and earlier) win64 Description: Vertex-per-face normals generated by auto-smooth are not exported by collada exporter. Reproduction: File auto_smooth_export.blend: Make an 8-sided cylinder with triangle fan caps, with smooth shading, with auto-smooth active and with auto-smooth angle set to 80 degrees. This produces a smooth shaded cylinder with sharp edges around the caps. Duplicate the cylinder and name them "Source" and "Target". Add a Data Transfer modifier to "Target", using "source" as the source with evaluation in object spaces, transferring (replace) custom normals from "Nearest corner and Best Matching Face normal". Note that the vertex-per face normals displayed in the 3D view appear identical in "Target" and source both before and after adding the modifier. They are all either parallel with or perpendicular to the Z axis. Export each object separately with the Collada exporter checking only "Apply Modifier" and "Selection Only" options. The file exported from "Source" has the smooth shading vertex normals unaffected by auto-smooth (i.e. those in the blue line vertex normal display). The file exporter from "Target" has the Vertex-per-face normals (purple lines). "Target" still has the transferred custom normals if its auto-smooth angle is set to 180 degrees. The distinction is immediately clear by inspecting the Z components of the normals, and can be visualised by importing into other software. I don't know whether the internal representation of the "vertex-per-face normals" generated by auto-smooth is the same as that of the "custom normals" transferred by the Data Transfer modifier. Therefore I don't really know whether the fact that they are not exported is intended or is a bug. However, I did expect them to be exported, given their similar representation in the UI, and it would certainly be useful if they were. There is, however, the work-around by copying the normals from the duplicate, as illustrated here. So whether this is something that needs to be corrected or not is entirely up to the developers, depending on intent and practicability. I offer my apologies if this should be condidered as a feature request rather than as a bug. [auto_smooth_export.blend](https://archive.blender.org/developer/F182151/auto_smooth_export.blend)

Changed status to: 'Open'

Changed status to: 'Open'
Gaia Clary was assigned by Drongle McMahon 2015-05-30 23:12:35 +02:00

Added subscriber: @Drongle

Added subscriber: @Drongle
Member

Added subscriber: @Blendify

Added subscriber: @Blendify

Added subscriber: @ideasman42

Added subscriber: @ideasman42

This isn't a bug, set as TODO.

This isn't a bug, set as TODO.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sign in to join this conversation.
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
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#44900
No description provided.