What is this E value that we have on the ADM tools? :shrug:
https://drive.google.com/file/d/0ByXkyEXdv3loUmRfR2tWYktMMlk/view?usp=sharing
I never got what is that for.
What is this E value that we have on the ADM tools? :shrug:
https://drive.google.com/file/d/0ByXkyEXdv3loUmRfR2tWYktMMlk/view?usp=sharing
I never got what is that for.
Damn, just found it, sorry. I wish I could delete this post.
However,
Equal Data Type:
The only suboperator that produces the Equal data type is the Parameter suboperator. The Parameter suboperator is particularly useful for setting (or letting the user set) the same parameter value for several suboperators. Very often this common parameter is exposed later in the interface.
One simple example: You would like to make a Data Operator that places particles randomly on the surface of an object, and sets a random initial speed. You’ll use the Geometry suboperator (Random Surface Point) for position, and the Vector suboperator to define the speed with Deviation set to 360 degrees for a random spread of direction.
Both suboperators have the Random Seed parameter. So, naturally, you would like to expose the Random Seed parameter so the user can play with chaos setup. But it might seem strange to have two Random Seed parameters in the interface. Therefore, you can wire both Seed parameters in the Geometry and Vector suboperator into a single Parameter suboperator with the type Uniqueness Seed. You can then expose Random Seed of the Parameter suboperator.
The Equal data type has subtypes: Real, Integer, Time, Sync, and Seed. Each uses a different shade of green. The Parameter suboperator has several output types: Angle, Float, Percent, World (all are Real type), Integer, Time, Animation Sync (as Sync) and Uniqueness Seed (as Seed). Angle, Float, Percent and World just differ as they are shown to the user in the UI, they are all Real. You can wire the Parameter output only to the matching E inputs, which is usually quite obviousif you link the Random Seed of a suboperator then the Parameter suboperator should have Uniqueness Seed type as well.
It is possible to live without the Parameter suboperator by using the standard 3ds Max script-wiring technique, and script-wiring the parameters of the suboperators, instead of linking them to a Parameter suboperator. However, script wiring is more time-consuming to set up, it does not have good visual reference as the Parameter suboperator, and it is prone to save/load and clone problems.
http://help.autodesk.com/view/3DSMAX/2015/ENU/?guid=GUID-4059B714-CF45-4D92-B962-9248F603B3D4
I think in the last ten years I have seen this used twice, I guess most of my stuff has never been complex enough to warrant using it 