SDK Bug & Feature Requests

The new 3.8.1-beta.1 SDK adds a bunch of new camera accessors. However, something that is missing that would be incredible for effects that involve funkier render passes and effects that need udon-side help is the ability to read the per-eye oblique matrix. While there are ways to get this as-is, it requires some manual math to derive and requires digging into unity innards. It'd be great to be able to get these values directly off of the camera. An example of this is to make a custom VRCMirror that has an arbitrary origin to more easily make better portal-like effects, as this requires being able to put a camera on the receiving side - doing this in a stereo-correct way is currently a tricky task. Having these values as getters or methods on the new VRCCameraSettings API would be incredible. Worth a note here: while we have accessors for eye position/rotation, this is not enough to correctly do stereo rendering. See the VRC Mirror component for details.

Within a render callback such as OnWillRenderObject, it's useful to be able to check which camera is rendering. Unity has "Camera.current" for this, but it's not exposed to Udon. The new camera API is awesome, but without a property like that, I still can't make my UdonPortals prefab render correctly in the hand-held camera because there's no way to tell which camera is currently triggering OnWillRenderObject. I'd like a property to tell which camera is responsible for the render. A really simple implementation would be a new read-only property like: VRCCameraSettings.CurrentCameraType: An enum consisting of the values "ScreenCamera" or "PhotoCamera". However, I think this API could be extended further to be even more useful. In particular, if a Camera that was created by the world (and so is already accessible to Udon) is rendering, it would be great to be able to access the actual Camera object! Just like Unity's "Camera.current", but only limited to world-created Cameras. An API might look like this: VRCCameraSettings.CurrentCameraType: Enum consisting of the values "ScreenCamera", "PhotoCamera", "WorldCamera", or "Other". "WorldCamera" would be any camera created by the current world, i.e. a Camera that's accessible to Udon. "Other" would be anything else that isn't (yet!) accessible to Udon, e.g. avatar cameras or the screenshot camera. VRCCameraSettings.CurrentCamera: A reference to the current Camera object, just like Unity's Camera.current, except it's only set when CurrentCameraType is "WorldCamera". Otherwise, it's null.

In the new SDK 3.7.6, it's now possible to build a world on Linux, but it is not possible to launch a local test with proton. Pls add proton support, similarly to: https://github.com/BefuddledLabs/LinuxVRChatSDKPatch

I've been fiddling around with new drone API since it is public, but I found out sometimes it is quirky when calling VRCDroneApi.TeleportTo() with Udon(sharp). Whatever what coordinate you want to teleport the drone to, the drone will always drift back to the same y-level it was. I don't know if this should consider a SDK bug or drone bug.

This new version seems really emjoy hanging in Scheduler.Tick. Maybe I got too many avatars?

SDK ver 3.8.1-beta.1 When setting platform overrides, which avatar you have selected when pressing build & publish still matters and it attempts to build & publish the avatar you have selected instead of what you specified in the platform overrides. I consider this to be a bug as the user already went out of their way to set a platform override, so I think that should take precedence. An easy way to get this is to be on the android build platform and have your PC avatar as the selected avatar, obviously with your android version set in the platform overrides, and then build and publish with just the android platform set as the build target. The build will fail with avatar validation failed.

I'm trying to merge scenes before build in OnBuildRequested. What is happening is that it creates a successful build and then cancel the upload. The only thing I do is copy all open scenes into a new scene and build that one instead. This is happening in 3.8.0 and in eralier versions as well. It seems to create a vrcw file just fine and reports that the build is successful. If I use an older SDK that still got upload last build as an option the file can be uploaded and works without any problems. (same build and publish problem is there as well though) Build and test also works flawless. Setup: Use the default world scene, add another scene with some cubes or something. Have a script create a new scene and move the content over to that scene when OnBuildRequested is run. After it has copied everything unload those scenes. When clicking Build & Publish it runs as expected until it reaches upload Where it just says "Upload cancelled" Tried to clean up some things in here. My code: https://gist.github.com/Tummy-git/8d5e1ee754abf2e321aa04d07a4754ae EDIT: We figured out why, and it's not technically a bug, so this is now a feature request. Make it ignore scene changes during preprocess and upload!

VRCExpressionParameters files should not clamp a parameter's defaultValue if Synced is unchecked. Unsynced variables aren't clamped, so the parameters file should allow this.

Steps: Create a scene Create a gameobject with a slash in the name, or a gameobject as a child of another gameobject with a slash in the name (basically, scene path has a slash in it) Attach a component that makes it networked, such as VRCObjectSync or an udon script with networking on it Generate and export network IDs Attempt to import the network IDs As a result of the file using slashes as separators, the network IDs will fail to import for these objects. Unfortunately, using slashes to signal section (for example, "/// PATREON ///") is a common practice among many creators, and this causes problems for transferring network IDs between projects when a separate PC vs Quest scene or unity project is used.

VRChat SDK - Avatars Ver.3.8.0 Sorry if there are any mistakes because I used machine translation. There appears to be a configuration error in the animator controller of the Avatars SDK sample. In the default FX layer, within the vrc_AvatarV3FaceLayer, in the Eyes layer, the Empty state does not have an animation clip assigned. Therefore, this state behaves the same as when Write Defaults is turned on. If the FX layer is built in its original sample state, bugs from Write Defaults being on fortunately do not occur. However, if you use the sample as a base and then make modifications to the FX layer by adding elements afterward, bugs may potentially occur. Similarly, the Empty state in the Idle layer of vrc_AvatarV3IdleLayer, which is stored in the same directory as vrc_AvatarV3FaceLayer, also does not have an animation clip assigned. Fortunately, since the Idle layer is set to Additive, no bugs occur, but this is still an unhealthy state that should be fixed.