Page MenuHome
Create Task
Maniphest T75377

Extrude Edges - Normal Orientation is wrong
Closed, ArchivedPublicBUG
Actions

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66

Blender Version
Broken: version: 2.83 (sub 11), branch: master, commit date: 2020-04-03 21:41, hash: rB7c0e28594840
Worked: never

Short description of error
Extrude Edges along Normal Transform Orientation is broken. Take a look at GIF below.
https://i.imgur.com/AXi2jD2.gif

It work same for Active Element, Median Point or Individual Origins. It look like operator create new edge with some micro position offset and then take Normal Orientation not from base edge but from this new one. If I press RMB to cansel extrusion - new edge has same Normal Orientation as axis while extrude operation.

And it work in this way since 2.7X... Would be good to see it fixed in 2.83.
https://i.imgur.com/ue6tVR7.gif

Exact steps for others to reproduce the error

  • Open attached file (you should see a cube with a selected edge and orientation to normal)
  • Extrude selected edge and press Z to move the edge in the direction indicated by Gizmo

Notice that the movement follows another direction.

extrude_bug.blend550 KBDownload

Event Timeline

Orest Kravchuk (IIIFGIII) created this task.Apr 4 2020, 1:57 PM
Germano Cavalcante (mano-wii) added a subscriber: Germano Cavalcante (mano-wii).Apr 6 2020, 4:07 PM

The video is not very clear about the steps to reproduce the problem.

Please follow the submission template and guidelines and provide a list of steps to reproduce the problem.
Also explained here: https://www.youtube.com/watch?v=JTD0OJq_rF4

Orest Kravchuk (IIIFGIII) added a comment.EditedApr 6 2020, 11:39 PM
In T75377#904596, @Germano Cavalcante (mano-wii) wrote:

The video is not very clear about the steps to reproduce the problem.

Please follow the submission template and guidelines and provide a list of steps to reproduce the problem.
Also explained here: https://www.youtube.com/watch?v=JTD0OJq_rF4

Thank you for reply. Of course. I will describe problem more detailed, as you wish.

Please follow steps.

  1. Switch to Normal Transform Orientation mode. No metter which Transform Pivot Point option you will enable Individual Origins, Median Point or Active Element - they all give wrong axis.
  2. Select edge. You can also enable Gizmo visualization for better understanding of selected edge Normal axis directions. https://i.imgur.com/IcI1sHJ.png
  3. Press E to start Extrude Edges operator ( or choose same item in context menu ). https://i.imgur.com/kUemDy3.png
  4. While in Extrude Edges operator press X or Z for constraint along Z or X axis( edge Normal Z or X as expected, because Normal Transform Orientation is enabled ). https://i.imgur.com/vay7775.png
  5. Now you can see that edge extrusion goes not along X and Z axis which you saw before with gizmo, but along some different axis with different directions. https://i.imgur.com/OkX6zzU.png

Additionally.

  1. If you press Right Mouse Button during extrusion action to cansel it - new edge will be created without extrusion.https://i.imgur.com/nq4wmoy.png
  2. You may notice that this new edge Normal Orientation look at same directions as those which we saw during extrusion.
  3. With this in mind we can assume that Extrude Edge operator algorithm may work in wrong way. Looks like operator firstly create this " new " edge and only then pick Normal Orientation from it instead of use Nomal Orientation of edge selected when we start extrusion. But of course I'm not a coder and I have no ideas what exactly work wrong.

Bug work not always same.
Results for other edges in this model ( notice, this example model is not perfect cube, just extruded plane to some cubic shape ).

https://i.imgur.com/wlCBmxj.png
https://i.imgur.com/FqSEoYx.png
https://i.imgur.com/jy7703w.png

In similar example case with perfect cube shape all for edges give same angle difference between what Gizmo show and what Extrude operator use.

https://i.imgur.com/7CbEDzl.png
https://i.imgur.com/MsGACfW.png
https://i.imgur.com/wTmvWsI.png
https://i.imgur.com/emEvhSO.png

I hope such description will be enough. But if it still not enough - let me know. I can capture video with voice description. Thank you for attention.

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Confirmed.Apr 7 2020, 8:42 PM
Germano Cavalcante (mano-wii) updated the task description. (Show Details)
Germano Cavalcante (mano-wii) added a project: Modeling.
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".
Germano Cavalcante (mano-wii) updated the task description. (Show Details)
Germano Cavalcante (mano-wii) closed this task as Archived.Apr 7 2020, 8:50 PM
Germano Cavalcante (mano-wii) claimed this task.

In better terms, this works as expected.
The extrude operator is a macro that performs two operations:

  • Extrude (similar to inset faces)
  • Move with Z constrain and normal orientation.

After the extrude the normal of the element is different.

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Orest Kravchuk (IIIFGIII) added a comment.Apr 10 2020, 8:48 PM
In T75377#905666, @Germano Cavalcante (mano-wii) wrote:

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Even if it correct on code side and work " as expected " - it still work as 120% bug on user side and not even close to what expected. Code is ok, but algorithm of actions is not. What you said is just what I thought.

Sorry for such words, but propose me to go with this issue to some RCS or Devtalks and request something is nearly equal to propose me to go **** myself...

I read and write on RCS about two years - useless place, things stay in top years and still not implemented... Better to call this website NOC - no one care.
I have experience to request on Devtalks - to get something like this is ok, still no one care, pretty same" 0 " efficiency place.

It's not just some sort of " my own problem " so I can go **** myself with searching for solution while no one care. It's a problem of all Blender users who use it for modeling and It work in this wrong way since I start learning Blender more then 2 years ago, but I suspect it exist much more. During all this time still no one fix it.

I have report here few times bug and saw how fast they were fixed. I thought that this is right place where people can do real things instead of useless talks. If you know anyone who can get such task and make things work correct - please contact this person(s) and show this problem. If you can do it by yourself - please do something. If you know where and how to bring real attention to this issue - do at least this, please.

Germano Cavalcante (mano-wii) added a comment.Apr 10 2020, 9:24 PM

This is not a bug.
You can see that it is not a bug when trying this:

  • Extrude and press Esc to cancel the move,
  • see the new normal direction.

I'm not even sure if what you propose is really an improvement on the current implementation.
What you propose can be compared with what is already done by the extrude tool (by the extrude gizmo).

Assuming that the movement should always follow that blue arrow is just an assumption. Why then say it is a bug?

I know the code and I can say that it is not even easy to implement.

This bug tracker does not accept feature requests because developers cannot handle the number of feature requests.
They can barely handle the amount of bugs.

(I still don't see any convincing arguments for considering this a bug)