Bug Reports

For Deaf users, the chatbox is a primary communication method. Typing text is equivalent to voice chat for hearing users. When typing at a normal conversational speed, the chatbox frequently triggers spam detection and applies a timeout. This occurs during regular back-and-forth conversation, not intentional spam. As a result, Deaf users are temporarily prevented from communicating at all, because our primary communication tool becomes unavailable. This creates an accessibility barrier where none should exist. This is not an improvement, but a big step backward in accessibility for Deaf players. I do not use TTS, so chatbox access is essential. Please excuse my English, as British Sign Language (BSL) is my first language.

My chat messages seem to either not load for minutes or i get timed out after 2-3 messages which makes communicating as a non-mic user kinda difficult. The problem only became apparent after the update

Any avatar with Marshmellow PB post patch is good example of this local jitter and does not show up in a screen recording using OBS. The issue seems to be tied to frame rate and at 60 fps locked it functions normally, however above that its appearing to jitter extremely fast while locomotion moving. Can only observe this behavior in first person POV. I did not notice this before but maybe im just crazy. Either way there is a issue. Edit: I Had thought this behavior wasnt showing in a mirror but upon checking again today, i can see it now at higher frame rate. my thought is maybe something with recent fix on physbones may have made a new movement bug with resting colliders.

The new sdk pickups behave differently on vive wands (relative to previous sdk versions) In the video provided, I'm using the trigger to try to transfer a pickup between my hands, it often gets dropped during a transfer. It's not on par with previous pickup versions and it makes pickups very unintuitive to use Among all the new pickup types (across 1.0 and 1.1) only one type does not randomly drop out of the hands on vive wands when picking it up, that being pickups set to 1.0 with Auto Hold's "Sometimes" setting I can't control what worlds upload their pickup types as, using the new pickup types is painful on vive and the behaviour is new to pickups. They regularly drop during transfers between hands or during initial pickup events if some internal state disagrees with me wanting to auto hold it This is with the trigger acting as both InputUse and InputGrab (a typical vive setup as far as I'm aware)

If a group moderator is in an instance and has their permissions revoked while in the instance, they can still use moderation permissions WITHOUT BEING LOGGED. If given back their permissions upon rejoining they cannot warn, kick, mute, or disable features in an instance but can only close the instance. Steps to recreate: Moderation Role user is in a group instance. Moderation Role user is revoked of their role/permissions in a group while staying in the instance. Said user can still use moderation permissions and not get logged until they leave the instance. Note: If a user is in the instance and is given the moderation permissions, they will only be able to CLOSE THE INSTANCE and not be able to use any of the other functional moderation tools.

According to the official documentation below, ApplyModifiedChanges() must be called after modifying VRC Constraint properties via script to apply the changes: https://creators.vrchat.com/common-components/constraints/constraints-api/#applymodifiedchanges However, I am encountering a compilation error stating that ApplyModifiedChanges() cannot be found, regardless of whether I call it on the Constraint component itself, the Sources list, or an individual source (e.g., Sources[1]). I have already included the following namespaces as specified in the documentation: using VRC.Dynamics; using VRC.SDK3.Dynamics.Constraint.Components; I also noticed a similar method called ApplyConfigurationChanges() defined for VRCParentConstraint. I tried using it instead, but it did not seem to reflect the changes. Could you please clarify where ApplyModifiedChanges() is defined or how to correctly apply property changes via U#? Environment: SDK Version: 3.10.1 原文： UdonSharpからVRC Constraintのプロパティを変更する際、ApplyModifiedChanges() メソッドが見つからない 下記の公式ドキュメントによると、スクリプト経由でVRC Constraintのプロパティを変更した後、変更を適用するために ApplyModifiedChanges() を呼び出す必要があります： https://creators.vrchat.com/common-components/constraints/constraints-api/#applymodifiedchanges しかし、Constraintコンポーネント自体、Sources リスト、あるいは個別のソース（例: Sources[1]）のいずれに対しても、ApplyModifiedChanges() が見つからないというコンパイルエラーが発生します。 ドキュメントの指示通り、以下の名前空間は含めています： using VRC.Dynamics; using VRC.SDK3.Dynamics.Constraint.Components; また、VRCParentConstraint に定義されている ApplyConfigurationChanges() という似た名前のメソッドを見つけたので試してみましたが、変更は反映されませんでした。 ApplyModifiedChanges() がどこに定義されているか、あるいはU#経由で正しくプロパティの変更を適用する方法を教えていただけますでしょうか？ Environment: SDK Version: 3.10.1

All avatar's view point position (desktop, half body or full body) has their view point off center, GoGo Loco T Pose controller fixes this issue. The black Mayu has the view point position centered using GoGo Loco T Pose controller. The yellow Mayu has the view point off center using VRChat's default T Pose controller. Notice how it leans closer to one of the eye bones. This can be observed with any avatar!

World tags should not be case sensitive. There is no reason why "chill" and "Chill" should be considered two different tags.

When using Selfie Expression, some avatar jaws will close too much and clip through the mesh. Example avatars: https://vrchat.com/home/avatar/avtr_e11afca0-b6d8-4787-a501-e78739ff742f https://vrchat.com/home/avatar/avtr_1f0e5cad-6a90-401b-b25d-379b2d2bb30e

Transactions not showing up before date range has changed. Click the credits button from the menu. Click transactions. See that it says that no transactions are available for the last 7 days. Change the range to a month or something. You now see all the transactions and can swap back to 7 days if you want.