Page MenuHome

current value '0' matches no enum in 'ToolSettings', '(null)', 'snap_node_element'
Closed, ResolvedPublic


System Information
Operating system: Linux-4.13.10-041310-generic-x86_64-with-debian-stretch-sid 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.67

Blender Version
Broken: version: 2.81 (sub 3), branch: master, commit date: 2019-08-20 22:35, hash: rBdaba3e871ff5
Worked: rBf2cab8267f22

Short description of error
current value '0' matches no enum in 'ToolSettings', '(null)', 'snap_node_element' is printed repeatedly to the terminal, as soon as a shader editor is on the screen.

Exact steps for others to reproduce the error

  • start Blender and switch to the default Shading workspace
  • watch the terminal

Event Timeline

Philipp Oeser (lichtwerk) triaged this task as Confirmed, Medium priority.

Guess this is due to recent changes by @Germano Cavalcante (mano-wii) (not sure though...)?

Brecht Van Lommel (brecht) raised the priority of this task from Confirmed, Medium to Confirmed, High.

I see the same console messages all the time as well.

I guess the 3D viewport and node editor snapping options need to become separate settings. This is something we should have done anyway, but with more snapping changes this becomes more urgent.