Bug Reports

For a few days now, the default settings for the instance type of my private homeworld (not published) no longer apply. The instance is always created as "Invite," even though the default type is set to "Friends." If I set a published world as my homeworld, the default type works correctly again. The problem first caught my attention two days ago. Currently, I always have to manually reopen the world as a Friends Lobby. Build: 2024.4.1p4-1538-c5eb5d8aff-Release

I'm not entirely sure what's causing it all I know is that theres a chance it shows up when you look at world then switch over to another, it sometimes (not always but a good majority) shows the instances for a world you were just looking at instead of the current one. Now it doesn't always happen, sometimes it does load in the instances for that world but a majority is that when you look at one world then back out and look at another world only the instances for the previous world show up, you can go to the random instance that it shows when you open it but specific instances do not show up for said world, only the ones before

Random avatars are currently returning error bots for non-local players (Ie; they look fine to the wearer, but anyone else loading them gets the Error Bot). Console shows the following errors; Error - [Behaviour] Error downloading avatar [AVATAR NAME]/Security: Error loading asset bundle from ****: HTTP/1.1 403 Forbidden Error - [Behaviour] Error downloading avatar [AVATAR NAME]/Standard: Error loading asset bundle from ****: HTTP/1.1 403 Forbidden

Issue: I've run into a weird issue with OnDeserialization , when ever a late joiner joins my Picture Loader World the event fires, but without actually having received any networking data. Reproduction Steps: Create an Instance in my World https://vrchat.com/home/world/wrld_65b1db37-cce6-48d8-b57e-58c3f31b2c93 Go the the URL Input section and enter a URL Join with another client If you do this you will notice that the Image wont start loading for them. You can manually do another RequestSerialization by pressing on the Lock button, doing so will result in it also loading for them. Additional Info: I've added a few log messages to my map to help with debugging it: Debug.LogError("BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB: Start Ran!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"); This fires once start has run on the URL Input script to make sure it always runs before receiving network data Debug.LogError($"AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA: I received Network Data!!!!!!!!!!!!!!!! Locked:{locked}, Persistence Data Loaded: {savedImageLoaded}, netURL: {netUrl}"); This runs once OnDeserialization has fired and includes all variables that are being synced. The default is Locked: false, Persistence Data Loaded: false, netURL: , if nothing is different compared to this than the Networked Data wasn't actually updated. Expected Behaviour: Networking Data should actually be updated once OnDeserialization runs. This also works fine in Local Test Builds btw. Attachments: Here is a video show casing the issue: https://files.catbox.moe/ey775e.mp4

Since the latest update, personal avatar scalers like the Jackal scaling system and Mag's scale adjuster have been broken for the local mirror clone. This means that in mirrors or cameras, the scale seems to be getting applied twice. It appears this has to do with constraints not running in the mirror clones. Dexvoid highlighted a temporary workaround, although this is undesirable and also doesn't guarantee this will keep working in the future as the behavior will get changed again. To make them work again for now there is a workaround to add source to the constraint on the armature that looks at the head bone with a weight of 0. This makes the local version be incorrectly scaled twice up as well, which then can be compensated by having all scale animations be the square root of the original value. I've attached a couple images of the discord message, workaround fix applied to the constraint in unity, and a screenshot of in-game showing the issue. Here a scale of .4x has been selected. You can see the eye height is a little below the pool table, but in the mirror the local clone got a lot smaller than .4x

Although I turn on leave notification, I cannot get ones. I CAN receive join notification, and I've gotten leave ones before updating to 1533. (It was 1519 I think.)

When clicking "Join" after waiting through a world queue, it sends you back to the instance page, asking you to queue again. This issue seems new since this week's release. I experienced it on 1538 and 1548 (open beta). The issue also affected a friend, so it doesn't seem to be only me. I experienced the issue on two separate worlds, both with queues. However, I was on priority queue for both, so that may be related. The issue is inconsistent. I triggered it three times in a row, then joined, left, and rejoined the queue and it worked.

