Scenes
A Scene acts as a container for a configuration and can be used to present and visualize individual or multiple products.
Different types of Scenes can be defined for this purpose:
-
An empty scene with a white or colored background, or with an artificial horizon
→ Advantage: Focus on the product
Example: Jovie, E-Line in single configuration -
A scene with a "base surface", where the configurable object is placed.
The surface can either match the background color or visually stand out from it.
It is also possible to use shaders to display surfaces (e.g. grass, water).
→ Advantage: Shadows on the surface, dynamic background makes the product visualization more vivid
Example: Concrete mixer on a white surface, Seabob on water -
A scene with a complete room/environment situation
→ Advantage: Product can be displayed in a contextual and sales-promoting way
Example: Room doors, Jovie in a street scene, lighting in a room
Creating a Scene
By clicking the “Create” button in the CRUD component, a new Scene can be created.
Existing Scenes can be edited or viewed via the “inline icons”.
Fields
-
Code (mandatory)
→ Technical name of the Scene.
Can be freely chosen, but must follow naming conventions and be unique within Scenes. -
Descriptions (optional)
→ Multilingual description of the Scenede_de
= Basis Szeneen_en
= Base Scene- …
Scene-Information Tab (Create)
When creating a new Scene:
- Code is required.
- Description can be maintained in multiple languages.
Actions:
- Save → Create new Scene
- Save → Save changes
Scene-Information Tab (Edit-/View-Mode)
In Edit-/View-Mode:
- Base information of the Scene can be viewed or modified.
- Save
Scene-SceneConfiguration Tab
Here, the SceneConfiguration links the Scene (3D-Customizing) with the corresponding Scene in the Unity backend and defines the central insertion point for the 3D objects.
Creating a SceneConfiguration
By clicking the “Create” button in the CRUD component, a new SceneConfiguration can be created.
Existing SceneConfigurations can be edited or viewed via the “inline icons”.
Fields
-
Code (mandatory)
→ Technical name of the SceneConfiguration.
Can be freely chosen, must follow naming conventions and be unique. -
SceneName (mandatory)
→ Technical name of the Scene.
Must match the Scene name in the Unity backend.
The naming convention should be followed when creating the Scene in the backend.
Example:BaseScene
-
SpawnPoint (mandatory)
→ A SpawnPoint must be selected (which must be defined beforehand underSpawnPoints
).
The SpawnPoint defines the position and orientation of the 3D object in this Scene.
Example:Center
-
Descriptions (optional)
→ Multilingual description of the SceneConfigurationde_de
= Basis Szeneen_en
= Base Scene- …
SceneConfiguration-Tab (Create)
When creating a new SceneConfiguration:
- Code is required.
- SceneName is required.
- SpawnPoint must be selected.
- Description can be multilingual.
Actions:
- Save → Create new SceneConfiguration
- Save → Save changes
SceneConfiguration-Tab (Edit-/View-Mode)
In Edit-/View-Mode:
- Base information of the SceneConfiguration can be viewed or modified.
- Save