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 - Luca Giarrizzo

Pages: 1 2 [3] 4 5 ... 32
31
Hello @Cohen Olson 0,

Thank you for clarifying!

Consider each output in your graph has it own 'path' of nodes. These paths may come together upstream in the graph, as they pull information from the same sources.
A common workflow is starting building the Height path, and pulling information from it to feed other paths, such as Normal or Roughness. Thus, while the Normal path will include more high-frequency detail than the Height path down the graph, it needs to pull information from the Height path.

I recommend arranging your graph so that these paths appear and read very clearly, so you have better control over what information feeds into a path and when it does so.

It is not necessary to split height-related and normal-related nodes into separate sub-graphs for optimisation purposes.
Splitting parts of a graph into sub-graphs generally follows one or both of these principles:
  • The split portion executes one specific function/effect but uses a lot of nodes to achieve it
  • The split portion can be reused across multiple graphs
In the attached image, you can see in the red frames how the Height and Base color paths are arranged, as well as a number of sub-graphs which have one specific role.

I hope this is helpful!

Best regards,
Luca

32
Hello @jellyk,

Thank you for reaching out to us!

I am interested in investigating this issue further. Can you please send me an SBS package which include a graph demonstrating the problem?

Feel free to send it out to me in a direct message if you prefer not to disclose the file publicly.

I appreciate your help and patience!

Best regards,
Luca

33
Hello @bluicat,

You can use the Material blend nodes. There are different nodes depending on how and what your want to blend.
Feel free to let me know if these nodes help!

Best regards,
Luca

34
Hello @ptoing,

Indeed, in the tutorial you linked, Wes uses Connection splitters, which are not available anymore and are now replaced by Dot nodes.

Dot nodes let you merge multiple connection into one rerouting point and their connections are editable. In this sense they are a better option for reducing clutter and making it easier to control the routing of connections in the graph.

That being said, it is true that it is now not possible to have curved and straight links concurrently in the graph.

I hope this is informative!

Best regards,
Luca

35
Hello @Cohen Olson 0,

I am unsure I understand what you mean exactly by node groups and shared nodes. Is that related to splitting graphs into subgraphs and using instance nodes in the main graph?

Feel free to provide more details, and include screenshots in this thread.

Best regards,
Luca

36
Hi @willg3dg,

I am glad! Feel free to get back to us if you need further assistance.

Best regards,
Luca

37
Hello @willg3dg,

Thank you for reaching out to us!

Indeed, it is currently not possible to expose presets in a node instance directly at the graph level.

The behaviour you describe is largely what is expected: when a preset is applied to a node which has exposed parameters, the parameters impacted by the presets are switched to the state saved in the preset – i.e. not exposed/driven by a function graph if that was not the state saved in the preset.

Please try the following steps to recreate your node presets at the graph level with as few actions as possible:
  • Save the node's default values, and each of the node's presets to separate Preset files (*.SBSPRS)
  • Batch expose the node's parameters at the graph level
  • In the graph properties, display the Parameters tab in the Input parameters section
  • In the tab's top bar, open the drop down menu next to the '+' button and select the Load values from file option
  • Load one of the preset files saved in step 1
  • Select the Presets tab, name the preset and click the New button
  • Repeat steps 3 to 6 for each of the preset files saved in step 1
  • Repeat steps 3 to 5 for the preset file containing the default values to retrieve those easily
I understand this is still somewhat time consuming depending on the number of presets which need to be recreated. I appreciate your feedback regarding exposing presets, and will forward it to the rest of the development team.

I hope this is helpful!

Best regards,
Luca

38
Hello @Cohen Olson 0,

Thank you for reaching out to us!

Indeed, you can load SBS and SBSAR files on both computers provided they use matching versions of Substance software. On the system with no GPU, the CPU version of the Substance engine will be automatically selected. The CPU engine may output slightly different results than the GPU engine, so it is recommended to check your graphs for any undesired results when switching systems.

Please note that loading SBS packages on a different system may result in missing dependencies if the resources used by the package have different paths.
To prevent this issue, you may do either of the following:
  • Export the package with dependencies: this will create an autonomous project folder which can be moved between workstations.
  • Using aliases: In the Aliases tab of the Project section in the Preferences window, you can set up aliases which point to a location on the system or remote storage. These paths will be replaced by the aliases in SBS packages, which can let you move SBS packages across systems as long as the file structure after the aliased path is the same. You can learn more about aliases here and their applications in project configurations here.
