1.3.2.2

Release notes for version 1.3.2.2 - 21-Oct-2024

The following new features are available in this version:

Enhancements to the Psychological Evolution API endpoint

We have enhanced the Psychological Evolution API endpoint to provide you with clear indicators of VHs' psychological evolution based on the following factors:

• Psychological well-being

• Mental well-being, based on the following components:

  • Anxiety

  • Level of stress

  • Self-knowledge

  • Aggressiveness

  • Creativity

  • Social skills

  • Openness to change

  • Level of inhibition

• Personality evolution

You can also filter the results by session, triggered action, and entity (VH), and limit the number of results retrieved.

For detailed reference documentation for this API endpoint, see Analyze the psychological evolution of VHs during a simulation.

Tier-based data limits

To enable Orchestra to deliver fast and reliable EDAA™ services specific to your entities, we have implemented data maintenance protocols and limited the availability of functionalities based on your tier. This improves our response time and performance.

Ability to create input interaction channels based on environmental objects

You can create an input interaction channel based on any object in the simulation environment.

To do this, you can create channels of the new type, object. For this type, the value parameter is optional.

This feature enables you to notify EDAA™ about events that don't require a response from it. For example, you can inform EDAA™ about an VH's movement.

You can also condition interactions based on the value of objects (by configuring input interaction channels of the object type as logic conditions). For example, you can set up a condition that interactions wouldn't occur if the light intensity or sound volume exceeds a specified threshold.

To perform interactions using interaction channels of this type, you need to provide at least one object in the object_statuses array (by entering its name and value).

Additional validations and improved error handling

To improve your experience in working with Orchestra APIs, we have added additional validations at different stages and included relevant HTTP 400 errors, complete with standardized error codes and descriptive messages, to help you debug your issues.

For the complete list of error codes and messages and their detailed explanations, see Error messages.

When performing an interaction, the following validations are available:

• If the interaction session belongs to an Entity ID of type Environment, the following validations are performed:

  • We check whether the source entity ID has been provided. If it wasn't provided, error message ER0028 is displayed.

  • If the source entity ID was provided but the entity was never summoned before, error message ER0052 is displayed.

  • If the source entity ID was provided and the entity was summoned earlier, we validate whether it has a non-null User ID. If it doesn't, error message ER0053 is displayed.

  • If the source entity ID was provided, summoned earlier, and has a non-null User ID, we check whether diagnostics were completed for it. If it wasn't, error message ER0054 is displayed.

• For voice interaction types, we validate whether a valid base64 value is provided for the interact_value parameter. If it isn't, error message ER0015 is displayed.

• We validate whether the interaction session has already ended. If it has, error message ER0058 is displayed.

Support for retrying connection requests from gRPC clients

During a connection request from a gRPC client, if the required service is not found or unavailable, the connection is automatically retried thrice. An error is displayed only if it is still unsuccessful.