Messages

31

Substance Automation Toolkit - Discussions - Re: SBSRender Multiple .sbsar

 on: January 20, 2019, 05:17:32 pm 

Hi,

In order to solve this you need to make some kind of script (python or batch file) to find all the files and invoke sbsrender on each of them.
If doing it using python I would recommend you look at either the os.walk function:
https://www.bogotobogo.com/python/python_traversing_directory_tree_recursively_os_walk.php

or glob:
https://docs.python.org/2/library/glob.html

32

Substance Automation Toolkit - Product Support - Re: pysbs - sbsenum input node enumerations unavailable?

 on: January 11, 2019, 09:31:17 am 

The real fix will accept non-standard input usages (i.e you'll provide a string instead of an sbsenum.UsageEnum). Yhere is an issue with the API for creating inputs at this point.

What I'm showing in my code example is a workaround to solve any emergencies for now, hopefully you'll be able to pass a string in directly in the next release.

33

Substance Automation Toolkit - Product Support - Re: pysbs - sbsenum input node enumerations unavailable?

 on: January 10, 2019, 07:09:25 pm 

Hi,

I'm sorry for your inconvenience. We'll make sure custom inputs are supported in the next release.

My workaround for the issue looks like this:

from pysbs import context
from pysbs import sbsgenerator
from pysbs import sbsenum
sbs_context = context.Context()

sbsDoc = sbsgenerator.createSBSDocument(sbs_context,
                                        aFileAbsPath='input_usage.sbs',
                                        aGraphIdentifier='Composite')

aGraph = sbsDoc.getSBSGraph(aGraphIdentifier='Composite')
input_node = aGraph.createInputNode(aIdentifier='Test',
                                    aColorMode=sbsenum.ColorModeEnum.COLOR,
                                    aUsages={sbsenum.UsageEnum.BASECOLOR:{sbsenum.UsageDataEnum.COMPONENTS:sbsenum.ComponentsEnum.RGBA,
                                                                           sbsenum.UsageDataEnum.COLOR_SPACE:sbsenum.ColorSpacesEnum.LINEAR}})
input_param = aGraph.getInput('Test')
usages = input_param.getUsages()
usages[0].mName = 'banana'
sbsDoc.writeDoc()



The usage is set on the input_param on the graph rather than the actual input node.

34

Substance Automation Toolkit - Discussions - Re: SBSCOOKER Application is too old to open URL

 on: January 08, 2019, 02:26:53 pm 

Do you have any aliases in your sbs file? Those need to be specified using the alias flag

35

Substance Automation Toolkit - Discussions - Re: substance automation toolkit updata schedule?

 on: January 08, 2019, 02:25:52 pm 

Hi Sum,

Sorry for the delay. It's finally out.

36

Substance Automation Toolkit - Product Support - Re: SBSBaker output-size issue

 on: December 12, 2018, 06:59:34 pm 

I know we did change the command line parser somewhere in the process.
What might be the case is that we only baked square textures in the past, can you try passing in only 10 (as opposed to 10,10) and see if it works for you?

37

Substance Automation Toolkit - Discussions - Re: substance automation toolkit updata schedule?

 on: December 10, 2018, 01:20:25 pm 

It should be a few days out.
Code is working, just some formalities to clean up.
Sorry for the inconvenience

38

Substance Automation Toolkit - Product Support - Re: SBSBaker output-size issue

 on: December 03, 2018, 03:57:13 pm 

Hi Andrei,

That looks like a correct command line to me and my attempt to recreate it seem to work for me.
Can you try quoting the 10,10 and see if works, I'm worried that somehow the shell is interpreting the 10,10 incorrectly.

C:\Program Files\Allegorithmic\Substance BatchTools 5> .\sbsbaker.exe ambient-occlusion-from-mesh --output-size "10,10" "C:\Users\Merle Boule\Desktop\ATKit\test.FBX" --output-path "C:\Users\Merle Boule\Desktop\ATKit"

David

39

Substance Automation Toolkit - Product Support - Re: Error - Baker not available

 on: November 23, 2018, 09:47:40 am 

Hi Eric,

This is a sign of missing a modern enough OpenGL to run the baker.
What platform are you on, there are workarounds but they depend on what OS you are on.

David

40

Substance Automation Toolkit - Product Support - Re: Substance Automation Installation issue - error2

 on: November 23, 2018, 09:45:20 am 

This is concerning.
The user document directory is where we install samples to make sure they are in a writable location.
Can you send us any logging information from the installation to see if we can figure out what is going wrong.
PM me if you want a different installation solution as a workaround and I'll do my best to help out.

David

41

Substance Automation Toolkit - Product Support - Re: Substance Automation toolkit Installation and license setup

 on: November 23, 2018, 09:42:36 am 

Hi,

The SAT runs independently of Substance Designer. The installation process is outlined here:
https://support.allegorithmic.com/documentation/sat/setup-and-getting-started

On linux it means:
Unpack/placing the binaries/assets in the place you want it
Use pip to install the python API in your python environment
Potentially set PATH and various Environment variables for the users in order to make the command line tools available and help the SAT to find the resources.

Let me know if you run into anything specific you need help with

42

Substance Automation Toolkit - Product Support - Re: SBSDocument.write save sbs file problem

 on: September 28, 2018, 06:04:07 pm 

Hi Sum,

This is unfortunately a known bug. It will be fixed in the next release. PM me if you need a hotfix for it.

David

43

Substance Automation Toolkit - Discussions - Re: Textures processing

 on: September 28, 2018, 06:01:49 pm 

Hi,

It should be a pretty easy process using sbsrender.
Look at the variations sample for some inspiration.

Regards
David

44

Substance Automation Toolkit - Feature Request - Re: Render 3D View

 on: September 04, 2018, 06:24:45 pm 

Hi Jon,

There is finally an example showing how to do a little bit of this:
https://github.com/AllegorithmicSAS/sat-scons

It uses arnold or appleseed to render material samples and it should be possible to repurpose it for your needs.

45

Substance Automation Toolkit - Discussions - Re: Issue modifying variations.py example

 on: September 04, 2018, 06:22:47 pm 

It's likely to be related to packages directory and aliases and you have discovered.
For full compatibility the packages path should be the same as used by SD when you author the sbs