Skip to main content

SceneComposer Usability Improvements

Integrate Appearance Templates

A set of appearance templates was introduced in the default solutions for OpenGL 2.0 and OpenGL 3.0 platforms. Those templates will be available only in the newly created solutions.

Migration: in order to make the templates available in solutions converted to 3.2.0, one can import them via "Import from solution" option. The appearance templates solutions can be found in SceneComposer\Data\AppearanceTemplates.zip.

The file must be first unzipped in a preferred location in order to reveal the two folders which contain the solutions for OpenGL 2.0 and OpenGL 3.0 (Mantis 6421).

Executable Generation

A new feature is available in the toolbar as a plug-in which will provide the option to generate the asset files and run a script with certain commands defined by the user.

The user is able to define as many configurations as necessary, each configuration containing a set of default parameters, a set of custom parameters and a script to be run after a successful asset generation. Long lines can be broken by using the caret (^). The script is not mandatory and it can contain references to the default and custom parameters defined by the user. The set of custom parameters are specific for each solution and are saved in

USER_DIR\ AppData\Roaming\SceneComposer\Solutions.

(Mantis 6232).

See also:

Control Handles for cubic Bezier

A new editing mode will be available in the Curve Editor: "Pair editing". This mode will apply only in case of Bezier interpolation. It will be available through a toggle button "Enable control points pair editing". The button will be available when at least one animated property within the selected ones has Bezier interpolation (Mantis 6268).

See also:

Scripting

Scripts can now be added to a solution. SceneComposer offers a script editor, similar to shader editor. Scripts, written in the LUA programming language, can be "validated" by pressing F8 or by selecting Validate Script from the Script menu (Mantis 6042).

See also:

Automatic Imports

The user can configure monitored folders for automatic imports - both images and fbx files (Mantis 6302).

See also:

Transitions. Rule Editor

The Rule editor allows the designer to define rules on how to handle transition requests (Mantis 6144).

The user will be able to:

  • Create new rules or remove rules. Filter the rules to quickly find the desired rule.
  • Ordering the rules by drag and drop a rule or using the up and down icons from the beginning of each row which correspond to a transition rule.
  • Defining a specific source object or "any"-identifier for each rule (AnyScene2D, AnyScene3D, SpecificScene2D, SpecificScene3D, AnyNode2D, AnyNode3D, SpecificNode2D, and SpecificNode3D).
  • Optionally defining a destination identifier/object for each rule.
  • Defining a hint for each rule.
  • Optionally adding hint details. The user will be able to enable/disable the fade, enable/disable the Fade Timeline, set the Fade Timeline.

Enable 8 Byte Alignment of Bitmap Pixels Data in Asset

SceneComposer provides now a solution option, "Enable 8 byte alignment of bitmap pixels data in asset", to enable bitmap pixel data alignment to a position multiple of 8 in the asset file (Mantis 6408).

See also:

Minor Improvements

  • Linking Compatibility Guard SCHost.lib can no longer be linked with an incompatible SCHost.dll. Compatibility checks have been added, upon build a suggestive linker error will show up (Mantis 5735).
  • Removed Property LayoutingRectangle property was removed. Solutions of older versions are updated during conversion process (Mantis 6401).
  • Handling of Dynamic Layout Properties Dynamic properties that propagate value (have PropagatesValue flag), are written into the asset when they have default value. Currently, LayoutDirection property has such a flag and obeys this rule (Mantis 6380).
Back to top