Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - mvijfwinkel

Pages: 1 [2] 3 4 5
I really like to use static variable in pixel processor too.
If I can use the static variable, I can make Auto Level much faster than now.

Allegorithmic just released a SD update with an improved Auto Levels node which is supposed to be much faster. (See their blog).

Is it possible to have direct inputs on a Function, instead of having to connect other nodes?

I have a function that has 4 static inputs, and I need to set this function up in a lot of parameters. It would be much faster to simply enter the values in input boxes instead of having to create and attached Float nodes. Please see attached sketch.

Or are direct inputs reserved for 'atomic' function nodes (like Float, Integer, etc)?

That was also my solution, keeping the value from getting bigger than 0.99. Good to see I can be even more precise with 1e-6.

Thanks for the help, much appreciated!

I'm trying to make a simple node that shows a uniform color based on a position in a gradient map.

It seems that the alpha mask is always filtered using bilinear filtering. When the position is set to 1.0, it displays the gradient at position 0.0. Exactly the happens for the color when the output is not set to "Nearest Neighbour", so I think somehow the filtering on the alpha channel is not set correctly. SBS example graph attached.

Substance DesignerSubstance Designer - Discussions - Re: performance issues(?)
 on: February 12, 2018, 02:02:34 pm 
It's probably faster because it does not have to store and display the intermediate maps, just the output?

While for your source graph, it has to keep 100+ maps in memory.


Even being able to copy/past settings between nodes would be a huge time saver.

For example, right now I have made a custom version of the scratches generator. When I want to update my graph with this new node, I have to manually transfer all settings from the old to the new node. A "Copy settings" function that would apply all variables with a similar name would save me a lot of time.

The 2D view has a little Save icon which you can use to export the current 2D View window contents. Could that be helpful?

The Edge Detect node is also one to avoid if you want your material to have a flexible resolution. It's output also varies too much between low and high resolutions.

So I actually found that the color map does match (It was just hard to see in the viewer).

I often have this problem as well. I'd love to be able to cycle through the unlit maps in the viewport, so you can compare pixel level details between color/height/normal. Voice your support here if you think it's a good idea:,17987.0.html

Is your GPU enabled under Edit->Preferences->iRay?

On my machine this got disabled after a software updated (but it didn't take 30 seconds to start iRay, it was just rendering at 1/10 the speed).

I would not count a solution involving modifying the file in a text editor as a "correct" answer ;)

More seriously though : if you do that, you're on your own. We cannot offer any guarantee regarding how well that will work, nor offer any support with your future use of that file.

I can understand you don't want to give support in case of problems when using this method, but I feel you should at least mention it as a possibility. It can be very valuable to revert to an older version, in my case it saved me a few hours or having to redo a material from scratch. So as a user I rather know even if the chance of it working is slim.

Please note that the documentation about sizes contains an error. For relative size the name variable is $sizelog (the documentation still refers to $sizelog2.

More here:,17930.msg75363.html#msg75363

Sorry. It's not possible.

The correct answer is: yes, in *some* cases you can.

Open up the SBS in a text editor and change version numbers right at the start of the file:

<formatVersion v=""/>
<updaterVersion v=""/>

Change the version numbers to the version of the numbers you see when you open a sbs saved with your older Designer.

It might not always work, or some nodes will show up as ghost nodes, but it's better than nothing.

It's super akward that Designer doesn't display variables values, having to guess when a function is not working as expected is very unproductive.

At least for more static functions it should be possible to display the value of a variable. For example functions that only depend on exposed parameters.

Pages: 1 [2] 3 4 5