VRChat Build 1913 brings Unity 6 to the regular Quest Open Beta
VRChat’s September 15 release notes specify Unity 6000.0.67f1 for the regular OpenBeta branch used to test Quest in standalone mode. Standalone means VRChat runs on the headset itself; playing the PC version through a Quest connected to a computer is a different setup. VRChat also says Unity 6 builds have become stable enough for its normal open-beta branches, so it is closing the separate unity-6 testing branch.
That branch change has a history. In a June 25 developer update, VRChat introduced Unity 6 testing on its own unity-6 open-beta branch. Moving those builds to the ordinary beta branches makes the new engine easier for existing beta users to encounter; extending the beta to standalone Quest lets VRChat test that client on the headset as well. “Stable enough” is VRChat’s judgment about beta readiness, not a claim that the engine transition is finished for creators or live players.
The precise scope matters for PC users. VRChat provides a Steam open beta for its PC client, but its beta instructions say open betas are not available through Meta PCVR. Quest owners who launch the PC version through Steam are testing the PC client, not the standalone Quest build announced in Build 1913.
Unity 2022.3.22f1 remains the editor for VRChat creators
A Unity engine version in the client describes the application players run. The Unity editor version in a creator’s SDK project describes the environment used to build and upload a world or avatar. Build 1913 changes the first of those on the Quest beta; VRChat explicitly says the SDK side has not changed and warns creators that upgrading their projects to Unity 6 “will not work.”
VRChat’s creator documentation names Unity 2022.3.22f1 as its supported editor version and directs creators to use the Creator Companion to install the appropriate Unity version. For creators building Quest content, the documentation also calls for Android Build Support in that editor installation. The useful rule is therefore specific: keep a VRChat world or avatar project on the supported Unity 2022 editor even if the player testing it is running the Unity 6 beta client.
VRChat has explained why this split is intentional. When it launched the earlier Unity 6 client beta in June, the company said it had kept the existing render pipeline and put compatibility measures in place for changed Unity APIs used by Udon, VRChat’s system for interactive world behavior. It said worlds and avatars should remain compatible and asked users to report content that looks or behaves differently from the live client. At the same time, VRChat warned that its servers reject content uploaded from Unity 6. A creator can test existing content against the newer client without converting the project that produces it.
This also gives creators a clearer way to interpret a problem. If an existing world behaves differently in the beta, compare it with the live client before changing the project’s editor version. VRChat treats a difference between the Unity 6 beta and Unity 2022 live client as a bug to report; switching the SDK project to Unity 6 is not its recommended fix. VRChat has not announced a date or migration procedure for Unity 6 SDK support.
Build 1913 fixes specific faults, not a measured Quest speed problem
The Unity 6-related fixes in Build 1913 are concrete. VRChat says it fixed a crash during world loading, another associated with certain buffer-particle setups, and a case in which TextMeshPro.renderer was unavailable to Udon. Those are useful changes for beta testing because a crash or missing API can prevent a world from working correctly regardless of whether its average frame rate is acceptable.
The release notes also report improved frame rate with high-polling-rate mice. VRChat says that issue is not necessarily fixed and that it is working with Unity and Microsoft on a fuller solution. A mouse-specific PC issue should not be read as a Quest performance result: Build 1913 supplies no Quest frame-rate, memory-use, or loading-time comparison. Players may find differences while testing, but the published notes do not quantify a headset performance gain.
Nor does every subsequent 2026.3.3 beta fix apply to Quest. VRChat lists Build 1914 on September 18, followed that day by Build 1915 for Steam only. The latter contains a small fix intended to help avoid intermittent SteamVR soft locks. It is a later PC beta change, separate from the Quest engine switch.
Quest owners can opt in without changing their creator projects
For a Quest player who wants to try Build 1913’s engine change, VRChat documents the opt-in through the headset’s release-channel setting. This is a test build, so VRChat cautions that some open betas can be incompatible with the live network; when that happens, beta users may be unable to see people on the live release. That possibility is worth weighing before switching a headset used primarily to meet friends.
- Open the headset’s Library and find VRChat.
- Hover over its thumbnail, select the
...menu, and choose Settings. - Select Release Channels beside the version information, then choose Open Beta (Opt-in).
- Return to the Library and launch VRChat after the beta download completes.
Those are standalone Quest instructions. Steam’s PC beta uses Steam’s Properties → Betas menu instead, while VRChat says the Meta PCVR client has no open beta. None of these player-side choices calls for an SDK-project upgrade.
What this means for you
Opt into the Quest beta if you want to test how your usual worlds and avatars behave in the Unity 6 client; keep production creator projects on VRChat’s supported Unity 2022 editor. The live release identified in VRChat’s release notes is 2026.3.2, Build 1901, dated September 1, while the Unity 6 Quest change is documented under 2026.3.3 Open Beta. VRChat gives no date in those beta notes for a live 2026.3.3 release.
- Quest standalone players can select Open Beta (Opt-in) in the headset’s VRChat release-channel settings to receive the Unity 6 beta build.
- World and avatar creators should continue using Unity 2022.3.22f1 for VRChat SDK projects, even when testing content in the newer client.
- Creators building Quest content should retain Android Build Support with the supported Unity editor installation.
- A world or avatar that changes appearance or behavior between live and beta is a compatibility issue to report, not a reason to convert its project to Unity 6.
- Build 1915’s SteamVR soft-lock fix applies to Steam; it is not a documented Quest fix or a Quest performance benchmark.
VRChat has advanced Unity 6 testing from a dedicated branch to its regular open beta and added standalone Quest to that test. For creators, the next meaningful change will be an explicit SDK-support announcement from VRChat. Until then, the safest division of labor is simple: test the Unity 6 client if the beta is useful to you, and build publishable content with the supported Unity 2022 editor.