Help Topics Version 2.0

Performance Tweaks

A few property settings allow you to influence the performance of your multi-touch scenario: Preload, Unload on hide and Unload Behavior. These settings can be found in the Advanced section.


Preload is a Scene component property. If Preload is active, all components in the scene will be loaded into memory when the projects loads. This also applies to invisible components.

When to use

Use this option to achieve smooth transitions when cross fading scenes. Note that preloading scenes may require a lot of memory. If the available system memory is insufficient, the system can stall.


Unload on hide must be deactivated for the scene and for all components that are to be preloaded. Components with Unload on hide active will not be preloaded.

Unload on Hide

Unload on hide is an Advanced property available for each component. If Unload on Hide is active, the component will be unloaded from memory when hidden. This saves memory, but requires the component to be loaded again when shown.

When to use

Use this option to free up memory when components are hidden. This mode is particularly recommended for Mac minis and for scenarios with a big memory footprint.


The following tables show the priority of Unload on hide settings. The first table shows that an activated Unload on hide setting of a Scene component overrides a deactivated Unload on hide setting of its child component.

Unload on Hide Memory Action
Media Player 1 TRUE UNLOAD
Media Player 2 FALSE UNLOAD

The second table shows that an activated Unload on hide setting of a child ignores a deactivated setting of a parent Scene component.

Unload on hide Memory Action
Media Player 1 TRUE UNLOAD
Media Player 2 FALSE KEEP

Unload Behavior

Unload Behavior is a Scene component property that affects all children of a scene. It determines how long a component will remain in memory when being rendered invisible. There are three modes available that are shown in the following table:

Mode Unload Time (sec.)
Immediate 0.1
Medium 1
Slow 3

When to use

Use Immediate for systems with low performance and scenarios with a large memory footprint, for instance due a large number of videos and images, or due to videos and images with a high-end resolution. Immediate will ensure that memory is cleared most effectively. Especially when switching between scenes, this mode prevents components from multiple scenes jamming the memory.

Use Slow mode if the component‘s visibility is toggled frequently (less than 3 seconds). In this case, it's a good idea to keep the component in memory and not to unload and reload it on each individual visibility toggle event.


Only components with Unload on hide active will be effected by the Unload Behavior setting.

© ~sedna gmbh 2016