Bug Reports

I use push to talk in SteamVR advanced settings, and ever since the new patch for some reason when I use push to talk and finish speaking, the mic icon is still lit up like a second or two after I'm finished speaking. I tested to see if it was still recording my voice after I let go of my push to talk button, and even though the mic icon was still lit up 2 seconds after I let go of the push to talk button, my visemes weren't activating when I let go of my push to talk key. So it just seems to be a visual UI error? Either way this wasn't happening before. I can record a video of what I'm talking about if needed, although hopefully others are experiencing this same issue and it's not just me ;_;

Unsure if isolated to the beta, but I have been in a world for a few hours and noticed the friends list in not only the wing but the social tab as well weren't updating. Shows friends still online that I know aren't and old locations in the wing tab.

When using the Standard Shader on an avatar with all correct textures assigned, The Shader Fallback System seems to ignore the Mettalic/Smoothness Texture and use the Slider value directly resulting in a Shiny Avatar.

What is expected: A shader with all the same properyu names as Unity Standard would have the associated values get mapped correctly when shaders are blocked. What happens: Not all are properly passed on, such as _MetallicGlossMap and _SpecGlossMap, when shaders are blocked, resulting in an incorrect material configuration. Here is a list of the main inputs for the unity standard shader included with unity 2018.4.20 half4 _Color; half _Cutoff; sampler2D _MainTex; float4 _MainTex_ST; sampler2D _DetailAlbedoMap; float4 _DetailAlbedoMap_ST; sampler2D _BumpMap; half _BumpScale; sampler2D _DetailMask; sampler2D _DetailNormalMap; half _DetailNormalMapScale; sampler2D _SpecGlossMap; sampler2D _MetallicGlossMap; half _Metallic; float _Glossiness; float _GlossMapScale; sampler2D _OcclusionMap; half _OcclusionStrength; sampler2D _ParallaxMap; half _Parallax; half _UVSec; half4 _EmissionColor; sampler2D _EmissionMap; If present in a blocked shader these should be mapped to Unity Standard.

PCVR through Virtual Desktop on Quest Pro and Quest 3. The hand-tracking feature seems to work well (aside from opening the SteamVR menu every time you try to open the VRChat menu), but the inability to switch between using controllers and using hand-tracking makes the feature essentially useless. On standalone, you click your controllers together to switch to hand-tracking, then the next time you pick up your controllers both the headset and VRChat disable the hand-tracking so you can use your controllers again. In the current beta, when you pick your controllers back up, VRChat still tries to force you to use hand-tracking. For example: when navigating the VRChat menu while holding the controllers, the VRChat "pointer/laser" is linked to where your index finger is pointing instead of where the controller is pointing. Additionally, pulling the trigger on the controller doesn't select menu items. The "gestures" that your avatar's hands perform when holding the controller are also different than the gestures the same avatar would perform if VRChat had switched from hand-tracking to controllers. I assume this has something to do with the fact that it's emulating index controllers. It's odd because VRChat is still receiving some inputs from the controllers when you pick them back up. You're able to move/turn your avatar, open and select items on the radial menu, etc. Yet for some reason VRChat doesn't recognize that you've switched to using the controllers for things like interacting with the normal menu, performing gestures, grabbing, etc. The issue wouldn't be quite as bad if there were a setting in the "Tracking & IK" tab that allowed you to disable/enable hand-tracking whenever you wanted, but I couldn't find that option. I even disabled hand-tracking in my Quest settings, yet VRChat wouldn't disable the hand-tracking. I had to uninstall the VRChat beta and go back to the normal build in order to properly use my controllers again. The actual hand-tracking works well. It's just unfortunate that the feature is essentially unusable due to the inability to switch between controllers and hand-tracking, and the "open VRChat menu" and the "open SteamVR overlay" being linked to the same gesture (palm facing headset, pointer-finger touching thumb). In regards to the VRChat/SteamVR menu, I tried the toggle at the top of the VRChat hand-tracking settings that said something about "avoiding dual inputs in SteamVR," but it had no noticeable change regarding this issue.

Getting spam bursts of this error for different players after they joining the instance and loading avatar. Also happens sometimes when players in instance for a long time and doesnt change avatar. I see no unusual messages around this error, so I don;t have additional context for this. Here some fragments from logs, with stacktrace, I hope this help solve issues: