Vertices Rip shortcuts have locked Fill checkboxes #73379

New Issue

Paul Kotelevets · 2020-01-25T03:10:53+01:00

Paul Kotelevets commented

2020-01-25 03:10:53 +01:00

System Information
Operating system: Linux-4.15.0-51-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116

Blender Version
Broken: version: 2.83 (sub 1), branch: master, commit date: 2020-01-19 15:50, hash: 9b70950e3c
Worked: (optional)

Short description of error
Both Rip actions (V, Alt+V shortcuts) have locked Fill checkboxes, attempt to swap their shortcut values leads to their collapse.

Exact steps for others to reproduce the error
Vertex Rip without fill is a common way of using vertices rip action - to split a mesh into a parts by seam loop, so a simpler key combination is required due to relevance.
So, when trying to cover entire merge/rip actions map making setup like this

V - merge vertices (the most commonly used operation, simplest quickly accessible shortcut)
Alt+V - simple rip (frequently used operation, medium accessible shortcut)
Alt+Shift+V - rip fill (rarely used operation, long shortcut)

the only way is to delete both rip defaults and remap mesh.rip_move operator manually.

GIF

**System Information** Operating system: Linux-4.15.0-51-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116 **Blender Version** Broken: version: 2.83 (sub 1), branch: master, commit date: 2020-01-19 15:50, hash: `9b70950e3c` Worked: (optional) **Short description of error** Both Rip actions (V, Alt+V shortcuts) have locked Fill checkboxes, attempt to swap their shortcut values leads to their collapse. **Exact steps for others to reproduce the error** **Vertex Rip without fill** is a common way of using vertices rip action - to split a mesh into a parts by seam loop, so a simpler key combination is required due to relevance. So, when trying to cover entire merge/rip actions map making setup like this - V - merge vertices (the most commonly used operation, simplest quickly accessible shortcut) - Alt+V - simple rip (frequently used operation, medium accessible shortcut) - Alt+Shift+V - rip fill (rarely used operation, long shortcut) the only way is to delete both rip defaults and remap **mesh.rip_move** operator manually. GIF ![RIP FILL.gif](https://archive.blender.org/developer/F8300502/RIP_FILL.gif)

Paul Kotelevets commented

2020-01-25 03:10:53 +01:00

Added subscriber: @1D_Inc

Paul Kotelevets commented

2020-01-25 03:56:34 +01:00

Both default rip operators shortcuts seems to be interconntected, so changing shortcut of one influences shortcut of another.
Deleting and manual reassigning seems to fix that issue.

Both default rip operators shortcuts seems to be interconntected, so changing shortcut of one influences shortcut of another. Deleting and manual reassigning seems to fix that issue.

Pasang Bomjan commented

2020-01-25 08:00:55 +01:00

Added subscriber: @Pasang

Pasang Bomjan commented

2020-01-25 08:00:55 +01:00

This has always been the case, even in 2.7x. I had even bought an 11-button mouse just to do this but gave up and always thought of it as a limitation.

Paul Kotelevets commented

2020-01-25 08:52:07 +01:00

In #73379#858205, @Pasang wrote:
This has always been the case, even in 2.7x. I had even bought an 11-button mouse just to do this but gave up and always thought of it as a limitation.

That's strange, in 2.79 they are, actually different operators, called mesh.rip_move and mesh.rip_move_fill
The second one works with fill even without fill checkbox filled.

> In #73379#858205, @Pasang wrote: > This has always been the case, even in 2.7x. I had even bought an 11-button mouse just to do this but gave up and always thought of it as a limitation. That's strange, in 2.79 they are, actually different operators, called **mesh.rip_move** and **mesh.rip_move_fill** The second one works with fill even without fill checkbox filled.

Pasang Bomjan commented

2020-01-25 18:49:45 +01:00

@1D_Inc, Oh, I've mistaken your issue with my similar experience. Please ignore it.

Paul Kotelevets commented

2020-01-26 20:49:28 +01:00

In #73379#858378, @Pasang wrote:
@1D_Inc, Oh, I've mistaken your issue with my similar experience. Please ignore it.

Thats okay, I remember same experience.
It is always hard to define the problem in such cases, because it is easy to understand that something is wrong, but hard to define what exactly.

> In #73379#858378, @Pasang wrote: > @1D_Inc, Oh, I've mistaken your issue with my similar experience. Please ignore it. Thats okay, I remember same experience. It is always hard to define the problem in such cases, because it is easy to understand that something is wrong, but hard to define what exactly.

Richard Antalik commented

2020-01-27 15:28:57 +01:00

Closed as duplicate of #68531

Richard Antalik closed this issue

2020-01-27 15:28:57 +01:00

Germano Cavalcante commented

2021-01-05 14:14:07 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2021-01-05 14:14:07 +01:00

I reproduced this bug in the 2.83, but not the latest daily build, so it appears the bug has been fixed already.

Paul Kotelevets commented

2021-01-05 15:11:03 +01:00

In #73379#1087167, @mano-wii wrote:
I reproduced this bug in the 2.83, but not the latest daily build, so it appears the bug has been fixed already.

Sounds nice! Thank you for your attention.

> In #73379#1087167, @mano-wii wrote: > I reproduced this bug in the 2.83, but not the latest daily build, so it appears the bug has been fixed already. Sounds nice! Thank you for your attention.

Yevgeny Makarov commented

2021-01-05 15:26:23 +01:00

Added subscriber: @jenkm

Yevgeny Makarov commented

2021-01-05 15:26:23 +01:00

@mano-wii Oh, I re-checked, actually I seem to have a different bug.

Can you reproduce something like this? Make sure that the cursor does not move between clicks. Maybe there is already a report for this.

#73379.mov

@mano-wii Oh, I re-checked, actually I seem to have a different bug. Can you reproduce something like this? Make sure that the cursor does not move between clicks. Maybe there is already a report for this. [#73379.mov](https://archive.blender.org/developer/F9551433/T73379.mov)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Vertices Rip shortcuts have locked Fill checkboxes #73379