Meta Horizon Worlds v133 Release Notes: Introducing a Time Spent Dashboard + Mute Notifications

Meta Horizon Worlds v133 is here! This week’s update includes a new dashboard to view time spent in Worlds and a test to let people know when they’ve been muted. Let’s get into it.

See How Much Time You’ve Spent in Worlds

You can now see how much time you’ve spent in Worlds over the past seven days, including how much of that time was spent on the web and mobile vs. on your Meta Quest headset. Check it out by going to Settings > Safety & Well-being > Time spent.

Quality of Life Improvements

General

• Testing mute notifications to create sound awareness: We’ve heard feedback from our community that unusually loud noises or players with a lot of background noise can be distracting when visiting Worlds—but sometimes it’s hard to know that your microphone may be picking up background sound or if your volume is louder than expected. This week, we’re beginning to test ways to let people know when they’ve been muted by multiple other people around them, so they can be more aware of their sound and turn off their microphone if they want to.
• We removed the total player count on world cards if the world has zero concurrent players.

Highlighted Bug Fixes

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

General

• We fixed a bug where the mute toggle wouldn’t show the option to unmute someone if they’re already muted.
• We fixed a bug where the app load wouldn’t progress when there was no available disk space.
• We fixed an issue where the emote selection menu would visually overflow if someone had unlocked lots of emotes.
• We fixed a bug where clicking on the image of the world in the edit details page would cause travel to fail—it will now take you to the correct world.
• We fixed an issue where some emotes weren’t visible in mirrors or the selfie camera.
• We fixed an edge case in which wearables behaved unpredictably, sometimes attaching to different positions on the player.

Select Known Issues

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

General

• Controller triggers don’t always fire code events if both are clicked at the same time. Creators should take note so that they don't rely on this functionality for anything major in their worlds (e.g., to start a round of a game).
• People’s avatar remains visible in the mirror after they’ve left a world.
• When the user rotates the controllers in their physical hand, the avatar hand rotates continuously.

Creators

• The “when object detaches from player” codeblock doesn’t fire in some cases.
• Worlds with many collaborators sometimes have problems loading their door content.