ChilloutVR 2026r182 Hotfix 1

Changelog

• Avatars are now put into a normalized IK pose before being configured for wearing
  • This addresses an issue where avatars which were not uploaded facing world forward would calibrate incorrectly for some game systems that initialized before IK calibration (like self portraits face tracking)

• Being immobilized no longer pushes you out of your current movement state
  • This addresses switching worlds kicking you out of flight mode

• Exposed button hold wait timer value as a property
• Fixed BetterScheduleSystem to include the overshooting time when running each frame (results in steadier timing for recurrent tasks)
• Fixed content details and full image button images disappearing in some cases
• Fixed group owner avatar image url for when the group owner is not in the instance
• Fixed video player audio sources which were not enabled by default not playing once enabled
• Refactored CVRTexturePropertyParser:
  • Fixed backing color native array for bound global textures being leaked
  • Fixed disabling a CVRTexturePropertyParser gameobject not removing it from processing
  • Reworked global texture binding to share resources in the case multiple parsers use the same texture (like _AudioTexture)

• Refactored how immobilizing the local player works so multiple systems can call for immobilization without conflicting and resetting each other
• Reimplemented the native crash bandaid for remote avatars animating a camera off on first frame
• Reworked CVRGlobalShaderUpdater internals:
  • Globals set by this component are now reset on world unload
  • Fixed disabling a CVRGlobalShaderUpdaters gameobject not removing it from processing
  • When multiple updaters drive the same global texture, the first enabled updater will always take priority. If the active updater is disabled, control will automatically transfer to the next eligible updater.
    • This fixes CVRTexturePropertyParser not behaving as expected in Viviklub

• Reworked UILib click handling to better handle onheld and event handling, should generally work better and not have additional sound effects going off
• The default AAS profile is now applied on avatar load on remote clients
  • This is the case for the local client already, but remotes would sit in their animator default state until first inbound AAS packet. This change should hopefully address the last case where avatars would briefly load in as an undesired/unknown state for the non-wearer.