The application may be used without visual interaction, for scripted or batch operation. This allows for setup using the menus, achieving settings you desire, then repeating the process without further interaction. The session file is a standard, simple .pdf3dsettings XML format, which allows it to be edited or even created by external software, which can then invoke the application within a script. For more sophisticated server generated work-flows, we recommend pdf3d.io, which goes well beyond features of PDF3DReportGen.
The expected calling sequence is:
PDF3DReportGen -state filename.pdf3dsettings -silent
where filename.xml is ReportGen's state file, which includes defined export scene parameters. The inclusion of -silent is necessary to run the conversion without launching the user interface.
To show dialog with description about ReportGen's expected calling sequence:
$PDF3DReportGen -help
Data paths inside the XML state files can be absolute, or relative to the statefile location. Also, output paths can be prefixed with %TEMP%, which will map to typical temporary file locations on all platforms, known to have write permissions.
Please note, command line usage behaviour in ReportGen has changed in V2.24. In previous versions, it was possible to define interface from command line, e.g export scene using parameters defined in test1.xml by using GRD Interface:
$PDF3DReportGen -state test1.pdf3dsettings -silent "GRD Interface"
For V2.24, the option to set interface from command line has been deprecated. Instead, users should check that their preferred interface is defined within their .pdf3dsettings file using the <PreferredInterfaceName value=""/> tag within AssemblyProperties and DefaultAssemblyProperties.