2023.1.1344.2 Actor

1 Overview
2 Where to find
3 Feature Layout
4 How to use

Overview

The Actor is the base class that should be used for all objects in a DES application that execute behaviour over time. Actors are managed by the DESController and may interact with Cues (which in turn triggers Instructors to apply new behaviour to the Actor) and other Actors.

Where to find

There is currently no menu option for the Actor class, since the user must always create their own custom Actor class that inherits from the base class.

Feature Layout

The image below shows the complete feature layout of the Actor base class. Note that the layout may change depending on the custom implementation.

Transform Settings
Use Rigidbody	Toggle to enable or disable the rigidbody component of the participant
Transform Precision	Calculation precision of the participant. Either Float or Double
Specifications
Participant ID	ID of this Actor for reference within the DESController
Active in Simulation	Toggle to activate or deactivate the Actor for the running DES simulation.
Activity State	Awake: The Actor is currently executing behaviour and is being actively managed by the DESController Asleep: The Actor is currently not doing anything but can still be managed by the DESController when needed
Debugging
Verbose	Toggle to log debugging messages in the console
Report All Activities in Inspector	Toggle to show which activities are being executed by the Actor within the Inspector

How to use

The Actor can only be used by manually creating a script that inherits from DESActor. Any and all behaviour that should be executed by the Actor for a specific implementation, must be written by the user. Note that in most cases, custom Instructor scripts must also be written.

Once these scripts are finished and added as components to GameObjects in the scene, they should be placed under a DESController in the scene hierarchy. The DESController will manage the behaviour of Actors and Instructors during runtime.