Merge menu auto selects wrong location #40900

Closed
opened 2014-07-01 10:48:02 +02:00 by Robin Karlsson · 5 comments

System Information
Windows 7 64 bit
AMD Radeon HD 6970

Blender Version
Broken: Blender 2.70 and 2.71
Worked: (optional) Blender 2.69 and earlier

Short description of error
When using the merge menu Blender auto selects the last used location from when you merged last time, in earlier versions it chose methods based on how you had selected elements earlier, now it always goes with the last used location no matter what. It's not easy to properly explain what's happening, but see the steps listed below for a practical example.

I'm not sure if this is actually a bug or not (might be an intentional design choice) but I thought it worked a lot better before. I liked the older method a lot more as I very often merge at the last element, but sometimes need to select a whole loop and merge it at center, in earlier versions that never made me stop and adjust back which now lowers my modelling speed and makes Blender feel less streamlined.

Exact steps for others to reproduce the error
Steps to reproduce:

  1. Add a default cube.
  2. Select two vertices (with Shift+RMB)
  3. Merge these two at the last element and deselect them.
  4. Select two other vertices (with C [circle select] in one go).
  5. Merge these two at the center and deselect them.
  6. Select two other vertices again (with Shift+RMB).
  7. Try to merge these vertices and you'll see that Blender thinks you want to merge them at the center, even though you selected at last the last time you could.
**System Information** Windows 7 64 bit AMD Radeon HD 6970 **Blender Version** Broken: Blender 2.70 and 2.71 Worked: (optional) Blender 2.69 and earlier **Short description of error** When using the merge menu Blender auto selects the last used location from when you merged last time, in earlier versions it chose methods based on how you had selected elements earlier, now it always goes with the last used location no matter what. It's not easy to properly explain what's happening, but see the steps listed below for a practical example. I'm not sure if this is actually a bug or not (might be an intentional design choice) but I thought it worked a lot better before. I liked the older method a lot more as I very often merge at the last element, but sometimes need to select a whole loop and merge it at center, in earlier versions that never made me stop and adjust back which now lowers my modelling speed and makes Blender feel less streamlined. **Exact steps for others to reproduce the error** Steps to reproduce: 1. Add a default cube. 2. Select two vertices (with Shift+RMB) 3. Merge these two at the last element and deselect them. 4. Select two other vertices (with C [circle select] in one go). 5. Merge these two at the center and deselect them. 6. Select two other vertices again (with Shift+RMB). 7. Try to merge these vertices and you'll see that Blender thinks you want to merge them at the center, even though you selected at last the last time you could.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @RobinKarlsson

Added subscriber: @RobinKarlsson
Author

I just went back and tried this in Blender 2.69 and 2.68 and apparently this is not how it worked there.I must have gotten something mixed up somewhere along the line as I was sure I could remember it working like this. It could be a nice idea to implement as it would optimize my workflow a bit, but I don't think this is the right place for posting that.

Sorry for posting a faulty bug report.

I just went back and tried this in Blender 2.69 and 2.68 and apparently this is not how it worked there.I must have gotten something mixed up somewhere along the line as I was sure I could remember it working like this. It could be a nice idea to implement as it would optimize my workflow a bit, but I don't think this is the right place for posting that. Sorry for posting a faulty bug report.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2014-07-01 12:41:07 +02:00

Yeah, indeed, afaik this never worked this way. I see how this could be useful, issue being, it’s very hard to determine 'best' option each time. Never the less, that kind of menus always “pre-select” the last used item, and that’s all.

So no bug here, thanks for the report anyway.

Yeah, indeed, afaik this never worked this way. I see how this could be useful, issue being, it’s very hard to determine 'best' option each time. Never the less, that kind of menus always “pre-select” the last used item, and that’s all. So no bug here, thanks for the report anyway.
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
2 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#40900
No description provided.