Scene3D QML Type

The Scene3D type is used to integrate a Qt3D scene into a QtQuick 2 scene. More...

• List of all members, including inherited members

Properties

• aspects : list<string>
• cameraAspectRatioMode : enumeration
• compositingMode : enumeration
• entity : Entity
• hoverEnabled : bool
• multisample : bool

Methods

• void setItemAreaAndDevicePixelRatio(area, real devicePixelRatio)

Detailed Description

The Scene3D type renders a Qt3D scene, provided by an Entity, into a multisampled Framebuffer object. This object is later blitted into a non-multisampled Framebuffer object, which is then rendered with premultiplied alpha. If multisampling is not required, it can be avoided by setting the multisample property to false. In this case Scene3D will render directly into the non-multisampled Framebuffer object.

If the scene to be rendered includes non-opaque materials, you may need to modify those materials with custom blend arguments in order for them to be rendered correctly. For example, if working with a PhongAlphaMaterial and a scene with an opaque clear color, you will likely want to add:

sourceAlphaArg: BlendEquationArguments.Zero
destinationAlphaArg: BlendEquationArguments.One

to that material.

It is not recommended to instantiate more than a single Scene3D instance per application. The reason for this is that a Scene3D instance instantiates the entire Qt 3D engine (memory managers, thread pool, render ...) under the scene. You should instead look into using Scene3DView instances in conjunction with a single Scene3D instance.

When using Scene3D with Scene3DViews the following conditions are expected:

• The compositingMode is set to FBO
• The Scene3D is sized to occupy the full window size
• The Scene3D instance is instantiated prior to any Scene3DView
• The Scene3D entity property is left unset

Note: Åšetting the visibility of the Scene3D element to false will halt the Qt 3D simulation loop. This means that binding the visible property to an expression that depends on property updates driven by the Qt 3D simulation loop (FrameAction) will never reavaluates.

Property Documentation

Method Documentation