Hi friends!, Just to ask for feedback about something I find weird , as simple as you create a new project,then proceed to use ctrl-r and make 3 cuts on tree sides, top, left and right side of the default cube.
Then You select faces and then select extrude region on the left side panel and proceed to select two adjacent faces on the cube and this is what You expect:
as You can see the handle appears upside instead diagonally making harder to extrude that way (diagonally).
Now, if You just take the cube and subdivide it with subdivision surface 2 and select simple and apply, the cube although looks identical than the manually subdivided , in this case You can select several adjacent faces and You will have not the issue mentioned.
I dont know , as I rarely use extrude region or extrude along normals, but it is interesting why blender is behaving that way. As a side note, I checked normals, and doubles.
Hope You can give some feedback, Thank You.
It should match the direction of the normals of the selection, so yeah, that’s a bug, just report it. I can replicate the issue on Windows, Blender 4.1.1, 4.2.3 and 4.3.0 RC
Something is wrong in the math. If you select all geometry in edit mode and move it slightly, it goes away. There must be some combination of coordinates or values stored that the algorithm fails with.
By entire mesh, you mean the mesh in edit mode, or the object in object mode? If you move the object, nothing changes about the mesh in object space. It seems to go away if I do it in edit mode. In any case, that probably doesn’t matter much. That’s a bug.
I mean if you were looking for a solution, you can just use the extrude operator instead of the tool. That works fine. Just change transform orientation to Normal and E works exactly the same.
Oh no, it doesn’t! That’s buggy as well at least in 4.3.0
It’s the same thing - it mostly works but sometimes doesn’t. I only tested it a few times before commenting and it worked then, but it sometimes doesn’t.
Oh, but it’s also broken in 3.6… It’s an old one… Seems like a major bug… I am starting to suspect it might be reported already and I am just failing to find it.