Active Element Scales from last active face position if no active vert #121135

Open
opened 2024-04-26 16:50:42 +02:00 by Daniel Gryningstjerna · 7 comments

Blender Version
Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: 40a5e739e270

Short description of error
If no active vert is selected and active element is on, it will scale from a completely random and nonsensical position instead of doing it from the median point of the selected in some cases.

This only happens sometimes on some meshes, most of the time it works correctly.
image
Wrong:
Wrong
Correct:
Correct
Exact steps for others to reproduce the error

  1. Select the inner circle and scale it using S (from the attached .blend)
  2. Notice that the scale position is scales from is completely random and not reflective of the current selection.
  3. Now try make the circle just a plane like in the correct .gif and notice that it correctly scales from the median like intended.
**Blender Version** Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: `40a5e739e270` **Short description of error** If no active vert is selected and active element is on, it will scale from a completely random and nonsensical position instead of doing it from the median point of the selected in some cases. This only happens sometimes on some meshes, most of the time it works correctly. ![image](/attachments/0a5c74ae-af7e-4326-9dea-a3c2509ec1cf) Wrong: ![Wrong](/attachments/e0db4288-c904-4108-99b1-dfb86f8bfec9) Correct: ![Correct](/attachments/96ff89b0-8898-4c38-a278-0794d814c082) **Exact steps for others to reproduce the error** 1. Select the inner circle and scale it using S (from the attached .blend) 2. Notice that the scale position is scales from is completely random and not reflective of the current selection. 3. Now try make the circle just a plane like in the correct .gif and notice that it correctly scales from the median like intended.
Daniel Gryningstjerna added the
Status
Needs Triage
Priority
Normal
Type
Report
labels 2024-04-26 16:50:43 +02:00

I can confirm this behavior. After switching Select Mode from face to edge or vertex, the pivot point seems to be at the last selected face when all vertices/edges of that last active face are selected.

I can confirm this behavior. After switching `Select Mode` from face to edge or vertex, the pivot point seems to be at the last selected face when all vertices/edges of that last active face are selected.

I can confirm this behavior. After switching Select Mode from face to edge or vertex, the pivot point seems to be at the last selected face when all vertices/edges of that last active face are selected.

Thanks, but there is literally nothing that indicates or explains it in the UI or viewport, it's just super confusing behavior to be frank. It should just scale to the median point in all casese if no active vertex is selected, like it does most of the time.

> I can confirm this behavior. After switching `Select Mode` from face to edge or vertex, the pivot point seems to be at the last selected face when all vertices/edges of that last active face are selected. Thanks, but there is literally nothing that indicates or explains it in the UI or viewport, it's just super confusing behavior to be frank. It should just scale to the median point in all casese if no active vertex is selected, like it does most of the time.

I also think that this is unexpected behavior, but what if you want to scale (or rotate) vertices/edges to the center of the active face? Selecting the face as active and then choosing the vertices to scale would be the only way to do that.

Maybe it's best to have the active element visible regardless of select mode? Or should this happen only when the pivot point is active element?

Or maybe the active element should depend on the current select mode, like you said. Faces can only be the active element in face select mode, edges can only be active element in edge select mode etc.

This is probably a UI issue and a modeling issue. Has it always been this way or is this a regression?

I also think that this is unexpected behavior, but what if you want to scale (or rotate) vertices/edges to the center of the active face? Selecting the face as active and then choosing the vertices to scale would be the only way to do that. Maybe it's best to have the active element visible regardless of select mode? Or should this happen only when the pivot point is active element? Or maybe the active element should depend on the current select mode, like you said. Faces can only be the active element in face select mode, edges can only be active element in edge select mode etc. This is probably a UI issue and a modeling issue. Has it always been this way or is this a regression?

Can you confirm that the following line is true, and the pivot point is not random?

The pivot point seems to be at the last selected face when all vertices/edges of that last active face are selected.

Can you confirm that the following line is true, and the pivot point is not random? > The pivot point seems to be at the last selected face when all vertices/edges of that last active face are selected.

Can you confirm that the following line is true, and the pivot point is not random?

I do not think the pivot point is random, but it feels random to the user since there is zero indication in the view-port or UI that the pivot has been changde from median point to another location.

> Can you confirm that the following line is true, and the pivot point is not random? > I do not think the pivot point is random, but it feels random to the user since there is zero indication in the view-port or UI that the pivot has been changde from median point to another location.
Member

Hi, thanks for the report. Can confirm.

The pivot point seems to be at the last selected face when all vertices/edges of that last active face are selected.

seems so.

Hi, thanks for the report. Can confirm. > The pivot point seems to be at the last selected face when all vertices/edges of that last active face are selected. seems so.
Pratik Borhade added
Module
Modeling
Status
Confirmed
and removed
Status
Needs Triage
labels 2024-05-07 08:01:12 +02:00
Member

As pointed out, this is not random, it just uses the , see calc_active_center_for_editmode / BM_select_history_active_get which falls back to the active face.

So in a way, code works as intended (though a bit unintuitive -- and could use the median as fallback as mentioned, which seems to make more sense, agreed)

As pointed out, this is not random, it just uses the , see `calc_active_center_for_editmode` / `BM_select_history_active_get` which falls back to the active face. So in a way, code works as intended (though a bit unintuitive -- and could use the median as fallback as mentioned, which seems to make more sense, agreed)
Philipp Oeser changed title from Active Element Scales from random position if no active vert in some cases to Active Element Scales from last active face position if no active vert 2024-05-07 09:21:32 +02:00
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
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#121135
No description provided.