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 - rosalie.martin_1

Pages: [1]
1
Hi Julien,
To provide several entries you can feed a list to the parameter 'set_entry', in your case this should work:
batchtools.sbsrender_render(inputs=dir_path+'AutomationTest.sbsar',
                           output_format='png',
                                    input_graph="AutomationTest",
                                    input_graph_output="outputTexture",
                                    output_path=dir_path+'output/',
                                    output_name='test',                                   
                                    set_entry=['refTexture@'+dir_path+'ref.png','inputTexture@'+dir_path+'ref.png']
                                    ).wait()


Per your second question, are you talking of the parameter output-bit-depth that is available when calling "sbsrender render " command ?

2
Hi,

The error is indeed not as clear as it could be, but sbscooker needs to know where the packages coming with SAT installation are, using --include argument, for instance:
sbscooker.exe "C:\Users\MyName\Documents\Allegorithmic\Substance Automation Toolkit\Sbs\YourSbs.sbs" --includes "C:\Program Files\Allegorithmic\Substance Automation Toolkit\resources\packages"

3
Hi NevTD,

The '$' must be used only for predefined variables (such as $outputsize), but for a user defined parameter you must omit it.
And the color is a float parameter, so you should put values in float in the range [0,1].
This should work by instance:
-set-value 'leather_color@0.3,0.5,0.2'

Rosalie

4
Hi dukecg,

Could you send me your Substance in PM, and provide me the exact command you are executing ?

Thanks !
Rosalie

5
Hi,

Files created with a newer version of Substance Designer cannot be processed by an older version of a batch tool (here sbscooker).
You need to process them with a compatible version of sbscooker (this executable is available with your Substance Designer 2018 installation)

6
Hi,

Here is a sample command of sbsupdater, with the declaration of the default packages path, and of an alias:
sbsupdater --input <PathToTheSbsToUpdate> --output-path {inputPath} --output-name {inputName}_updated --presets-path <PathToTheDefaultPackages> --alias myalias://<PathToTheAliasedFolder>

More information here:
https://support.allegorithmic.com/documentation/display/SAT/sbsupdater+command+line+options

Rosalie

7
Hi ryod,

Not very user friendly indeed, the Output(s) computation option corresponds to the "disabled" tag present in the "root" tag of a "graph" in the .sbs file:
<graph>
  ...
  <root>
    <disabled v="1"/>
    ...
  </root>
</graph>

In Pysbs, once you have created a SBSDocument on the concerned .sbs, parsed it, and get the SBSGraph you want to edit, you can do:
my_graph.mRoot.mDisabled = '1'

8
Hello and sorry for the late reply.
I don't see what could be causing a crash without raising an exception.

Are you able to launch the original demo you copied from Pysbs ?
You can launch it from the demo folder installed in <PythonInstallFolder>/Lib/site-packages/pysbs_demos (be sure to have admin rights, or copy the entire folder elsewhere):
python demos.py -fct: demoExportWithDependencies -args: "sample/argsDemoExportWithDependencies.xml"

If yes, have you tried your script with another substance ?
Could you provide the substance you are trying to open, with its dependencies if any.

In all the cases, could you give us details on your configuration: OS, Python version, SAT / Pysbs version.

Thanks

9
Hello, thanks for including the solution.

When you will be writing your own script, if you don't want to declare an environment variable you can also declare the installation path of Substance Automation Toolkit once, at the beginning of your script, using the static function:

Context.setAutomationToolkitInstallPath("/opt/Allegorithmic/Substance_Automation_Toolkit")

10
Indeed, createIterationOnPattern was not designed to handle input nodes so the uniqueness of input identifier is not checked, but this could be seen as an issue, and we should fix it.

However, when you create an input/output node, the API, as SD does, ensures that you have unique identifiers and add a suffix to the provided identifier if necessary. So you can have a loop for creating input nodes without caring for unique identifiers on your side.

Pages: [1]