Open Beta

While streaming the camera via Spout, it appears the resolution specified in the config file is not respected. In fact, it seems to for some reason be streaming much lower than 1080p (By just guessing it looks to be about 720p). Attached video is me toggling between Spout and the game window. Game is being rendered at 1440p (downscaled to 1080p by OBS), and the Spout stream is being rendered at a much lower resolution regardless of my config settings. Edit: Had a chance to check and confirm this also happens in VR mode. The game window will render the camera at the right resolution, but Spout is locked to a low resolution.

The ParticleSystemForceField component new to Unity 2018, combined with "external forces" module can open up a whole new breadth of avatar/world interactions not seen since Ik controlled GPU Particles. Mimi made an example showing what this component can do: https://i.imgur.com/yglb74H.gifv For the module to be useful, it must be allowed on avatars so that (combined with IKFollower) leg and arm positions can emit forces. Doing so can enable new types of 30dof interactions not seen before between avatars or between avatars and particle systems in worlds. Worlds that wish to block avatar particle interactions must only uncheck avatar layers including Player, MirrorReflection etc. For this reason it should be safe to allow avatars to carry this component without impeding world creation. https://docs.unity3d.com/2018.4/Documentation/Manual/class-ParticleSystemForceField.html

I cannot join back group+ instance which I made myself while others managed to join. 2024.09.19 12:55:57 Error - [EOSManager] EOS ThreadLoop Exception: System.ArgumentOutOfRangeException: The specified timeout must represent a value between -1 and 2147483647, inclusive. Parameter name: millisecondsTimeout Actual value was -3. at System.Collections.Concurrent.BlockingCollection`1[T].TryTake (T& item, System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00000] in <00000000000000000000000000000000>:0 at ÌÎÎÏÎÎÏÌÌÍÍÏÍÌÌÏÎÎÎÌÌÏÌ.ÌÌÌÌÍÎÏÏÏÍÌÍÌÍÌÍÎÏÎÌÎÍÎ () [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00000] in <00000000000000000000000000000000>:0 2024.09.19 12:56:18 Error - [EOSManager] EOS ThreadLoop Exception: System.ArgumentOutOfRangeException: The specified timeout must represent a value between -1 and 2147483647, inclusive. Parameter name: millisecondsTimeout Actual value was -14. at System.Collections.Concurrent.BlockingCollection`1[T].TryTake (T& item, System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00000] in <00000000000000000000000000000000>:0 at ÌÎÎÏÎÎÏÌÌÍÍÏÍÌÌÏÎÎÎÌÌÏÌ.ÌÌÌÌÍÎÏÏÏÍÌÍÌÍÌÍÎÏÎÌÎÍÎ () [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <00000000000000000000000000000000>:0 at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00000] in <00000000000000000000000000000000>:0

When in VR, turning the streaming camera on and enabling the streaming toggle works fine and displays correctly on the desktop mirror. However, closing the camera (either via through the menu or a controller binding) while leaving the toggle on stops the capture to the desktop mirror. Video: https://files.catbox.moe/1zlzq5.mp4

Haxy discovered earlier today that in the new Open Beta build chatbox moderating a user in anyway will break SSO login with canny aswell as the website playermoderation's page to crash and become unusable halting login. https://vrchat.com/home/playermoderations here's two videos showing it happening only with chatbox moderation's active, removing them fixes issues. https://www.youtube.com/watch?v=OwIwREoVUh https://www.youtube.com/watch?v=K_THj7uCLsM

Simply earmuff mode should reduce/mute avatar audio and prevent avatars from trying to bypass this by setting audio volume or radius with an animation

The message says "press join" or "press eye", but there are no buttons at all, I can't even remove the message from UI. This doesn't happen 100% of time, but most of the time.

It appears that in SDK 3.2.0-beta.1, the ExtensionMethods.GetOrAddComponent helper was moved to the VRC.Core namespace; this can break editor extensions that might have inadvertently pulled this in by editor method completions.

I noticed that when some friends would stretch my avatars nose, I could not see it stretched. So I did some investigation: Seems like some sort of networking issue? On the live game everything works as normal, if I move my physbones, other people see them moved, if they move them, I see them moved. On the beta: If I move / stretch / pose my physbones, only I see them moved, other clients do not see them moved. If another person moves my physbones, all remote clients see them moved, but I do not. UPDATE: after writing the above I realized that it may be related to the network compatibility of the open beta, and found a friend also on the open beta. They were able to see my physbones move when I moved them! So its only interactions between live clients and open beta clients where this seems to happen. The avatar id of the avatar that I noticed this on is, but it seems to happen on other avatars I tried: avtr_1b2c6655-d89d-438f-89a4-1014e651b502 I've attached some images of this happening, however its somewhat hard to distinguish which are in what context. In order: What my friend on live sees, what I see, what I see when not on the beta. The images are from desktop mode, however I tested VR and the same thing occurs.

When you select on any individual user, there should be an option to allow/deny dyn perms for select individuals since the current perm toggles are all-encompassing.