Skip to main content
Michael Prais
Known Participant
November 22, 2023
Question

Parameter and Preset presetinput type= definitions in .sbsprs files

  • November 22, 2023
  • 1 reply
  • 130 views

Context:

PROPERTIES > INPUT PARAMETERS > Parameters > Save Default Values to FIle...

PROPERTIES > INPUT PARAMTERS > Presets > Save Presets to File...

 

These operations produce .sbsprs files with XML content that describes Parameter and Preset identifiers

with a name ("identifier"), "type", "uid", and "value".

There appears in my application four "type" values:

0: one value of any "Type/Editor" type (Boolean, Integer, integer2, ...)

1: two values of any "Type/Editor" type

2: did not appear

3: four values of any "Type/Editor" type

4: one, two or four values of any "Type/Editor" type

 

How is type="4" defined?

How is type="4" set in the parameter UI?

Can type="4" be replaced with another type with the same number of values before loading an sbsprs file?

The S3D online documentation says that parameters and presets are Replaced when the identifier and type are matched with that of existing parameters or presets.

Does the uid have any function on input? Can it be eliminated? Can it be used to match?

It appears that Replace Presets with File... does not replace individual, matching preset identifiers. It replaces all preset identifiers eliminating any preset identifiers that did not appear (or did not match) in the sbsprs file.

Is there any way to incrementally replace identifier values?

Any information on the items (type, uid, dependency, ...) in the sbsprs file would be appreciated.

The documentation for these features in S3D is underwhelming!

This topic has been closed for replies.

1 reply

Cyril Dellenbach
Community Manager
Community Manager
November 24, 2023

Hello Michael,

 

Thanks for the questions and the feedback regarding the documentation.

 

I think nobody in the team will disagree with you: the SBSPRS format is not documented, and its use is both unclear and unsuitable.

The answers to your questions require consultation with the engineers. We will provide possible answers in the course of next week.

We'll be documenting the format and its use over the next few weeks, as exhaustively as possible. In the course of this work, corrections and improvements will be collected and passed on to the team.

Best regards,

 

Cyril Dellenbach (Micro) | QA Support Artist | Adobe