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 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 setting is enabled (even with field set to ), 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:

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 enabled demonstrates this issue well. (yeah its creepy xD Just a stripped down version of my avatar):