I hope this is helpful and informative!

Best regards,
Luca

39
Hello @Ziflin,

Indeed, let me know if you experience this issue again. I will perform some tests on the Redo action on my side.

Thank you for your help!

Best regards,
Luca

40
Hello everyone!

In Substance Designer 2021.1.2 (11.1.2), we fixed an issue impacting the refresh process of Library thumbnails. You may have experienced this issue in the form of thumbnails 'stuck' on their refresh icon.

We strongly recommend you manually trigger a rebuild of Library thumbnails, by following these steps:
  • Open the Edit menu
  • Select the Preferences option to open the Preferences window
  • Select the Library section
  • Click the Rebuild thumbnails button
The thumbnails should then be updated to their expected image.

Alternatively, you can delete the thumbnail images from your system before starting Substance Designer. They are stored at the following location per OS – you may delete the thumbs folder altogether:
  • (Windows) C:/Users/[USER_NAME]/AppData/Local/Allegorithmic/Substance Designer/databases/thumbs
  • (macOS) /Users/[USER_NAME]/Library/Application Support/Allegorithmic/Substance Designer/databases/thumbs
  • (Linux) /home/[USER_NAME]/.local/share/Allegorithmic/Substance Designer/databases/thumbs

Please note triggering a rebuild of Library thumbnails from the Preferences window is a good first step to troubleshoot thumbnails issues in general. Please try this if you experience such issues.

Thank you for your patience, and have fun with the Substance tools!

The Substance Designer team

41
Hello @bluicat,

Thank you for reaching out to us!

The mesh in the 3D View becomes invisible because the Alchemist filter template is set up with Input nodes with a default value of 0 or (0, 0, 0, 0) connected directly to Output nodes.
This means that some outputs such as Opacity and Ambient Occlusion have a value of 0 by default, which makes the mesh appear black and entirely transparent.

Default values other than 0 for Input nodes is a feature exclusive to the Substance engine v8, and this template was set up for the best compatibility. That being said, I can suggest the following courses of action:
  • Use a non-0 default value for the Input nodes – again, this is only supported by Substance engine v8
  • Use a bitmap resource as a preview input in the Input nodes. To do this, you can drag and drop a bitmap resource from the Explorer panel to the Input node
  • Put aside the Input nodes, and use placeholder nodes while working on the graph. Reconnect the Input nodes when finished
Regarding the Normal format, you can set it to the one matching your workflow in the General tab of the Project settings for your current project. These settings are located in the Projects section of the Preferences window.
The default Normal format used in the 3D View and nodes using the this property (e.g. Normal, Bevel, etc.) will inherit the value set in the Project settings.

To change it manually in the 3D view, open the Materials menu, then select the Edit option under the Default submenu to display this material's properties, and change the DirectX normal option.

I hope this is helpful!

Best regards,
Luca

42
Hello @bluicat,

Thank you for reaching out to us!

The Alchemist filter template in Substance Designer is only preconfigured with inputs, outputs and a specific value in the User data property of the graph, so it is recognised as a filter in Substance Alchemist.
To use custom filters in Substance Alchemist, you may refer to this page of the software's documentation.

Regarding using SBSAR created using the Alchemist filter template in 3ds Max and Unreal engine with the corresponding Substance integrations (i.e. plugins), please note the template includes image inputs which may need specific actions in the target software to be used properly. See for instance this page about using Substance image inputs in Unreal engine.

Other than that particular precaution, you can use the SBSAR published from these graphs in other software.

I hope this is helpful!

Best regards,
Luca

43
Hello @miccetro,

I am glad! Have fun using the Substance tools!

Best regards,
Luca

44
Hello @miccetro,

Thank you for reaching out to us!

You can refer to my response in this thread for information and recommendations regarding tessellation displacement.

I hope this is helpful!

Best regards,
Luca

45
Hello @aaeriam,

Thank you for reaching out to us!

Some users indeed experience issues when using Substance applications with secondary monitors. These problems are most likely linked to the 3D View's OpenGL rendering instance.

The use of a USB-C dongle is a very valuable piece of information. I will perform some tests on my side and keep you updated with the results. I appreciate your patience in the meantime!

Best regards,
Luca

Pages: 1 2 [3] 4 5 ... 32