Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

SD does not recognize a Parameter Step <> 0.01

New Here ,
Jan 14, 2023 Jan 14, 2023

SD does not recognize a Step option other than the default 0.01 for a Float parameter.

Select an unused portion of the Graph to view INPUT PARAMETERS.

Select Parameters to view the list of exposed parameters for the graph.

Select > for any Float parameter to view the options for that parameter.

Notice the default value, 0.01, for the Step option.

Edit the default value so that it becomes 0.1 or 0.001.

Select the parameter under Preview or Presets.

Select the increase or decrease (step) controls to change the parameter value.

Notice that the parameter is changed in steps of 0.01.

 

It is inconvenient to scroll through hundredths of a unit of the parameter when tenths are suffient.

It is more inconvenient to have to repeatedly delete and enter hundredth of a unit after 0.99 when changing the Mask Random value for a node with a large Tiling Amount.

 

Bug Unresolved
87
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
2 Comments
Community Expert ,
Jan 14, 2023 Jan 14, 2023

I can't replicate that issue here. After setting the step value to 0.1 or 0.001 the preview input slider changes in steps of 0.1 or 0.001.

I am using Substance Designer v 12.3.1 on Windows 11

 

Dave

Translate
Report
New Here ,
Jan 15, 2023 Jan 15, 2023
LATEST

Thanks for checking, Dave. I'm on macOS. I have ten or twelve parameters that control Mask Random values. In Parameters, I set each to a Default value of 0.99 and made sure that each Step value was set to 0.001. In both Preview and Preset (for one preset), I changed each of the Mask Random from either 0.99 or 0.99X using both the inc and the dec controls. The Mask Random value consistently changed by 0.01 (after 0.99X changed to 1 or 0.99). Looks like the bug is OS dependent.

Translate
Report