Page MenuHome

Loop Cut Doesn't Exit Properly
Closed, ResolvedPublic

Description

System Information
Operating system: Windows 10 Pro
Graphics card: GeForce GTX1060

Blender Version
Broken: 2.80 Beta, blender2.8, 2018-11-29 Hash: 26d5a3625ed
(example: 2.79b release)
(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)
Worked: (optional)

Short description of error
Doing a loop cut does not exit properly. It goes into an edge mode it appears, but when finished, does not allow selecting edges, faces etc...

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

Start with default scene and cube. Go to edit mode and press 3 to go to face mode and select a face. Now press ctrl R to add a loop cut into the cube.

You can no longer select any faces. It appears to put it into edge mode after adding the loop, but you can’t even select edges or faces or anything. You next need to press 3 to select faces again. (or 2 to select edges).

Event Timeline

William Reynish (billreynish) changed the task status from Unknown Status to Archived.Nov 29 2018, 8:44 PM

Not a bug. This has always been the case. It's strange, but the reason is that otherwise it would not be possible to only have the loop selected.

It seems bugged to me. I can't select anything (not even edges) after doing a loop cut.

Yeah, it definitely seems like a bug, it falls into a strange state. If you enable x-ray, you can select edges, but without it you can't, bizarre.

It seems bugged to me. I can't select anything (not even edges) after doing a loop cut.

Exactly. Not even edges are selectable. It shows it's in edge mode and the select tool was active. Took me a while to figure out why I couldn't do anything with the edges, vertices, or faces.

William Reynish (billreynish) changed the task status from Archived to Unknown Status.Nov 29 2018, 10:02 PM

Ok yes, I can reproduce the last part.

Ok yes, I can reproduce the last part.

Thanks!

Campbell Barton (campbellbarton) changed the task status from Unknown Status to Resolved.Nov 30 2018, 6:34 AM

This is working in a760e73dcf6f0a0da901359d1456ad5ca180ebeb

Thanks for fixing so quickly!