Open Beta

I have a Raycast which is rotated in intervals, the WallCollider/_Ratio value can be seen in the debug, the value is not updating based on the rotation and is somehow giving me the value in a single direction (front of the avatar). This can be fixed by adding a new step where I disable the component during a rotation. As you can see WallCollider/_Ratio now gives the correct values.

Under conditions that have not yet been identified, the Voice parameter, which is expected to remain local-only, shows minor fluctuations (approximately 0.01–0.02) when other users are speaking. This behavior has been observed even while the microphone is muted. This may indicate an issue related to how this parameter is updated. This report was translated from Japanese.

VRCSDK 3.10.3-beta.1 added a new VRCRaycast component. However, all fields on the component are private, even fields visible in the inspector, which makes it difficult to configure or read the configuration from scripts. Please make fields visible in the inspector public or provide public properties to access them, so that we can read and write the configuration from scripts without needing to use reflection or SerializedObject (which is also reflection-like). There are some use cases that requires reading of the configuration fields. For example, my Avatar Optimizer requires read access to the raycast configuration to determine which parts of the avatar are safe to optimize and which should be left unchanged. I don't know why the fields are private currently, but if you're concerned about future breaking changes, it's common practice in C# to expose fields through public properties with private backing fields. Properties allow you to control access and add logic in the future without breaking existing code. If a fields' type or name needs to change, you can cast the value to the new type or redirect it to a new field while keeping the property's name and type the same for backward compatibility.

Response obtained by accessing http://127.0.0.1:<port>/ in a web browser: https://gist.github.com/logicmachine/b927b2c267b5525c9ea3506fa8be9a9f The value of user-camera pose is not an array: Expected response: {"FULL_PATH":"/usercamera/Pose","ACCESS":1,"TYPE":"ffffff","VALUE":[0.0,0.0,0.0,0.0,0.0,0.0]} Actual response: {"FULL_PATH":"/usercamera/Pose","ACCESS":1,"TYPE":"ffffff","VALUE":[{"ÍÌÏÎÏÏÏÏÎÍÎÎÏÌÍÌÍÌÍÍÍÍÏ":[0.0,0.0,0.0,0.0,0.0,0.0]}]} The VALUE for /usercamera/Pose is wrapped by an object with a strange key. The response is cut off midway: Actual response: {"FULL_PATH":"/avatar/parameters/Fx_Color","ACCESS":3,"TYPE":" The response is cut off midway and it becomes an invalid JSON. Environments: VRChat Build 1706 Avatar: avtr_5f2b783e-dd6c-490b-b52d-fe3240fc5f60

Block a User. View their Mutual Friends. Get blocked. View their Mutual Friends. This seems like a pretty big privacy oversight, as I doubt anyone would want blocked users looking up mutual friends to harass or co-opt into being intermediates. For context: Not even Discord allows this with it's mutual friends feature.

On an avatar which has Viseme Parameter driven animations to my material that change a lighting pattern according to what phoneme I'm saying, these animations are no longer driven correctly on the current open beta (Build 1830). This doesn't affect the normal mouth blendshapes setup and defined in the avatar descriptor. This behaviour is also only local, friends report seeing animations displaying normally (but I don't know if they were on the beta or not, so maybe it was just because they weren't on the beta). Attached is demo with the first half of the video showing expected correct behaviour on the stable current build and second half showing behaviour on the open beta. (No audio was recorded in the video but you can see my HUD mic lighting up in first person and my mouth opening as I am speaking.) Avatar shown in example (private) is: avtr_69db88d0-7898-4c91-9b9b-f3015a8df65d Turn on Expressions > 'Switch Modes' to switch to the robotic texture and turn off Expressions > Clothing > 'Jacket On' to hide the jacket that is on by default.

Create new instance in-app Make sure to set "Minimum Avatar Performance" Mark "Set as Group Instance Default" Try create instance again and find mentioned setting not saved. 1st picture is when originally setup, while 2nd picture is trying to do same and option not saved.

I noticed in-between open beta and live that my visemes don't fire as effectively in the open beta compared to live. I checked the mic peak meter in the settings, and it appears to be that the client is not detecting my mic as loudly as compared to live. https://drive.google.com/file/d/1Qg0YDMQw3GGW0DLIsmRgnB8wJCM21Yi9/view?usp=sharing

Accessories that are attached to the head are not visible when viewed in the third-person camera. Accessories that are attached to other bones are still visible, however. See photo; I have the googly-eyes attached as evident by the face mirror, which aren't visible if I rotate the third-person camera around to see my face. However, I have a cube attached to the leg, which remains visible.

Every time update open beta branch, my group instance default setting got reset to none. It happen past few release which previously patched but happen again.