Page MenuHome

Mapping Node Issue. Translation and reading of mapping node data is broken between 2.80 - 2.81
Closed, ResolvedPublic


System Information
Operating system: Windows-10-10.0.16299 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.08

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: rB26bd5ebd42e3
Worked: (optional)

Short description of error
Mapping node data is missing or is not translated at all, correctly when I move my project from 2.80 to 2.81 official build.

Exact steps for others to reproduce the error
I'm using blender from years. Currently, I'm using EEVEE to preview the scene, which I'm developing for my company needs.
I had project including dynamic properties of data /DRIVERS/ attached to the MAPPING NODE in the Shader of an object.

  1. When I migrated from 2.80 to 2.81, drivers were broken into those Mapping nodes and I have had to built them from scratch, there is not a single node. I will not be able to reproduce the complete shader logic for few days including all drivers behavior if this data cannot be translated properly.
  1. When I try to open my progress to downgrade the project with current progress from 2.81 to 2.80, again mapping node is completely broken and cannot be recognized for some reason?
  1. I measured the performance between both versions between 2.80 and 2.81, and can conclude I had much better performance for some reason with the scene in 2.80, without changing anything. Even when I play the timeline, and move any of the attached driver properties, the fps in 2.81 is getting down drastically.

Please, check the previews I'm attaching here.

Here you can see the proper setup in 2.80

Here not recognized driver in the node, strage property type which is not giving much HINT what and how this shuld be re-build

Here when I try to downgrade from 2.81 to 2.80 with existing progress, I'm facing this issue - data for mapping node is not recognized at all

Guys, I'm looking for your support to succeed with the project. Thank you for everything you do!

Event Timeline

Mapping node was rewritten to support dynamic inputs.

Not sure about backward compatibility with drivers. Keep in mind that opening file from 2.81 in older versions may break things, that's expected.

Assigning @Omar Emara (OmarSquircleArt)

It appears we didn't add versioning code to drivers. I will take a look.

Philipp Oeser (lichtwerk) lowered the priority of this task from 90 to 50.Nov 25 2019, 10:56 AM

Hello Guys,
I would like to ask you if there is any progress on this Bug resolved. I saw Fixed in D6302, but how to relate this to the released version to know that bugfix was applied? Can you tell me which version I have to downlowad for this fix?
Thank you!

@Ivaylo Gogov (ivaydesign) : D6302 is not committed (yet).
Once it is, this task should be closed automatically [and you should be notified about this automatically as well].
Then, the fix will be included in the next daily build on

Hello @Omar Emara (OmarSquircleArt) , can I know this bug is already fixed or is in progress. I saw it was moved to resolved state?
If yes (it is fixed) where I can find the fix build for it. Is it coming as fixed package in 2.80 or 2.81 or in 2.82 release?
Could you tell me please? Because I tried with the current build, but still not working.

@Ivaylo Gogov (ivaydesign) The fix should be in 2.82. Can you produce a simple blend file that fails the versioning?