Controls the scale factor of the in-scene debug and profile views.

The default value is 1.0.

Note: This property has no effect when using View3D items in the Qt Quick scene, because the profile views are managed by Qt Quick, not the 3D engine then. Use Studio3DProfiler in that case.

When this property is true, the interactive statistics and profile view is displayed in-scene, on top of the 3D content.

Note: This feature can be disabled at build time, in which case this property has no effect.

Default value is false.

Note: This property has no effect when using View3D items in the Qt Quick scene, because the profile views are managed by Qt Quick, not the 3D engine then. Use Studio3DProfiler in that case.

When enabled, Qt 3D objects managed by the runtime get tracked, and various statistics get collected internally. These are then exposed in the views that can be toggled by profileUiVisible or by having a visible Studio3DProfiler item in the Qt Quick scene.

The default value is false.

Note: Changing the value after the presentation has been loaded has no effect for the already loaded presentation.

Note: In the Qt 3D Studio Viewer application presentations are opened with profiling enabled by default. Therefore, applications wishing to have an experience comparable to the Viewer, when it comes to the debug and profile views, should set this property to true.

Holds the main presentation source (*.uia or *.uip) file location. May be either a file URL or a qrc URL.

Holds a list of (variant group):(variant) tags that are loaded when the source property is set. If this list is left empty (default), no variant filtering is applied and all items are loaded regardless of variant tags in the presentation. Variant mechanism allows one presentation project to contain multiple variants of the presentation and the decision which variant set is loaded is determined during runtime based on the variantList.

Variants are divided to variant groups, e.g. one variant group could be region and the variants within that group could be e.g. US, EU, CH. Another variant group could be e.g. power and variants within that could be e.g. gas, electric, diesel. To filter in this example an electric variant for the EU region, the variantList needs to contain two strings "region:EU" and "power:electric". Also of course the presentation project needs to contain these variant groups and tags applied appropriately to the presentation content.

When variant filters are used, the decision what gets loaded and what is not loaded is based on checking every item in the presentation:

• If the item has no variant tags, it will be loaded.
• If the item has no tags defined for the checked variant group(s), it will be loaded.
• If the item has tag(s) for the variant group, any of those tags must match any of the variants defined in the filter for that group.

If the item doesn't fulfill the above rules it will not be loaded.

This signal is emitted when an action with the Emit Signal handler is executed in the Qt 3D Studio presentation. elementPath specifies the scene object on which the (Qt 3D Studio) "signal" name was triggered.

Connecting to this signal offers a way of reacting upon certain events in the Qt 3D Studio presentation.

In this example, pressing or tapping on the Cluster object will result in emitting customSignalEmitted("Cluster", "clusterPressed").

This signal is emitted when a slide is entered in the presentation. The elementPath specifies the time context (a Scene or a Component element) owning the entered slide. The index and name contain the index and the name of the entered slide.

This signal is emitted when a slide is exited in the presentation. The elementPath specifies the time context (a Scene or a Component element) owning the exited slide. The index and name contain the index and the name of the exited slide.

Dispatches a Qt 3D Studio presentation event with eventName on scene object specified by elementPath. These events provide a way to communicate with the .qml based behavior scripts attached to scene objects since they can register to be notified via Behavior::registerForEvent().

Returns the value of an attribute (property) on the object specified by elementPath. The attributeName is the scripting name of the attribute.

Returns a list of data inputs defined for this presentation as an array.

See also setDataInputValue().

Requests a time context (a Scene or a Component node) to change to a specific slide by name. If the context is already on that slide playback will start over.

If elementPath points to a time context, that element is controlled. For all other element types the time context owning that element is controlled instead. You can target the command to a specific sub-presentation by adding "SubPresentationId:" in front of the element path, for example "SubPresentationOne:Scene".

Requests a time context (a Scene or a Component node) to change to a specific slide by index index. If the context is already on that slide playback will start over.

If elementPath points to a time context, that element is controlled. For all other element types the time context owning that element is controlled instead. You can target the command to a specific sub-presentation by adding "SubPresentationId:" in front of the element path, for example "SubPresentationOne:Scene".

Requests a time context (a Scene or a Component node) to change to the next or the previous slide, depending on the value of next. If the context is already at the last or first slide, wrap defines if change occurs to the opposite end.

If elementPath points to a time context, that element is controlled. For all other element types the time context owning that element is controlled instead. You can target the command to a specific sub-presentation by adding "SubPresentationId:" in front of the element path, for example "SubPresentationOne:Scene".

Sets a time context (a Scene or a Component node) to a specific playback time in seconds.

If elementPath points to a time context, that element is controlled. For all other element types the time context owning that element is controlled instead. You can target the command to a specific sub-presentation by adding "SubPresentationId:" in front of the element path, for example "SubPresentationOne:Scene".

The behavior when specifying a time before 0 or after the end time for the current slide depends on the play mode of the slide:

• Stop at End - values outside the valid time range instead clamp to the boundaries. For example, going to time -5 is the same as going to time 0.
• Looping - values outside the valid time range mod into the valid range. For example, going to time -4 on a 10 second slide is the same as going to time 6.
• Ping Pong - values outside the valid time range ‘bounce’ off the ends. For example, going to time -4 is the same as going to time 4 (assuming the time context is at least 4 seconds long), while going to time 12 on a 10 second slide is the same as going to time 8.
• Ping - values less than 0 are treated as time 0, while values greater than the endtime bounce off the end (eventually hitting 0.)

Sets the value of an attribute (property) on the Qt 3D Studio scene object specified by elementPath. The attributeName is the scripting name of the attribute.

An element path refers to an object in the scene either by name or id. The latter is rarely used in application code since the unique IDs are not exposed in the Qt 3D Studio application. To refer to an object by id, prepend # to the name. Applications will typically refer to objects by name.

Names are not necessarily unique, however. To access an object with a non-unique name, the path can be specified, for example, Scene.Layer.Camera. Here the right camera object gets chosen even if the scene contains other layers with the default camera names (for instance Scene.Layer2.Camera).

If the object is renamed to a unique name in the Qt 3D Studio application's Timeline view, the path can be omitted. For example, if the camera in question was renamed to MyCamera, applications can then simply pass MyCamera as the element path.

To reference an object stored in a property of another object, the dot syntax can be used. The most typical example of this is changing the source of a texture map by changing the sourcepath property on the object selected by SomeMaterial.diffusemap.

To access an object in a sub-presentation, prepend the name of the sub-presentation followed by a colon, for example, SubPresentationOne:Scene.Layer.Camera.

Sets the value of a data input element name in the presentation.

Data input provides a higher level, designer-driven alternative to setAttribute or Element. Instead of exposing a large set of properties with their intenal engine names, data input allows designers to decide which properties should be writable by the application, and can assign custom names to these data input entries, thus forming a well-defined contract between the designer and the developer.

In addition, data input also allows controlling the time line and the current slide for time context objects (Scene or Component). Therefore it is also an alternative to the goToSlide, goToTime, and SceneElement.

As an alternative to this method, the DataInput type can be used. That approach has the advantage of being able to use QML property bindings for the value, instead of having to resort to JavaScript function calls for every value change.