Meta Horizon Worlds v174 Release Notes

|
|

Meta Horizon Worlds V174 is here! This week’s update includes a new quality of life improvement that will help you know whether your microphone is on or off when speaking, along with a handful of bug fixes.

Quality of Life Improvements


Introducing Microphone Indicator


We’re beginning to roll out a new microphone indicator in Worlds to help you see your microphone status while speaking.

When your microphone is set to OFF, an icon will show up on the left side of your screen showing that your microphone is muted. If your microphone is ON, the icon will indicate that the microphone is unmuted. In VR, the microphone indicator will only appear while you are speaking, but when exploring on mobile or browser/web, the microphone indicator will remain present even when you are not speaking. This feature will be turned on by default but you can choose to disable it from the Sound settings tab.

For more information on microphone and mute settings in Horizon Worlds, please visit the Meta Help Center.

Highlighted Bug Fixes

Here are some highlighted bug fixes for this week’s release.

General


  • Fixed a bug in which the confirmation screen would not display properly after reporting a user for "profile, name, or bio.”
  • We fixed a bug where users entering or exiting a world could sometimes break the menu for creators managing people in the world.

Creators


  • We fixed a bug where scaling the Create menu in Edit mode sometimes made it too small to grab the top bar.

Select Known Issues

Here are some of the known issues the Worlds team is currently investigating.

General


  • Recording or casting while playing can cause Horizon Worlds to crash when using Meta Quest 2.

Creators


  • Grabbable objects that are set to force grab and transfer ownership when a player enters a trigger do not work the first time, but further attempts are successful.
  • Some creators cannot see worlds where they are collaborators in the Collaborations: Editor list.
  • Accessing player location and other player data in an OnPlayerExitWorld event handler can cause the world to crash.
  • Attaching a script to an entity or editing its script will change the motion property from “None” to “Animated.”