Scaling in edit mode with individual origins and snapping activated is broken #46505

Open
opened 7 years ago by bliblubli · 7 comments

System Information
Win7 x64

Blender Version
Broken: 2.76

Short description of error
Following #39161. Scaling in edit mode works well with "median" as pivot point but with "individual origins" it breaks.

Exact steps for others to reproduce the error

In attached file:
Scale and choose a vertex with "ctrl" pressed, cube seems to disappear.
To compare, press "G" and choose a vertex for snap, the cube's center is moved as a cube (also individual origins could make all selected verts move to that position making a point instead of a cube?) to that vertex.
Scale with "median" as pivot, it works
bug scale individual origins.blend

So maybe to make it consistent, make "individual origins behave like median.

**System Information** Win7 x64 **Blender Version** Broken: 2.76 **Short description of error** Following #39161. Scaling in edit mode works well with "median" as pivot point but with "individual origins" it breaks. **Exact steps for others to reproduce the error** In attached file: Scale and choose a vertex with "ctrl" pressed, cube seems to disappear. To compare, press "G" and choose a vertex for snap, the cube's center is moved as a cube (also individual origins could make all selected verts move to that position making a point instead of a cube?) to that vertex. Scale with "median" as pivot, it works [bug scale individual origins.blend](https://archive.blender.org/developer/F228656/bug_scale_individual_origins.blend) So maybe to make it consistent, make "individual origins behave like median.
Poster

Changed status to: 'Open'

Changed status to: 'Open'
Poster

Added subscriber: @bliblubli

Added subscriber: @bliblubli
ideasman42 self-assigned this 7 years ago
Owner

Note that this was never supported and while we can support - it will take a bit of work to do it efficiently. Since we probably dont want to calculate this value for every element when its only going to be used in a specific case.

Note that this was never supported and while we can support - it will take a bit of work to do it efficiently. Since we probably dont want to calculate this value for every element when its only going to be used in a specific case.
Poster

well, don't loose your time finding a real solution for this one until someone comes with a real use case for it. But in the mean time, making it behave like in the " median" case instead of making it disappear would help.

I found another but by the way. When you scale on x,y (with shift+z), it seems the algorithm takes the z component into account also it is not used.
Step to reproduce:

  • Open this file: bug scale closest x y.blend
    In the left perspective view:
  • Press S
  • Press shift+Z
  • Hold ctrl to snap and hover the bottom right vertex of the other cube.
    Look on the right top view, the cube is not scaled up to the chosen point. Doing the same with grabbing instead of scaling works.

I can open another bug report if you want.

well, don't loose your time finding a real solution for this one until someone comes with a real use case for it. But in the mean time, making it behave like in the " median" case instead of making it disappear would help. I found another but by the way. When you scale on x,y (with shift+z), it seems the algorithm takes the z component into account also it is not used. Step to reproduce: - Open this file: [bug scale closest x y.blend](https://archive.blender.org/developer/F245926/bug_scale_closest_x_y.blend) In the left perspective view: - Press S - Press shift+Z - Hold ctrl to snap and hover the bottom right vertex of the other cube. Look on the right top view, the cube is not scaled up to the chosen point. Doing the same with grabbing instead of scaling works. I can open another bug report if you want.
Collaborator

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Collaborator

Setting this as Todo, seems this is just not supported yet (leaving it open though, so Campbell doesn't forget about it ;) ).

Setting this as Todo, seems this is just not supported yet (leaving it open though, so Campbell doesn't forget about it ;) ).
ideasman42 removed their assignment 7 years ago
Owner

Added subscriber: @ideasman42

Added subscriber: @ideasman42
mano-wii was assigned by Blendify 6 years ago
lichtwerk removed the
legacy module/Modeling
label 1 day ago
lichtwerk removed the
Interest/Modeling
label 1 day ago
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#46505
Loading…
There is no content yet.