Repeated extrusion operation doesn't respect custom transforms #53668

Closed
opened 2017-12-31 17:52:41 +01:00 by Paul J. Schrenker · 7 comments

System Information
Linux Mint 17.3, Intel graphics chipset, Dell Inspiron 15R

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Blender Edge 2.79 (Dec 30 update)

Short description of error
Repeated extrusion operations in edit mode fail to respect custom transforms. This is a bit of a workflow killer at times. This is because the transform type must be selected every single time to keep using the custom transform. If I have the user transform set to the custom, I expect it to respect that instead of switching to normal for the secondary transform operation. (If I want the normal to be the secondary, then it should be by the user's choosing. The way it is now is a bit broken.)

Exact steps for others to reproduce the error
Create some mesh in edit mode and orientate the object so it's not aligned to the usual global or local axes. Then pick an edge on it to create a custom transform. Then while the custom transform is active, do an extrusion operation elsewhere on mesh using the custom transform by double pressing one of the axis constraints. This will work as expected. However if you try to repeat the constraint, it will revert to normals for the object transformation. It will still show the setting for the custom transform, but extruding more than once fails to respect this setting.

**System Information** Linux Mint 17.3, Intel graphics chipset, Dell Inspiron 15R **Blender Version** Broken: (example: 2.69.7 4b206af, see splash screen) Blender Edge 2.79 (Dec 30 update) **Short description of error** Repeated extrusion operations in edit mode fail to respect custom transforms. This is a bit of a workflow killer at times. This is because the transform type must be selected **every single time** to keep using the custom transform. If I have the user transform set to the custom, I expect it to respect that instead of switching to normal for the secondary transform operation. (If I want the normal to be the secondary, then it should be by the user's choosing. The way it is now is a bit broken.) **Exact steps for others to reproduce the error** Create some mesh in edit mode and orientate the object so it's not aligned to the usual global or local axes. Then pick an edge on it to create a custom transform. Then while the custom transform is active, do an extrusion operation elsewhere on mesh using the custom transform by double pressing one of the axis constraints. This will work as expected. However if you try to repeat the constraint, it will revert to normals for the object transformation. It will still show the setting for the custom transform, but extruding more than once fails to respect this setting.

Added subscriber: @pauljs75

Added subscriber: @pauljs75
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Are you refering to repeat (Shift+R)? This works for me (repeated extrusions with a custom transform orientation)
As for the extruding with the E-key: yes, that defaults to switching to 'Normal + Z constrained' (which I even find reasonable - its just the mostly used for this kind of modeling operation) for the extrusion.
(You propably wouldnt just want to use the orientation that is currently set as the one for the extrusion as well. -- assuming lots of people still have 'global' set as orientation while modeling)

Maybe there's a way to do this with 'double pressing' as you say [so not toggle between 'normal' and 'global', but 'normal' and 'current/custom' while extruding]. Will have a look later, other suggestions welcome...

Are you refering to repeat (Shift+R)? This works for me (repeated extrusions with a custom transform orientation) As for the extruding with the E-key: yes, that defaults to switching to 'Normal + Z constrained' (which I even find reasonable - its just the mostly used for this kind of modeling operation) for the extrusion. (You propably wouldnt just want to use the orientation that is currently set as the one for the extrusion as well. -- assuming lots of people still have 'global' set as orientation while modeling) Maybe there's a way to do this with 'double pressing' as you say [so not toggle between 'normal' and 'global', but 'normal' and 'current/custom' while extruding]. Will have a look later, other suggestions welcome...

Single press is global as expected and usual with everything else. But I'd like to have the selected transform option be the one used for the double press. Some other operations respect it in this way, but for some stupid reason extrude doesn't. If I switch to select another face that I want to extrude on the custom transform, then I have to go back to the transforms menu and select the custom edge. It's tedious and creating an extra step that shouldn't be there. Again if I wanted the secondary constraint to be based on normal transform axes, I would have picked that from the menu. (So there shouldn't be any problem with fixing this flaw in the UI. It feels like an inconsistency.)

Also nothing against transforms menu showing "normal" as the default transforms type when starting out. But once the user picks something else, then it should stay with that until the user changes it again. Not this do it once, and then behave as if switched to normal that it does now.

Single press is global as expected and usual with everything else. But I'd like to have the selected transform option be the one used for the double press. Some other operations respect it in this way, but for some stupid reason extrude doesn't. If I switch to select another face that I want to extrude on the custom transform, then I have to go back to the transforms menu and select the custom edge. It's tedious and creating an extra step that shouldn't be there. Again if I wanted the secondary constraint to be based on normal transform axes, I would have picked that from the menu. (So there shouldn't be any problem with fixing this flaw in the UI. It feels like an inconsistency.) Also nothing against transforms menu showing "normal" as the default transforms type when starting out. But once the user picks something else, then it should stay with that until the user changes it again. Not this do it once, and then behave as if switched to normal that it does now.

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Sybren A. Stüvel self-assigned this 2020-02-04 12:20:34 +01:00

This could be seen as a feature request. In any case it's a limitation of Blender's current architecture/design, and not a bug in its implementation.

This could be seen as a feature request. In any case it's a limitation of Blender's current architecture/design, and not a bug in its implementation.
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#53668
No description provided.