Since a few days ago I noticed a significant drop in fps. Usually by myself in my homeworld the fps is stable at 80 but won’t go above 40 now. With other players it can go down as low as 20.
Noticed the fps drop happened around the same time a lot of avatars loaded in as the error robot model and world thumbnails showed “no image” .
Using a rift s on windows 11 with the following specs :
i7-12700K , 3070ti
It’s often (Very Poor) avatars. “[Performance Stats]” in full output logs may give a clue to cause, if you want to share those performance stats from output logs here.
Note “Asynchronous Spacewarp” (Meta Quest) / “Motion Smoothing” (Valve Index) may also cut down the framerate in half when going below the refresh rate.
Without full output logs to diagnose, my best guess is you may have the Intel Killer Network Services task running. Reported on Canny: Cant load images or most avatars | Voters | VRChat
Apparently there was a performance regression in VRChat 2026.1.3 that went live. (Source: 1, 2)
@Miku_Miku_Mii Could you please try with the perf-test beta branch and see if it improves the performance for you?
- In Steam, right-click VRChat, select “Properties”, then “Game Versions & Betas”.
- At the bottom, enter the code
LetsGoFastAgain. - Opt-in to the
perf-testbeta branch.
Then, play VRChat as usual.
Tested with the beta branch and it restores my performance to what it was before the update.
Seems there is something in the current build that causes mirrors and some lighting effects in particular to cause heavy frame drops.
Thanks for the help and info, guess at this point I will just have to wait until the next update.
Great. If you’re in the VRChat Discord’s #open-beta-discussion channel, the developers would like to know your feedback this has solved your performance problems.
Do you still have issues with VRChat 2026.3.1p1 (Build 1819)? Another user on Canny (linked in my previous post in this thread) reports this build still has performance issues present, despite the changes.
The problems are still present in the current build of vrchat so I am guessing I am affected by the same issue as the other user.
