Bug Reports

  • No off-topic posts
  • Don't report more than 1 issue at once
  • For isolated issues or customer support visit help.vrchat.com
Thanks for your bug report!
[1865] AudioReverbZone's User preset parameters are not applied correctly from the 2nd Join onward
## Overview The parameters of a User preset configured on an AudioReverbZone stop being applied correctly starting from the 2nd time (and onward) the user joins the world. The AudioReverbZone itself is active and reverb is applied, but the reverb sounds as if different parameters are being used than the ones originally configured. ## Steps to Reproduce Prepare a world with an AudioReverbZone component that has arbitrary parameters set via a User preset. Join the world (1st time) → Reverb is applied correctly, matching the configured settings. Leave the world once, then join the same world again (2nd time onward). The AudioReverbZone is active and reverb is applied, but the sound is as if different parameters are being used than the ones originally configured. A world for reproducing the above steps has been prepared. https://vrchat.com/home/launch?worldId=wrld_4ced52a1-695c-42c6-9e01-966acc4ea11e An AudioReverbZone and an AudioSource are set up around the green cube in the world mentioned above. When you use the white cube, it will overwrite the parameters of the AudioReverbZone that were set during the world upload. ## Expected Behavior Even after rejoining, reverb should be applied with the parameter values matching the User preset configured on the AudioReverbZone. ## Workaround After joining, if Udon re-overwrites the originally configured parameters, they return to the correct values at that moment. However, if you rejoin after that, the same issue recurs. The issue was not resolved unless the VRChat content cache was cleared. ## 概要 AudioReverbZoneに設定したUserプリセットのパラメータが、ワールドへの2回目以降のJoinから正しく適用されなくなります。 Reverb Zone自体は有効でリバーブはかかっていますが、本来設定した値とは異なるパラメータのリバーブがかかってしまいます。 ## 再現手順 AudioReverbZoneコンポーネントにUserプリセットで任意のパラメータを設定した物を配置したワールドを用意する ワールドにJoinする(1回目)→ 設定通りのリバーブが正常にかかっている 一度ワールドを離れ、再度同じワールドにJoinする(2回目以降) AudioReverbZoneは有効でリバーブはかかっているが、本来設定した値とは異なるパラメータの音になっている 上記の再現手順を実施するためのワールドを用意しました。 https://vrchat.com/home/launch?worldId=wrld_4ced52a1-695c-42c6-9e01-966acc4ea11e 上記ワールドの緑のCube周辺にAudioReverbZoneとAudioSourceが設定されています。 白のCubeをUseすると、ワールドアップロード時に設定してあったAudioReverbZoneのパラメータに上書きします。 ## 期待される動作 Joinし直しても、AudioReverbZoneに設定したUserプリセットの値通りのパラメータでリバーブが適用されること。 ## 回避策 Join後、Udonで元々設定していたパラメータを再度上書きすると、その場では正常な値に戻ります。 しかし、その状態で再度Joinし直すと、同じ症状が再発します。 VRChatのコンテンツキャッシュを削除しない限り、症状は改善しませんでした。
0
World Visits counts may have been increasing abnormally since around June 17, 2026
Since around June 17, 2026, the Visits counts for VRChat worlds may have been increasing abnormally. Based on posts from multiple world creators and external tracking services, this does not appear to be limited to a specific world. Several unrelated worlds seem to have shown a significant change in their Visits increases around the same time. For example, some worlds appear to have roughly doubled their daily Visits increases after around June 17. There have also been reports of unexplained Visits increases in worlds that normally receive very few visitors, worlds intended for small groups or personal use, and newly uploaded worlds where the creator only entered for testing or to take screenshots. At the same time, in some cases there does not appear to be a significant change in Favorites increases, social media promotion, or other factors that would reasonably explain the increase. This makes it difficult to explain the situation as simply an increase in popularity or traffic. Could you please check the following? Whether the Visits aggregation logic or counting conditions changed around June 17, 2026 If there was a change, whether it was an intentional specification change Whether there is currently an issue with how Visits are being counted If possible, whether creators can be informed about any specification changes and their impact Visits are an important metric for world creators when analyzing post-release performance, the impact of updates, promotion results, and comparisons between worlds. If Visits are currently being counted using a different standard than before, it becomes difficult to compare them with past data, which has a significant impact on creator-side analysis. For reports related to this issue, please see my X post below and the quote reposts on that post. https://x.com/oe_tw/status/2070338873633444118
2
·
tracked
Windows H.264 decoder (msmpeg2vdec.dll) NULL-pointer crash when playing TopazChat RTSP streams — affects both HW and SW decode paths, client-side workaround requested
VRChat crashes of an AVPro video player opening any TopazChat live stream (rtspt protocol, host topaz.chat ). Four crashes in one evening, three different broadcasters' streams, so not specific to one stream. Crash signature, byte-identical across all four crashes: Faulting module: msmpeg2vdec.dll (Windows H.264 decoder), version 10.0.26100.8758 Exception: 0xc0000005, read of address 0x1348 Fault offset: 0x2f848 WinDbg on the minidump shows a NULL-pointer dereference on a decoder-owned worker thread. All stack frames are inside msmpeg2vdec.dll, with no VRChat, AVPro, or GPU driver frames. Timing suggests a race during stream startup. Important: the launch option disable-hw-video-decoding does NOT help. Logs confirm the playback path switched from MF-MediaEngine-Hardware to MF-MediaEngine-Software and the crash still occurs at the same offset, since msmpeg2vdec.dll is the CPU bitstream decoder used by both paths. GPU and driver are ruled out. Repro: join any world with a TopazChat player and play a live stream. Crash will happen when trying to load that stream. Environment: Windows 11 Pro for Workstations 26H2, build 26300.8758. VRChat PC (Steam), Build 1865. Tested on Unity 6 Public Beta,crashes too. Root cause is in Microsoft's code and I have filed a Feedback Hub report as well, but VRChat may be able to work around it client-side, and your crash telemetry should show this bucket for any user on current Windows builds. Full WER minidumps (about 75 MB each, four crashes) available on request.
0
Load More