Table of Contents
Testing Cortext-Ai
This is a living document which will document specific stages of the development of the Cortex-Ai system
Last Updated: 2025-Dec-19 11:58
Stage #1
The webserver code that returns the relevant data for an actor from a JSON data file is 'complete', although it may evolve in the future in line with requirements from the rest of the system.
Stage #2
The Cortex-Ai controller is now fetching data from the server for a single actor, and is spawning that actor where it should be.
As it spawns the actor, it stores its avatar UUID in the linksetData store. It also determines the UUID of the listener attachment (Cortex-Ai Client), and sends it a list of actions.
Stage #3
The Cortex-Ai client (attached to the actor) receives the list of actions and stores the UUID of the controller.
If the action is to animate the actor, the client sends a request back to the controller along with the name of the animation to play. The controller script forwards the animation request to the prim (child link) that stores the data pertinent to the specific actor, including all its animations. The satellite script in the child link plays the animation.
At this point, everything is ready to develop the full set of commands that will puppeteer the actor.
-
Some commands will be enacted by the client script
-
Some commands will be enacted by the satellite script
-
Some commands will be enacted by the controller
Each command must be versioned, and both controller and client versions will be injected into the profile information, so it will be possible to track and control versions and which commands are available.
Discussion