- Qt 6.12
- Qt 3D
- QML Types
- QtQuick.Scene3D (Deprecated)
- Scene3D
- Qt 6.12.0 Reference Documentation

# Scene3D QML Type

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

Import Statement: | `import QtQuick.Scene3D 2.12`
Inherits: | Item
Status: | Technology preview

This type is in technology preview and is subject to change.

- List of all members, including inherited members

## Properties

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

## Methods

- void setItemAreaAndDevicePixelRatio(size 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 (for example, memory managers, thread pool, render) under the scene.

Note: Setting 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 reevaluate.

## Property Documentation

### aspects : list<string>

The list of aspects that should be registered for the 3D scene.

For example, if the scene makes use of FrameAction, the `"logic"` aspect should be included in the list.

The `"render"` aspect is hardwired and does not need to be explicitly listed.

### cameraAspectRatioMode : enumeration

Defines how the aspect ratio of a camera found in the scene is computed.

Constant | Description
--- | ---
`Scene3D.AutomaticAspectRatio` | Automatic aspect ratio.
`Scene3D.UserAspectRatio` | User defined aspect ratio.

### compositingMode : enumeration

Constant | Description
--- | ---
`FBO` | Scene is rendered into a Frame Buffer Object which can be costly on some platform and hardware but allows a greater amount of flexibility. Automatic aspect ratio. This is the compositing mode to choose if your Scene3D element shouldn't occupy the entire screen and if you optionally plan on having it resized or animated. In this mode, the position of the Scene3D in the QML file controls its stacking order with regard to the other Qt Quick elements.
`Underlay` | Suitable for full screen 3D scenes where using an FBO might be too resource intensive. Scene3D behaves as a QtQuick underlay. Please note that when using this mode, the size of the Scene3D and its transformations are ignored and the rendering will occupy the whole screen. The position of the Scene3D in the QML file won't have any effect either. The Qt 3D content will be drawn prior to any Qt Quick content. Care has to be taken not to overdraw and hide the Qt 3D content by overlapping Qt Quick content. Additionally when using this mode, the window clearBeforeRendering will be set to false automatically.

The default value is `FBO`.

### entity : Entity `[default]`

The root entity of the 3D scene to be displayed.

### hoverEnabled : bool

`true` if hover events are accepted.

### multisample : bool

`true` if a multisample render buffer is requested.

By default multisampling is enabled. If the OpenGL implementation has no support for multisample renderbuffers or framebuffer blits, the request to use multisampling is ignored.

Note: Refrain from changing the value frequently as it involves expensive and potentially slow initialization of framebuffers and other OpenGL resources.

## Method Documentation

### void setItemAreaAndDevicePixelRatio(size area, real devicePixelRatio)

Sets the item area to area and the pixel ratio to devicePixelRatio.