VRC SDK version: 3.7.3 Set PB - enable Is Animated Move the bones set in PB with animation Make another object follow the PB bones with Constraint Combining all of these 1 to 3 will cause the Constraint to not work properly. This issue did not occur with VRC SDK versions 3.7.2 and below. -日本語- VRC SDKのバージョン: 3.7.3 1.PBを設定-Is Animatedを有効 2.PBで設定したボーンをアニメーションで動かす 3.Constraintを使用し、PBのボーンに別オブジェクトを追従させる これら1~3を全て組み合わせた場合、Constraintが正常に動作しなくなります。 VRC SDKのバージョン 3.7.2以前ではこの不具合は発生しませんでした。

After updating the SDK and VRC, objects set to follow with Constrain cause jittering in the mirror. Even when using mirror detection to disable all Constrain settings in MirrorClone, the same phenomenon occurs, so it seems to be an issue that arises when using Constrain in PlayerLocal. Confirmed with SDK 3.7.3 Release 1534. Please refer to the link below for the video. https://x.com/Tukumomi_VR/status/1854750688255131667 https://x.com/Tukumomi_VR/status/1854818302633083383 ================================================= [JP] 鏡の中でConstrain設定されたオブジェクトがジッターします。 SDKとVRCの更新後、Constrainで追従させたオブジェクトは鏡の中でジッターを引き起こします。 ミラー検出を使用し、MirrorCloneではConstrainをすべてDisableにするようにしても同様の事象が発生したため、PlayerLocalでConstrainを使用した時点で発生する問題のようです。 SDK 3.7.3 リリース1534にて確認

Constraints behave differently depending on whether they are set directly under the avatar's Root or under the Armature’s Hips. This phenomenon appears to affect only Contacts and PB, not Skinned Meshes or Particles. Additionally, with both configurations, when using Constraints, the mesh appears fixed in PlayerLocal but jitters in MirrorClone, similar to the behavior seen with Contacts. ①Constraint set directly under the avatar's Root The Constraint jitters when the avatar is stationary, but stops when the avatar is in motion. ②Constraint set under Armature’s Hips The Constraint remains stable when the avatar is stationary, but jitters intensely when the avatar is in motion. Please refer to the reference video below. https://x.com/Tukumomi_VR/status/1856163222237438081 The first avatar with the yellow ring is setup ① ID: avtr_5842db16-81ce-4956-9355-026ba3747b43 The second avatar with the blue ring is setup ② ID: avtr_b754535b-ebf0-4eb1-a4d1-2d8f86cba7c5 Here are the steps for the gimmick operation: [Activation] Make a RockNRoll gesture with your right hand and a Gun gesture with your left hand, then touch the Contact on your right wrist with your left index finger. [Expansion] Make a Point gesture with your right hand and a RockNRoll gesture with your left hand to expand the menu. In this state, it is fixed to the world. --------------------------------------------------------------------------- [JP] Constraint は、アバターの Root 直下に設定するか、Armature の Hips 配下に設定するかによって挙動が異なります。この現象はスキンメッシュやパーティクルには影響を与えず、Contact や PB のみに影響するようです。 また、どちらの設定でも Constraint 使用時、PlayerLocal ではメッシュが固定されて表示されますが、MirrorClone ではメッシュが Contact と同じようにジッターするようです。 ①Constraint をアバターの Root 直下に設定 アバターが静止している時に Constraint がジッターし、アバターが動いているとジッターが止まります。 ②Constraint を Armature の Hips 配下に設定 アバターが静止している時はジッターが止まり、アバターが動いていると激しくジッターします。 参考動画は以下をご参照ください。 [URL] 黄色いリングが付いた最初のアバターが設定① (Avatar ID) 青いリングが付いた2つ目のアバターが設定② (Avatar ID) ギミック操作の手順は次のとおりです。 [有効化] 右手で RockNRoll ジェスチャー、左手で Gun ジェスチャーを行い、左人差し指で右手首の Contact をタッチします。 [展開] 右手でポイントジェスチャー、左手でロックンロールジェスチャーを行うとメニューが展開されます。この状態ではワールドに固定されます。