Page MenuHome

Vector Rotate Node - Euler modes not working as intended
Closed, ResolvedPublic

Description

System Information
Operating system: Linux-5.3.0-7625-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44

Blender Version
Broken: version: 2.83 (sub 4), branch: master, commit date: 2020-02-24 05:01, hash: rBa31bd3f7b5cf
Worked: (optional)

Short description of error

  • It seems that instead of switching the order in which the euler rotations are applied the actual rotation axes are swapped.
  • When rotating on only one axis, the mode should not matter (as far as I understand)
  • Functionality of mapping node in texture type does not seem reproducable

(maybe my brain is just tangled up, please confirm)

Exact steps for others to reproduce the error
Create sphere with object coordinates -> Vector Rotate

Or:


choose euler rotation mode other than XYZ
rotate any one axis on its own -> sometimes axis is changed
or rotate multiple axes -> order is not influenced, only axes are swapped and inverted

Event Timeline

The Euler options are based on the point transform rather than the texture transform which will explain the difference for this part of the node. Do you think this should change?

As for the rotation order, I'll double check. It was based on another part of Blender and I may have got the sums wrong.

Charlie Jolly (charlie) changed the task status from Needs Triage to Confirmed.Feb 24 2020, 4:03 PM

Okay, thanks for looking into it!
I think, the way it is right now it is more confusing than it is useful. But that is my personal preference.
I would have expected a different interaction with the naming given.

@Simon Thommes (simonthommes) Since this is a new node, my own view is to remove the non-standard euler options and to leave only XYZ option and rename it Euler. If this is really important it can be added later.

Only question is whether to match Texture or Point mapping option?

@Charlie Jolly (charlie) Sounds good to me. I would say match point, as it is standard in mapping.
But it might also be nice to match the additional euler options to all the types from the mapping node... eventually...