Page MenuHome

Drivers not working with local rotation
Confirmed, NormalPublicBUG


System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48

Blender Version
Broken: version: 2.79, 2.83.1, 2.90
Worked: N/a

Short description of error
Drivers in the Material Mapping-Node work fine in the world rotation-mode. But when I switch to LOCAL rotation, it doesn't work any more.

Exact steps for others to reproduce the error

  1. In the default blender setting start up file, add an Empty.
  2. go in the cube material and add a Material.
  3. Make this setup in the Material: Texture Coordinate (use the normal output-socket)--> Mapping-Node-->Normal-node(Dot-output)--->emission-node--->Material-output.
  4. Add a driver to the X-Rotation of the mapping node.
  5. In the driver: Use the Empty as the input and the x-rotation as type.
  6. Try it out: It works great. (rotate the empty)
  7. Now change the driver space-type from world-space to local-space.
  8. Try it again. It's not working any more.

Event Timeline

Can you provide a simple file showing the problem?

Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Wed, Jul 1, 1:40 AM

I am not able to reproduce this as well. Behavior in 2.82 seems to be consistent with 2.90

Strange... I did upload a file with the bug report. O.k., here it is again.

The problem is not in blender 2.9 or 2.82, its only in blender 2.83 and 2.83.1 .

I may be mistaken, but as far as I know, 2.83.1 is only for critical bugs.
In this case, if the problem is not seen in 2.90, then it can already be considered solved.

Germano Cavalcante (mano-wii) changed the task status from Needs Information from User to Confirmed.Wed, Jul 1, 3:06 PM
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".

I tested it at 2.90 and the problem still exists.
It looks like the object must have at least one parent for Local Space in drivers to work.

Thank you for your help!
Good to know, that this is really a bug, not something wired I didn't expect.

Looking forward to a blender Version with this bug-fix :)

Thank you for your help!
Good to know, that this is really a bug, not something wired I didn't expect.

Looking forward to a blender Version with this bug-fix :)


The problem seems to be the same in all versions of blender. You can check it out again. in blender 2.82?
While waiting for your confirmation, I will edit the description removing the information that it worked in blender 2.82.

It is my bet that this will not work for any release, except 2.82. In that release some behaviour was changed in how constraints compute local space (rB7728bfd4c45c).

Blender's constraints have some non-standard behaviour, where "local space" is interpreted differently for parentless objects. This is confusing, and it is what was removed in 2.82, but people were still depending on the behaviour, so this was reverted in 2.82a (rBf881162f81e5).

As a workaround, either use world space (if the object has no parent, this is the same as local space) or give the object a parent.

Thank you, Sybren A. Stüvel. That's really confusion, but now I know it and everything is fine.
I will give my object a parent, because in my file are a lot drivers connected to a local rotation.