Extrude and Move on Normals does not move vertices or edges on normals #57681

Closed
opened 2018-11-07 20:40:08 +01:00 by Martynas Žiemys · 7 comments

System Information
Windows 10 Pro, GTX 970

Blender Version
Broken: 2.79b f4dc9f9d68, 2.80 Alpha2 2018-11-02 c4c62e6df5 also various 2.79 daily builds

Short description of error
Extrude and Move on Normals does not move vertices or edges on normals as the label of the operator suggests and also changes the normals of vertices and edges extruded making it a hard job to extrude and move vertices or edges on their original normals.

Exact steps for others to reproduce the error

  1. Start Blender

  2. Add a monkey

  3. Enter Edit mode

  4. Select any edge or vertex

  5. Hit space and type 'Extrude and Move on Normals' or hit E.

  6. If vertex normal display is enabled in the n panel it can be seen that the normals of newly extruded edges and vertices change. This is not very apparent on vertices of a cube or sphere, but on more irregular surface is well visible. The version 2.8 I checked it on does not have vertex normal display but if vertex is moved in the z direction with normal transform orientation it moves in a different direction than a vertex extruded from it.
    image.png

**System Information** Windows 10 Pro, GTX 970 **Blender Version** Broken: 2.79b f4dc9f9d68b, 2.80 Alpha2 2018-11-02 c4c62e6df55 also various 2.79 daily builds **Short description of error** Extrude and Move on Normals does not move vertices or edges on normals as the label of the operator suggests and also changes the normals of vertices and edges extruded making it a hard job to extrude and move vertices or edges on their original normals. **Exact steps for others to reproduce the error** 1. Start Blender 2. Add a monkey 3. Enter Edit mode 4. Select any edge or vertex 5. Hit space and type 'Extrude and Move on Normals' or hit E. 6. If vertex normal display is enabled in the n panel it can be seen that the normals of newly extruded edges and vertices change. This is not very apparent on vertices of a cube or sphere, but on more irregular surface is well visible. The version 2.8 I checked it on does not have vertex normal display but if vertex is moved in the z direction with normal transform orientation it moves in a different direction than a vertex extruded from it. ![image.png](https://archive.blender.org/developer/F5429310/image.png)

Added subscriber: @MartinZ

Added subscriber: @MartinZ
Member

Added subscribers: @brecht, @lichtwerk

Added subscribers: @brecht, @lichtwerk
Philipp Oeser self-assigned this 2018-11-08 14:10:17 +01:00
Member

In blender 2.8 you can find the normal display in Overlays.

Regarding the "Vert-Or-Edge-Only" issue:
For mesh elements without face data, it seems normals are just computed to point away from the object origin, see
#57681.blend

So if you extrude an edge or vert only, this new element will follow this rule (yes, its normal will change -- it will just point away from the object origin).

That being said, I assume there could be room for improvement (at least in the case where we have connected edges to a vertex)?
(Saying this because it causes issues in al kinds of tools -- see #57104 for example).

I will also claim this task (same as #57104), unless @brecht already knows this is going to be a dead end (looking into improving vert normals in vert/edge-only-scenario)?

In blender 2.8 you can find the normal display in `Overlays`. Regarding the "Vert-Or-Edge-Only" issue: For mesh elements without face data, it seems normals are just computed to point away from the object origin, see [#57681.blend](https://archive.blender.org/developer/F5441703/T57681.blend) So if you extrude an edge or vert only, this new element will follow this rule (yes, its normal will change -- it will just point away from the object origin). That being said, I assume there **could** be room for improvement (at least in the case where we have connected edges to a vertex)? (Saying this because it causes issues in al kinds of tools -- see #57104 for example). I will also claim this task (same as #57104), unless @brecht already knows this is going to be a dead end (looking into improving vert normals in vert/edge-only-scenario)?
Member

sidenote: found this comment:

/* following Mesh convention; we use vertex coordinate itself for normal in this case */

If this is set in stone, I am going to leave this as is, close the report (along with #57104), but still would like to hear an opinion from someone else...

sidenote: found this comment: > /* following Mesh convention; we use vertex coordinate itself for normal in this case */ If this is set in stone, I am going to leave this as is, close the report (along with #57104), but still would like to hear an opinion from someone else...

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Extrude moves faces along face normals.

Taking into account vertex normals for vertices and edges could be useful, but that's a missing feature that would be nice to add, not a bug.

Extrude moves faces along face normals. Taking into account vertex normals for vertices and edges could be useful, but that's a missing feature that would be nice to add, not a bug.

I would mainly consider this to be a bug because the label of the operator in the search menu says 'move on normals' and then the actual functionality does not match this. Since vertices and edges could be moved on their original normals I think it would be reasonable to expect this. The other problem here is that there is no easy way to extrude edges and then move them on the original normals because of the way the normals are calculated as you pointed out. I think this would be a good reason for the operator to work according to it's label. I am no programmer but since the 'Extrude only Vertices' operator leaves the normals as originals and it is then possible to grab and move them on the original normals even though they are recalculated immediately after the operation starts, I assumed that it should not be something impossible.

I would mainly consider this to be a bug because the label of the operator in the search menu says 'move on normals' and then the actual functionality does not match this. Since vertices and edges could be moved on their original normals I think it would be reasonable to expect this. The other problem here is that there is no easy way to extrude edges and then move them on the original normals because of the way the normals are calculated as you pointed out. I think this would be a good reason for the operator to work according to it's label. I am no programmer but since the 'Extrude only Vertices' operator leaves the normals as originals and it is then possible to grab and move them on the original normals even though they are recalculated immediately after the operation starts, I assumed that it should not be something impossible.
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#57681
No description provided.