Avatar Bugs & Feature Requests

Post about current Avatar bugs and Avatar Feature Requests. One item per post!
Non-constructive and off-topic posts will be moved or deleted.
`Eye Look` with Native FT causes random eye offsets on remotes
With the new Native FT update, windows build 1937, I've been having an issue where remote clients see my avatar's eyes with set random offsets. Locally, everything is 100% perfect all the time. Only remotes have this offset issue. After tracking the issue down, I've found that if I disable Eye Look completely in the VRC Avatar Descriptor, the offset no longer happens on remotes. (See included VRC Desc picture for broken version) It appears if you drive your own eye look bone rotations in your own animator while Eye Look setting is enabled (even with Eye-gaze field set to Face Tracking ), an offset is applied to remotes when your avatar is loaded in. Possibly an additional problem that I have 'none' set as my eye bones (defaulting to use Unity-Avatar's set Eye Bones when none?) If I had to guess, when the remote loads in your avatar, the stimulated Eye-Gaze functionality is on by default applying bone rotations and/or Eye Look param value changes. Then, the avatar is initializes with its networked params. Which freezes the simulated Eye-Gaze baking that offset into the remote user's avatar. This offset may be baked into the bone rotations, or the Native FT Eye Look parameter itself. If this issue is an intended conflicting behavior, perhaps a warning help-box in the VRC Avi Desc and an additional note in the documentation, would really help. Reproducible by: Use an avatar that uses bone rotations for its eye tracking. (you can use my linked avatar) Enable Eye Look with Face Tracking Eye-Gaze setting enabled. Drive your eye rotations via Native FT Eye Look params. Join a world with another remote user. Have the remote user observe the potential offset in the positions of the eyes. Included video: Note how when I switch avatars, the Remote eyes are completely different than the local. Including the ears rotations as they are also driven by Native FT Eye Look params. This public avatar uploaded with Eye Look enabled demonstrates this issue well. (yeah its creepy xD Just a stripped down version of my avatar): https://vrchat.com/home/avatar/avtr_b1e1f772-1b05-4556-965c-1ddeb5a8a0fc
1
·
Bug Reports
·
tracked
Some toggles not syncing on the same version after 10/28/2026 update
Some of my avatar's toggles are being forced on for my friends, while on my side the toggles are either off or something else is toggled on that would normally toggle off that toggle. Strangely the desync only happens on PC to PC, and not PC to Quest. The toggles in question are the Harness Panties, and the Harness Bra. They are on by default, and I think that might have something to do with why they are forced on for other PC users. This also affects the other underwear toggles since when I toggle one of them on, the only thing other people see is the default ones. Flat out taking them off also does nothing for other people (besides Quest users), so I think it's an issue with the On/Off state of the parameter forcing it to be on for other PC users. Before the update, I didn't have this issue, so I know it isn't something on the avatar's end. I will link the avatar and worlds used during testing below. Avatar: https://vrchat.com/home/avatar/avtr_454e63af-eed0-4c39-8c46-51f21268173b Worlds: https://vrchat.com/home/world/wrld_8d740b03-93a4-4153-99de-9fd67d86d4ae/info https://vrchat.com/home/world/wrld_1ddfdbb6-b972-4d88-8ee9-aee00c6c75a0/info https://vrchat.com/home/world/wrld_e0434a34-2f64-4e89-99da-8e3b4a86ffe4/info In order to recreate this desync, you'll need two PC users. As the one wearing the avatar, turn off, or equip something that would turn off the Harness Panties/Bra, such as another underwear item which can be found by going to Toggles->Closet->Bottoms or Toggles->Closet->Tops->Page 2. On the other PC user's end nothing will happen, but on the avatar wearer's end, the toggle will work as intended. You may want to take off the default bodysuit for a better view, since they blend in with each other heavily. It can be found under Toggles->Closet->Bodysuits. I'd also reccomend taking off most of the accessories that it has by default, found in Toggles->Closet->Accessories since it can cause lag on lower end devices.
1
·
Bug Reports
·
tracked
SDK default Additive controller (vrc_AvatarV3IdleLayer) uses Write Defaults OFF on an additive layer, tripling non-zero blendshapes
SUMMARY The SDK's default Additive controller (vrc_AvatarV3IdleLayer) has a single layer whose blending mode is Additive, and both of its states ("Upright Idle" and "Empty") are Write Defaults OFF. When no WD OFF state in a playable layer above Additive covers it, every shape key that - is bound by some clip in the avatar's playable layers, and - has a non-zero value on the SkinnedMeshRenderer is shown at 3x its value (30 becomes 90). We observed this in the VRChat client on an affected avatar, and reproduced it with the minimal steps below in Gesture Manager. Setting only the Additive controller's states to Write Defaults ON fixes it, without changing the idle body motion. STEPS TO REPRODUCE Environment: Unity 2022.3.22f1, VRChat SDK Avatars 3.10.4, Gesture Manager 3.9.9 Use any humanoid avatar. On its face SkinnedMeshRenderer, set any shape key to 30. Create an FX controller with one layer (weight 1) containing two states: - "Idle" (default state): an empty clip, Write Defaults ON. - "Shape": a clip that animates that shape key, Write Defaults ON, with no transitions into it (it never plays). Assign this controller to the FX slot. Copy vrc_AvatarV3HandsLayer.controller (Packages/com.vrchat.avatars/Samples/AV3 Demo Assets/Animation/Controllers/) into Assets, turn Write Defaults ON on every state, and assign it to the Gesture slot. Leave Base, Additive, Action, Sitting, TPose and IKPose at their defaults. Play, stand idle, make no gesture. Expected: 30 Actual: 90 Copy vrc_AvatarV3IdleLayer.controller (same folder) into Assets, turn Write Defaults ON on both of its states, and assign it to the Additive slot. Actual: 30. The idle body motion is unchanged. Notes: - Only shape keys that some clip in the playable layers binds are affected, even if that clip never plays. - A value of 0 stays 0. - Base does not matter. - The error is hidden while any WD OFF state plays above Additive: the default Gesture controller, a WD OFF FX, or Action at weight 1 during an emote or AFK. This is why most avatars never notice it. WHY IT HAPPENS A WD OFF state asserts every animated binding of the avatar. For the bindings it does not animate itself, it fills in its held (bind-time) value. On the Additive input, which is additive, that dense pose is added on top of the lower layers twice: - once through the additive playable input, and - once more through the additive layer blend. So a shape key the Additive layer never touches still gets its default value added twice: d + 2d = 3d With an empty (zero-curve) clip in the same state, the value does not settle; it keeps growing every frame. WHY WD ON IS SAFE FOR THIS CONTROLLER We compared Additive = default (WD OFF) against a WD ON copy in every combination of: - Base: WD OFF / WD ON - Gesture: WD OFF / WD ON - FX: WD OFF / WD ON / mixed per layer - Action weight: 0 / 1 That is 24 configurations, 300 frames each, checking all 54 humanoid bones and the root. The idle clip was a muscle-only additive clip that moves the body by up to 8 degrees. Results: - Shape keys, Additive WD OFF: 3x whenever Gesture and FX are WD ON and Action is at weight 0. 1x otherwise. - Shape keys, Additive WD ON: 1x in all 24 configurations. - Humanoid motion: identical in all 24 configurations (0 degrees / 0 m difference between WD OFF and WD ON Additive). Humanoid muscles are applied as a single human pose, which Write Defaults does not affect, so the idle motion does not depend on this setting. On WD OFF avatars the change is invisible. On WD ON avatars it removes the error. Tools already apply this fix: VRCFury's "Fix Write Defaults" option marks all additive states WD ON. REQUEST Please set Write Defaults ON on both states of the SDK's default Additive controller, and on the client's internal equivalent if it mirrors the SDK asset. RELATED "[BUG] VRChat apply blend shape values 3 times" (2020, marked fixed) has the same symptom. The cause described here is in the default controller asset. https://feedback.vrchat.com/avatar-30/p/bug-vrchat-apply-blend-shape-values-3-times ------日本語------ 概要 SDK 既定の Additive コントローラ(vrc_AvatarV3IdleLayer)は、合成方式が Additive のレイヤー 1 枚だけでできていて、その 2 つのステート("Upright Idle" と "Empty")はどちらも Write Defaults OFF になっている。 Additive より上の Playable レイヤーに、これを覆う WD OFF のステートが無いとき、次の条件を満たすシェイプキーがすべて、その値の 3 倍で表示される(30 が 90 になる)。 - アバターの Playable レイヤー内のどこかのクリップが bind している - SkinnedMeshRenderer 上の値が 0 でない 問題が起きるアバターで、VRChat クライアント上での発生を確認した。また、下記の最小手順で Gesture Manager 上でも再現した。 Additive コントローラのステートだけを Write Defaults ON にすると、idle の体の動きを変えずに直る。 再現手順 環境: Unity 2022.3.22f1、VRChat SDK Avatars 3.10.4、Gesture Manager 3.9.9 任意の人型アバターを使う。顔の SkinnedMeshRenderer で、任意のシェイプキーを 30 にする。 レイヤー 1 枚(weight 1)の FX コントローラを作り、ステートを 2 つ置く。 - "Idle"(既定ステート): 空のクリップ、Write Defaults ON - "Shape": そのシェイプキーを動かすクリップ、Write Defaults ON。ここへの遷移は作らない(再生されない) このコントローラを FX 枠に割り当てる。 vrc_AvatarV3HandsLayer.controller (Packages/com.vrchat.avatars/Samples/AV3 Demo Assets/Animation/Controllers/) を Assets にコピーし、全ステートの Write Defaults を ON にして、Gesture 枠に割り当てる。 Base、Additive、Action、Sitting、TPose、IKPose は既定のままにする。 再生し、ジェスチャー無しで立ったままにする。 期待値: 30 実際: 90 vrc_AvatarV3IdleLayer.controller(同じフォルダ)を Assets にコピーし、2 つのステートの Write Defaults を ON にして、Additive 枠に割り当てる。 実際: 30。idle の体の動きは変わらない。 補足: - 影響を受けるのは、Playable レイヤー内のどこかのクリップが bind しているシェイプキーだけ。そのクリップが一度も再生されなくても対象になる。 - 値が 0 のものは 0 のまま。 - Base は関係しない。 - Additive より上で WD OFF のステートが再生されている間は、誤りが覆い隠される。既定の Gesture コントローラ、WD OFF の FX、エモートや AFK 中で weight 1 の Action がこれに当たる。多くのアバターで気付かれないのはこのため。 原因 WD OFF のステートは、アバターがアニメーションしている全 binding を主張する。自分がアニメーションしていない binding は、保持値(bind 時の値)で埋める。 Additive の入力は加算なので、この「密なポーズ」は下位レイヤーの上に 2 回足される。 - 1 回目: 加算の Playable 入力として - 2 回目: 加算レイヤーの合成として そのため Additive レイヤーが一切触らないシェイプキーにも、既定値が 2 回足される。 d + 2d = 3d 同じステートに空の(カーブ 0 本の)クリップを置くと、値は落ち着かず、毎フレーム増え続ける。 このコントローラを WD ON にしても安全である理由 Additive = 既定(WD OFF)と、WD ON のコピーを、次の全組み合わせで比較した。 - Base: WD OFF / WD ON - Gesture: WD OFF / WD ON - FX: WD OFF / WD ON / レイヤーごとに混在 - Action の weight: 0 / 1 計 24 構成、各 300 フレーム、人型の 54 ボーンすべてとルートを確認した。idle のクリップには、体を最大 8 度動かすマッスルだけの加算クリップを使った。 結果: - シェイプキー、Additive WD OFF: Gesture と FX が WD ON かつ Action の weight が 0 のとき 3 倍。それ以外は 1 倍。 - シェイプキー、Additive WD ON: 24 構成すべてで 1 倍。 - 人型の動き: 24 構成すべてで一致(Additive の WD OFF と WD ON の差は 0 度 / 0 m)。 人型のマッスルは「1 枚の人体ポーズ」として適用され、Write Defaults の影響を受けない。そのため idle の動きはこの設定に左右されない。 WD OFF のアバターでは変更は見た目に表れない。WD ON のアバターではこの誤りが消える。 この修正は既にツールでも行われている。VRCFury の "Fix Write Defaults" オプションは、加算レイヤーの全ステートを WD ON にする。 要望 SDK 既定の Additive コントローラの 2 つのステートを、Write Defaults ON にしてほしい。クライアント内部の同等品が SDK のアセットと同じなら、そちらも。 関連 "[BUG] VRChat apply blend shape values 3 times"(2020 年、修正済みとして完了)は症状が同じ。ここで述べる原因は、既定コントローラのアセットにある。 https://feedback.vrchat.com/avatar-30/p/bug-vrchat-apply-blend-shape-values-3-times
1
·
Bug Reports
·
tracked
Load More
→