You can choose the language in which verbose will be displayed and activate the “Full Debug Verbose” mode in the Interface section of the PredictiveSuite preferences.
The verbose options are defined in the Logging section of the interface preferences.
If the “Full Debug Verbose” mode is activated, you will have more details on the Predictive Engine scene loading steps and the Predictive Unity internal workflow.
The Profiler section of the preferences contains the list of all processes currently rendering. For each process, the following details are listed :
Camera and Sensor : the camera or physical sensor associated with this process,
GUID : the guid of the shared memory associated with this process,
Target : the context in which this processed is used, the target can either be Overlay (used for an engine overlay), Renderer (used in the engine view), or Batch (used for a batch renderer),
State : the current state of this process,
Paths : the paths of the scene and settings files loaded in Predictive Engine,
Stats : the current render time and samples per pixel count for this process,
Scene Structure : the list of Unity elements loaded in the Predictive Engine scene for this process,
Scene Data : the actual data loaded in the Predictive Engine scene for this process,
Buffer : the raw content of the shared memory buffer for this process.
When you start Unity with Predictive Engine, there are three important messages you can look after in the “Console” tab :
When the Predictive Engine process is started for a camera : Starting Predictive Engine Process for camera : **name of the camera**
When the Predictive Engine scene was correctly loaded : Predictive Engine is ready to render
When the Predictive Engine process was stopped for a camera : Stopped Predictive Engine process for camera : **name of the camera**
NB : there should be one “start message” and one “stop message” for each enabled camera in the scene.