> For the complete documentation index, see [llms.txt](https://documentation.virtuedeep.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.virtuedeep.tech/whats-new/release-notes/1.3.2.3.md).

# 1.3.2.3

Release notes for version 1.3.2.3 - 28-Oct-2024

The following new features are available in this version:

## Ability to view the number of perceptions a VH required for evolution

A new integer type response parameter, `perceptions`, is available for the Psychological Evolution API to help you gain additional insights about psychological evolution.

If an evolution is observed, this parameter, which is nested in the `sessions` array in the response, displays the number of perceptions that the respective Virtual Human (VH) experienced.

For detailed information, see [Analyze the psychological evolution of VHs during a simulation](https://documentation.virtuedeep.tech/guides/using-the-public-apis/creating-managing-and-performing-interactions/analyze-the-psychological-evolution-of-vhs-during-a-simulation.md).

## Ability to share users and VHs across projects

You can summon and interact with users and VHs from different projects of the same tenant.

To facilitate this, we have added a new **required** parameter, **ProjectID**, to the `Interaction/SummonNPC` API endpoint, in which you must enter the project ID of the VH that you want to summon.

For API documentation, see [Summon a VH](https://documentation.virtuedeep.tech/guides/using-the-public-apis/creating-managing-and-performing-interactions/summon-a-vh.md).

{% hint style="info" %}
Entering the project ID is no longer mandatory for the following endpoints of the `DestinationEntity` API:

* `CreateEntities`
* `GetAllEntities`
* `UpdateEntity`
* `DeleteEntity`

When calling these APIs, passing values for the `ProjectID` parameter does not serve any purpose.

For API documentation, see [Creating and managing entities](https://documentation.virtuedeep.tech/guides/using-the-public-apis/creating-and-managing-entities.md).
{% endhint %}

## Performance improvements

We have enhanced our APIs and microservices to optimize the performance and response time of the following events that occur during bulk simulation:

* Starting data augmentation
* Summoning VHs

## Additional validation 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](https://documentation.virtuedeep.tech/guides/using-the-public-apis/getting-started/error-messages.md).

The following validations are available:

* After the raw data collection (RDC) event is completed, before starting data augmentation for bulk simulations, we validate that the RDC included a minimum of 100 stages. If it didn't, **ER0088** is displayed.
* When summoning VHs, first, we validate that the VHs aren't offline (killed). If you try to summon an offline VH, **ER0084** is displayed. Then, as you can directly use an VH that is active and online without summoning it again, if you try to summon an active VH, **ER0085** is displayed.
* To help you avoid incorrectly summoning and using VHs in interactions, we have also included a number of new validations and corresponding errors related to specific incorrect use cases.\
  For example, we validate if you are trying to perform an interaction with a VH that was never summoned, if you entered an invalid entity ID for a VH, and more.
