If possible, we need a sampler function node that accepts an integer used to select the image to sample from.

If this is not possible, we need some type of setup change that allows us to create generic sampling functions that sample pixels from images, without those image indices being hard-coded into the functions.

Currently, the only way to do this is some type of switch selector that samples from several images and returns the one desired. And in the pixel processor, this is a problem, because all code ends up getting executed for each and every sample. This means we end up sampling from 5+ images for every single sample, just to get the option of selecting the image by index.

Using 8 bit gray values in programs like Painter results in very low quality materials. I always use 16-bit ALL of my materials. But I often forget to set the graph format before I publish, which means some of my filters are most likely making some aspect of my materials look bad without my noticing.

I was even told by a member of your staff to always use 16 bit for gray values.

Anyway, it would benefit me greatly to have Designer default to 16-bit. And options to allow us to select these types of defaults makes a lot of sense for everyone.

Allow us to write function nodes that accept any type for their inputs. Since function nodes are inlined anyway, it makes a lot of sense to give us this freedom, if its possible.

For example, we should only need to write one function to generate an average. Not one for ints, one for floats, one for vector 2, vector 3, etc.

On the implementation side, it could be as simple as adding a new type to the function parameter drop down called "any". Then just assign whatever type that gets plugged in as the parameter's official type.

Return values will automatically become type independent as a result of these changes.

Currently, we have to mark those little pins next to each exposed parameter to record it as part of a preset. But I've also noticed that Designer marks parameters whose value has changed from its default. Doesn't it make sense to use this as part of the recording process? When a user switches into preview mode with the intention of creating a preset, they have very little reason to change any values, other than to make those values part of that preset. So why not record all values that are not set to their defaults? This would make the entire process easier, intuitive, and more user friendly.

If nothing else, maybe an option to cause this behavior?

As a related note, I had a lot of trouble figuring out how to record presets when I first started. I think it would help tremendously to add some mouse-over tips in the record preset button that describes how it works (either way it works).

Add the ability to clone a node, like you can do in e.g. Nuke. From Nuke's documentation:

"You can clone nodes in preparation for pasting them elsewhere in a script. Cloned nodes inherit the values of their parent, but unlike copied nodes, they also maintain an active link with their parents’ values. If you alter the values of one, the other automatically inherits these changes.

Clones are helpful for maintaining consistent setups across multiple elements. For example, you might use clones to apply an identical film grain setup to a series of elements shot on the same stock. Should you need later to make changes to the setup, these changes would automatically ripple throughout the script."

This can be achieved in Designer through exposed parameters, but that's pretty cumbersome when nodes have many parameters, and you also clutter the graph's input-parameters with variables you actually only want to use internally, not expose to the user.

Cloning a node would set this up automatically.

On FxMap-Quadrant node, there is a option named Pattern Varient. However, we don't use this most of the time, because it only works with very specific pattern in Quardrant-Pattern parameter.

So, here is my suggestion.

1. At very beginning of FX graph building, we should choose a node on its properties view.
2. The node must not have any input nodes, and have only one output node.
3. If complie is available, complie the Fx map node on Substance Designer.
4. After the complie, we can use every parameter of the node that we chose at step 1 in Quadrant node instead of Pattern Varient.

If it's possible, I will be very very happy.