This switching behavior prevents me from working when comparing Render Result with a texture side by side. Big oversight imho.

Soft min/max doesn't make sense in this value field. It should behave like other mathematical nodes and accept arbitrary numerical input. Use case for it would be Value set by the user and Min and/or Max values driven by an input, eg a texture.

Something is wrong with my setup. Older versions of blender started doing it too. Issue only occurs while saving to Desktop. Closing.

There is no mirror operator in node editors. Ctrl+M does nothing, then you are just deleting nodes by pressing X.
Closing.

Tested with 2.83.1, 2.90 and latest 2.91 alpha. Can't reproduce on your file.
However, I encounter similar issues often. Shaders don't compile properly when material updates, especially with Node Wrangler viewer shortcut.
Reconnecting nodes helps 99% times, restarting blender always fixes this. Never got case when I can reproduce this behavior.

Ok. Changing status then.

Mapping node rotation works the same. This is unfortunate but we definitely shouldn't use degrees for vector rotations, they are less practical and would require converting back and forth in complex setups.

Accepted range for this parameter is 6 to 9.
Updating with python works for me when using correct values.
Test and close task if it works.

Can't build blender after this commit.

Sure. 1.732 is absolute minimum multiplier, mathematically speaking. 1.732 also don't take into account VDB mesh smoothing (your last example) so value needs to be bigger than that.

In D6204#144790, @Leha (leha) wrote:

But we can increase this Limit a little to prevent artifacts described in the first post.
After some tests I found 7 of voxel sizes is a good value to preserve sharp corners. At the same time it is small enough to not allow holes of shrinkwrap modifier

ssmd.projLimit = target_me->remesh_voxel_size * 7.0f;

In D7541#182065, @Campbell Barton (campbellbarton) wrote:

This depends on the active UV map which isn't visible in the 3D view

Overall this is great. One small issue that needs to be addressed imho. Placement of checkboxes that are not related to a group might suggest they belong to them.

Underlying cause is exactly the same for all those textures. This is basically how GPU handle floating point math and we can't change that. Move texture in Z by a fraction and Z-fighting issues will be gone.

I can confirm this.

@Simon Thommes (simonthommes) Can you elaborate on your use case for this nose? For me it works fine and this rotation flipping behavior is actually ok.

Just tested this briefly and unfortunately this patch breaks shader compilation in Eevee.
After adding Object Info to node tree shader will become pink, except for node tree parts that were previously compiled.