[Beta] Ver 2.3.1a Updated to Unity 2022

27 Oct 2022Developer post

Overall

As announced earlier in the service development progress briefings, we made an update on the base system.

Updated Unity to version 2022.
Changed the rendering system from the Built-in Render Pipeline to the new Universal Render Pipeline.
We introduced and explained these updates in detail in the service development progress briefings held on 22 June 2022 and 28 September 2022.
- For information on the new rendering system, refer to here (Japanese).
- For the update to Unity 2022, refer to here
If you find a bug that seems to be caused by the system update, please report from here (Japanese).

When you reload a VCI, the ring menu will now go back to the item list menu. This will solve the issue where different VCI might spawn in cases between when you create a new item and reload an existing one.
Adjusted the design on the calibration scene.
Optimized the memory management around the photo capture.
Improved the stability of the server when using the RUDP.

Fixed the issue where you couldn't touch other avatars' SpringBone.
Fixed the issue where the column height setting reset to default when you select a "Next" button in the media history menu.
Fixed the issue where the scroll position resets when you select a "Next" button in the media history menu.
Fixed the issue where returning the ring menu by pressing the menu button after opening the media history will cause a certain thumbnail to not display.
Fixed the issue where some of the transform information is not saved when you leave a room right after you moved a subitem.

Added ExportTransform.GetAttachedPlayer to VCI script, which will get the player id of the attached target of an attachable subitem.
- This API will return different user Ids in rooms and studios even if the user is the same.
- It also returns null when the ExportTransform is not Attachable or not attached.

For ExportAssets.GetTransform in VCI, when you specify a name that starts with "/," the name will be considered as a path starting from the VCIObject.
- For details, please see the reference in the wiki (Japanese).

Fixed the issue where the velocity was not appropriately applied when you used SetVelocity(Vector3.zero) on a character from VCI.

In the room settings, the property "The user who can change the location" is removed. From now on, the owner and the administrators will have the static location change permission.