Sure. 1.732 is absolute minimum multiplier, mathematically speaking. It also don't take into account VDB mesh smoothing (your last example). We could calculate this precisely checking VDB meshing implementation.

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.

Hi @james egien (cubic_sloth), do you still want to finish this patch? @Charlie Jolly (charlie) or me might pick it up.

Sorry, apparently I forgot how Musgrave textures work. Lacunarity in basic Fractal Perlin Noise (our Noise node) affects only frequencies. However in Musgrave textures it affects frequencies and amplitudes. It's calculated this way:

Roughness = pow(Lacunarity, -Dimension);

In D7065#168760, @Luca Rood (LucaRood) wrote:

I'd suggest either changing this patch to match the Musgrave, or changing the Musgrave to match this. Having a consistent behaviour would make a lot of sense, considering they both use the same concept of stacking noises.

Lacunarity in fractal noises modifies frequency/scale of octaves, not amplitudes.
Roughness/Persistence works a bit similar to Dimension in Musgrave but input behavior and results are rather different.

I assume that differences in second example are caused by limited resolution of generated texture. Pixel values are averaged when stops are very close. Smoothstep version doesn't have this precision issues.

Please provide proper report.
https://wiki.blender.org/wiki/Process/Bug_Reports

Your model might have scale too big or too small to show up in viewport.