Recently CarlG found a node in the search options of the shader editor called “squeeze value” that squeezes values around a centre point.
josephhansen pointed out that it is not in the documentation, but I found it.
………………….in the 2.79 documentation!
Maybe I am going crazy but it has occurred to me that it could be a GHOST node.
A node that has been lurking in the depths of Blenders code since 2019 waiting to be summoned by the search command and has risen from the dead to haunt us!
I have started to check underneath my desk to make sure that there are no nodes coming to get me.
The node has materialized in Blender 3.4 (last heard of in 2.79).
Here is a link to Carl’s discovery, as it was going off topic I thought this phenomenon deserved a dedicated thread.
If anybody could shed a bit of light on this I would be great-full.
Has anyone else had an encounter with this node?
Does anyone know a developer who could ease my mind?
The node has been around since 2006 (I think this is the inital commit: 8dbefad45100, CC @guitargeek), but it seems to have been somewhat forgotten.
There was a patch to expose the node in the search, but looks like there aren’t plans to support it anymore.
I suspect it has been unearthed by the recent changes to the node search.
On the Windows 3.4 Beta build I’m using (Hash: 841460afcebd) it’s there. Do I need to be scared now? Maybe consult my witchdoctor? (There’s a Blenderguru, there must be a Blendervoodopriest or something… Whoyagonna call? -Blendbusters! .)
It was probably introduced in 2.42 for shading nodes of Blender Internal materials.
It was never supported by Cycles.
Since 2.80, most of shading nodes have been hidden in UI for EEVEE, and progressively revealed along progress of EEVEE development to support them.
Clément probably made EEVEE support it, without questioning it.
But Brecht did not want Cycles to support the node. https://developer.blender.org/D10891
It looks like taking a decision about removal, acceptation or improvement of the node was not a priority for Brecht, during past year.
So, it is still visible in in development versions. But it is hidden in official releases.
No, I just checked.
EEVEE and Cycles are currently supporting a lot more shading nodes than Blender Internal ever did.
Only other node present in Blender Internal shading nodes and absent in EEVEE/Cycles was Lamp Data node.
There was no ambiguity that was partially redundant with some Cycles nodes ( Geometry, Light Path ) and partially relative to a light linking not supported by Cycles and EEVEE.
So, this one was removed.
so is there a way to “squeeze” a value ? for example i have a value from 0 to 100 and i want limit it to 50, but without being a rough cut, i could use “Greater than” from math node but i kinda want the end value to be smooth or ‘blurred’
What are you trying to accomplish? Map range is for remapping an input range to a new output range; linearly, smoothstepped, smootherstepped, or stepped linear. If you want control over the curvature this happens, do linearly first then control the curve after. I recommend normalizing it back to 0-1 range first for math predictability, apply the curvature, the map range it back to where you want it. Here is what I use for fBias and fGain functions:
. The function “sqrt(1 - input * input)” is also very useful for circular sections, in some cases “sqrt(input - input * input)” when the angle of the trig functions isn’t what you want.
Hehe, no, not mine. A few basic curves that uses fGain which in turn uses fBias. Both sine and triangular will turn into a rounded square signal as the Gain is increased:
While the wave generator could be updated with circular shape (not just triangular, saw, and sine), let’s just say I wouldn’t mind having these available as 1D signal processors. There are others too, but these are the ones I’m using a lot.
.)
