Do it, asap. Just going to let a discord post be here. "i am surprised and very disappointed that i don't see that much talk about this new update. the networked IK is very inaccurate. not only does everyone's avatar jitter around and move with their whole head if they don't move it in slow motion, it is also so inaccurate and inconsistent that pens on avatars are almost useless. reading someone's writing turns out to be one of the most difficult tasks in this game now and mutes clearly are doomed with this update. to explain it a little further, the networked IK does not read movements correctly at all. to an extent, where if someone's writing, it more or less catches the wrist movement for the letters, but it does not understand at all how they are moving their arms and how far. resulting in letters overlapping, being written right on top of each other, or just completely jittery. the IK will every now and then catch on, but instead of doing anything correctly, it will just teleport the player's arm to where they actually are looking and writing, resulting in a huge and disgusting line being drawn. this is a very consistent issue and has never existed before this patch came out. also to be noted: it is already an issue with low pings. however, 90% of vrc players are dealing with 100+ ms pings. and this issue is getting worse the higher their ping is. tldr: this game ruined the game for the majority, just to make it better for a minority..."

As of build 772, any FinalIK component added to an avatar only works locally. For example, I have an avatar that uses AimIK to aim a gun with my head. It worked prior to 772 and still does locally, but everyone else sees my gun aiming in the default position. I'm guessing the new networked IK strips all IK components on other players, and not just the ones its syncing.

I made a gimmick that can get player's bottom collider position with the FirstPersonController and FollowTarget scripts of StandardAssets, but it doesn't work anymore since build 772. It still works in the Unity editor though. Reproduce: wrld_87213d88-a1b6-4520-aa30-acd91703f981 https://github.com/chiugame/VRC_BugReport_CharacterControllerDontFollow StandardAssets required. - Press the button at the center. - Then the capsule should be left side, the cube's position, at least they are in the Unity editor or before build 772, but now you'd see it at right side. Japanese: StandardAssetsのFirstPersonControllerとFollowTargetを使用して足元のコライダーの位置を取得するギミックを作りました。 しかしながらBuild 772にて正しく動作しなくなりました。 UnityEditor上では正常に動作します。 再現： wrld_87213d88-a1b6-4520-aa30-acd91703f981 https://github.com/chiugame/VRC_BugReport_CharacterControllerDontFollow StandardAssetsが必要 ・ワールドに入って正面にあるボタンを押します。 ・UnityEditor・Build 772以前であればCapsuleは左にあるCubeの位置に移動していましたが、現在は右にあるままです。

It seems that the sync rate for particle based pens has dropped to unusable levels with the latest update. Some examples in this Twitter thread: https://twitter.com/bironist/status/1129065299431440384?s=19

when people in destocking or vr crouch, the neck breaks and looks up, when they are not looking up (it does not always happen)

Since the VRC update that makes everything perform better for the Quest users (And apparently worse for the main desktop users) it brought a lot of problems with it. Besides the weird quiet sounding menue sound, theres a big delay with moving objects and people walking in general. Unnatural now. Its more like a sliding around than actual movements if you dont walk far. Besides those delays, theres also a now bigger voice delay. Before everything was relatively okay when it comes to that, but now theres a noticable 2 second delay when we speak. (2 people in world) I always interrupt someone while speaking now. Here i made a video of the object delay. https://youtu.be/WbZUWLXhXOI My PC specs. i7 8700k, 16GB Ram, GTX 1080Ti And just as a little side note. I find it nice that people with a Quest get included into this game, but making EVERYTHING perform better, which automatically makes everything worse (At least the way it is now) is absolutely unfair for all the desktop users which are just the main players of this game, and i personally believe, this update made the game quite a bit less enjoyable.

