About

In-editor utility that provides a bridge between backstage data and editor GUI. Provides base UI controls to manage environmental shell and embeds external debug tools into itself as a uniform hub.

More in this category:

How to ...

Start environment

Navigate to Doloro GDK menu at the top of your editor. In some version or along with a platform requirements menu item can be located within Tools directory.
Select DAI Debugger item.
Dock the window somewhere in editor where you are considering it most comfort to you.

Make sure that a left-top switch button means On in the DAI Debugger window colored in red (record). In case if it is gray and contains Off label, press it to turn-on environment tracking.

Stop environment

In opened DAI Debugger window press the On button colored red to disable environmental shell execution. After that the shell will stop Doloro AI Core events handlers till turn op back.

Add AI instance to debug shell

All the Brain instances connected to the debug shell and not demands any extra actions from you. But some of deep features could work for them on partial way. That's normally goes to high-weighted console logs call or other internal operations causing significant time loss.

Exclude AI instance from debug shell

When the environment shell is enabled, you can't exclude a single instance from the whole. You can only adjust extra tracking features by managing of Debug deep state of the instance.

How to: Change debug tracking deep

Change debug tracking deep

To start deepest analysis of an instance you must change its tracking depth settings parameter.

For this:

Select the instance game object in Scene Hierarchy window.
At the Brain component navigate to the Tracking block.
Here you should select Tracking depth option to state of your following purposes.

State	Activity
None	DEFAULT Any high-weight debug operations that going along with internal rule are blocked.
Shallow	Only most important operations will be called during AI graph execution.
Deep Warning Could cause significant FPS loss.	All operation focused on debug, tracking or analysis purposes will be permitted.

Track AI's call stack

During Play editor mode you can take a look inside execution process of each tracking instance of AI. For this you should open DAI Studio or an analog (if provided) and select target instance in scene's hierarchy.

After the instance has been connected to the studio you can find entire AI's pipeline map tree with state highlights for each member.

Warning: Depending from implementation different color of member's GUI representation may means different state. Following list is recommendation following with package included utilities.

Color marks legend (by default)

green means that the node has been computed with Result.Success.
red means that the node has been computed with Result.Fail.
yellow means that the node has Result.InProgress state and continue its execution at next step.
gray or absent mark means that the node has not been included to current execution queue.

Exam certain node

Base Doloro-AI-Inspector module implements several extension for the debug environment. The extensions available in normal inspector during selection of any node at DAI Studio or any other supportive editor.

History tab

Tab that tracks last received Results at the node. Allows to backtrack results after a new root execution session has been started.

Debug tab

Provides node related settings related to the node scope. Also provides statistic data about last node call.

Debug several AI instances

The environment shell recording data of entire AI instances at scene separately. Even if an instance currently offline from an editor like a DAI Studio it not losses it's session data.

You may switch between instances under the focus in any time to get access to its session.

Table of Contents