[TRACKER] Visual Shader nodes wishlist

[QbieShay]

Describe the project you are working on

Various VFX

Describe the problem or limitation you are having in your project

Some nontrivial VS nodes are missing.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Adding a couple of nodes to reach feature parity with what spatial shaders and canvas shaders can offer out-of-the-box.

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

Spatial:

• RotationMatrix node (supply axis and angle, return transform and/or transformed vertex)
• Proximity fade
• Distance fade
• Rand from seed (copy-pasted from particles)
• Rand between two values (can substitute above)
• Polar coordinates (with two modes, from polar and to polar)
• Remap (see comment)

Particles:

• Turbulence

If this enhancement will not be used often, can it be worked around with a few lines of script?

It can, but it's about improving VS UX.

Is there a reason why this should be core and not an add-on in the asset library?

It can, but it's about improving VS UX.

[Calinou]

Camera fade

This one should probably be named Distance Fade for consistency with the BaseMaterial3D parameter of the same name.

[QbieShay]

@Calinou fixed :+1:

[paddy-exe]

I would also propose these VS nodes:

• Random value between two given given values

• Ramap node (like the Map Range in Blender)

• PolarCoord node which transforms the given UV coordinates into polar coordinates (like GradientTexture in Blender)

• CardinalCoord node which transforms the given polar coordinates into cardinal coordinates

[fire-forge]

Remap (see comment)

This could be called "Range Lerp" to match the range_lerp() GDScript function.

It would also be nice to add the range_lerp() function to the shading language as well. I've been copy pasting this function into shaders as I need it (adapted from the C++ function in Godot's source code):

float range_lerp(float value, float istart, float istop, float ostart, float ostop) { 
         return ostart + (ostop - ostart) * ((value - istart) / (istop - istart)); 
 }

EDIT: I opened a proposal for this: https://github.com/godotengine/godot-proposals/issues/5112

[paddy-exe]

I actually forgot about the linearized depth from the depth_texture. Correct me if I am wrong, but I haven't seen a usecase where the logarithmic scale (default) was used instead of the linearized one🤔

https://docs.godotengine.org/en/stable/tutorials/shaders/screen-reading_shaders.html#depth-texture