Occasionally, other players become invisible (other than their nametag) and inaudible. Example screenshot showing two such players: https://www.dropbox.com/s/9hq42new0k5ewgk/20190516204755_1.jpg?dl=0 I'll be sending the output log to support@vrchat.com. Shortly before the timestamp of this screenshot, the following lines were in the log: 2019.05.16 20:47:26 Error - Exception encountered Deserializing VRCPlayer[Remote] olihata ［JP］ 777.SyncPhysics with observed components [VRCPlayer[Remote] olihata ［JP］ 777.PlayerNet, VRCPlayer[Remote] olihata ［JP］ 777.SyncPhysics, AnimationController.PoseRecorder, Indicator.SyncPhysics]: System.IndexOutOfRangeException: Array index is out of range. at DCEOAKELPLO.HPLDIPHOOHH (System.Byte[] OFGICEJHALF, UnityEngine.Vector3& FMPLFOLLAPM) [0x00000] in <filename unknown>:0 at DCEOAKELPLO.PFGPBFCLFJP (.NPACFHEICFH MEPFBOFMIFA, UnityEngine.Vector3& POGKNABGLHE, KFKIFKKGFMP DFFPMICCPHJ) [0x00000] in <filename unknown>:0 at SyncPhysics.FPBMKBIPENE (.NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL, .BONEJIDAGNJ CGFJHJFCMFL) [0x00000] in <filename unknown>:0 at SyncPhysics.OnPhotonSerializeView (.NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL) [0x00000] in <filename unknown>:0 at Photon.Pun.PhotonView.PIMIFMKOCCE (UnityEngine.Component PLAIAFOIFFM, .NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL) [0x00000] in <filename unknown>:0 at Photon.Pun.PhotonView.DeserializeView (.NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL) [0x00000] in <filename unknown>:0 2019.05.16 20:47:26 Error - Exception encountered Deserializing VRCPlayer[Remote] olihata ［JP］ 777.SyncPhysics with observed components [VRCPlayer[Remote] olihata ［JP］ 777.PlayerNet, VRCPlayer[Remote] olihata ［JP］ 777.SyncPhysics, AnimationController.PoseRecorder, Indicator.SyncPhysics]: System.IndexOutOfRangeException: Array index is out of range. at DCEOAKELPLO.HPLDIPHOOHH (System.Byte[] OFGICEJHALF, UnityEngine.Vector3& FMPLFOLLAPM) [0x00000] in <filename unknown>:0 at DCEOAKELPLO.PFGPBFCLFJP (.NPACFHEICFH MEPFBOFMIFA, UnityEngine.Vector3& POGKNABGLHE, KFKIFKKGFMP DFFPMICCPHJ) [0x00000] in <filename unknown>:0 at SyncPhysics.FPBMKBIPENE (.NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL, .BONEJIDAGNJ CGFJHJFCMFL) [0x00000] in <filename unknown>:0 at SyncPhysics.OnPhotonSerializeView (.NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL) [0x00000] in <filename unknown>:0 at Photon.Pun.PhotonView.PIMIFMKOCCE (UnityEngine.Component PLAIAFOIFFM, .NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL) [0x00000] in <filename unknown>:0 at Photon.Pun.PhotonView.DeserializeView (.NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL) [0x00000] in <filename unknown>:0 2019.05.16 20:47:26 Error - Exception encountered Deserializing VRCPlayer[Remote] olihata ［JP］ 777.SyncPhysics with observed components [VRCPlayer[Remote] olihata ［JP］ 777.PlayerNet, VRCPlayer[Remote] olihata ［JP］ 777.SyncPhysics, AnimationController.PoseRecorder, Indicator.SyncPhysics]: System.IndexOutOfRangeException: Array index is out of range. at DCEOAKELPLO.HPLDIPHOOHH (System.Byte[] OFGICEJHALF, UnityEngine.Vector3& FMPLFOLLAPM) [0x00000] in <filename unknown>:0 at DCEOAKELPLO.PFGPBFCLFJP (.NPACFHEICFH MEPFBOFMIFA, UnityEngine.Vector3& POGKNABGLHE, KFKIFKKGFMP DFFPMICCPHJ) [0x00000] in <filename unknown>:0 at SyncPhysics.FPBMKBIPENE (.NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL, .BONEJIDAGNJ CGFJHJFCMFL) [0x00000] in <filename unknown>:0 at SyncPhysics.OnPhotonSerializeView (.NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL) [0x00000] in <filename unknown>:0 at Photon.Pun.PhotonView.PIMIFMKOCCE (UnityEngine.Component PLAIAFOIFFM, .NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL) [0x00000] in <filename unknown>:0 at Photon.Pun.PhotonView.DeserializeView (.NPACFHEICFH MEPFBOFMIFA, HPMPDFMDLKE PJKMLPBODAL) [0x00000] in <filename unknown>:0 No such lines were seen for killy_

Aside from the bad interpolation resulting in some laggy looking movement, There seems to be some kind of bug whereby the networked IK system just completely falls apart if an instance goes on too long, possibly with too many people being a factor. https://streamable.com/0a665 All but 1 or 2 of the people in this clip are in VR, and a good chunk of them are in full body. They are all jittering around and all of them look like they are desktopping. This happened twice to us. Once we moved to another world it cleared up, (leaving and rejoining the affected instance does not fix it, and in fact, upon leaving the instance, you get a disconnect error as you fade to black, and you spawn at your destination in the default grey robot man.) but after a while in the new world, the problem reared it's head again. People freezing in place and then teleporting and jittering around, and in desktop mode. (And a disconnect error on exit+grey robot man avatar on load in)

Avatars with a number of audio sources (More than 10? I haven't tested) seem to cancel all audio currently active when the avatar loads in, including world audio and other avatars' audio that's currently active. It doesn't matter if the number of audio sources on an avatar is all active or disabled by default, if it has a high count of Audio Sources, it cancels everything else for some reason. Wondering if there is a planned fix for this, this started happening after the latest patch with networked IK and such. Scared to use some of my avatars now in other worlds that rely on world audio since it just breaks those audio sources.

With the last update, the precision of Object Sync's position on remote clients has become very low. Traveling a distance away from the 0 point will result in object sync'ed objects jumping or snapping to places. The x, y, and z values are treated independently, meaning that if you are at (0, 0, 200), then only the z position of the object will "snap" in place. Example world: wrld_312c666d-50c9-4456-9585-02da88e1a92e In this world there are three locations each with a green pickup sphere. Join with at least 2 people to see the bug. (0, 0, 0): The pickup here will act normal on remote clients. (200, 0, 0): The pickup will "snap" about 1 decimeter on the x axis, but will be normal on the y and z axes. (200, 0, 200): The pickup will "snap" on both x and z axes.