Output spam when enabling Spatial Voice

Reproduction Steps
Go to game settings → Options → Enable Spatial Voice and play the game (either in studio or live) on an account that does not have spatial voice enabled

Enabling spatial voice causes very verbose output spam which makes it impossible to debug and could potentially cause lag for the end user in some scenarios?

Expected Behavior
Output should be completely silent whether or not a user has spatial voice enabled

Actual Behavior
There are very long Roact errors that spam the output along with an intrusive message saying "Current Player is not elligible to use spatial voice

Workaround
Don’t enable Spatial Voice in your game

Issue Area: Engine
Issue Type: Other
Impact: High
Frequency: Constantly
Date First Experienced: 2021-09-23 00:09:00 (-06:00)
Date Last Experienced: 2021-11-11 00:11:00 (-07:00)

12 Likes

Thanks for the report! We’ve filed a ticket to our internal database and we’ll follow up when we have an update for you.

6 Likes

Seems like it happens even with Spatial Voice disabled for my games, Maybe to do with the account having VC enabled?

3 Likes

We are also experiencing this in all of our games that have spatial voice enabled. Takes longer to understand both game and studio output when searching for potential bugs.

3 Likes

Hello there!

I believe that I’ve identified the core issue for this problem in experiences. The problem that I’m seeing is an unstable Core Package (ReactReconciler) was merged into the main client branch recently. The issues shown here were unintended and were not supposed to appear.

The only way this can be fixed is if ReactReconciler and the other React packages are moved out of the main branch until they are ready to be merged back. Otherwise, team members can simply just make quick fixes to these issues.

I’ll wait for an official response from Developer Relations on this one though.

3 Likes

I am getting these warnings on a place that is not even published

image

2 Likes