However, all network connectivity outside of other player's movement and voice stops working.
Vrchat panic button update#
The first time I go to The Great Pug after an update to the game/map (with youtube-dl), it works. I'm just playing the game, most of the testing I've done comes as a result of trying to do something with friends and having it crash me.Īs far as "what is the actual problem with the video subsystem", I suspect something on the VRChat side. WindowsVideoMedia error 0x80004001 while reading
Unloading 1 Unused Serialized files (Serialized files now loaded: 2) With Youtube-dl, the same exact thing happens. Without Youtube-dl, that world doesn't crash, however it doesn't play a video either. If it could be used to test to see if this world also crashes VRChat under Proton, that might help confirm whether youtube-dl is specifically the issue or if it is the video player alone. Upon loading, it should autoplay a video from a direct URL.
Vrchat panic button install#
What is the best way to install that/check for Here is a test world that has a Unity Video Player component in it, but it does not use any VRChat video scripts, so it should not call youtube-dl: Whatever Proton and VRChat installed as part of initial setup is all that is installed. I don't see anything for it in the Program Files or Program Files (x86) folders. Youtube-dl requires Microsoft Visual C++ 2010 Redistributable Package (x86) per their Can you confirm this is installed and available for youtube-dl?Īs far as what is installed: I just told Steam to use Proton 3.16-6 Beta (and now it uses 3.16-7 Beta after an auto update). I absolutely plan to keep playing the game for the foreseeable future, so long as it stays in the current state (or gets better). It isn't perfect (see above for the issues), but most of the issues are usually avoidable and manageable. Overall, I'd say that with decently powerful hardware (see my system specs), the game is absolutely playable and a pretty good experience. I'll see if I can reproduce this with Proton 3.16-7 Beta it may have been fixed.
Restarting the game (and SteamVR, if SteamVR crashes) will fix this. If I go to a world where I usually get 45 FPS, it will be consistently dropping below 30 despite me being the only person there. When avatars have really demanding shaders, if I leave the world to other (empty, decently optimized) worlds, I'll often keep having terrible performance. I've also noticed an issue (although I don't know that I've seen it since Proton 3.16-7 Beta activated) where shaders or something seem to keep running. It isn't pleasant, but the game does survive. If anything I've found that I crash less than some other users who run on Windows, as the game seems to handle extremely resource-intensive avatar shaders "well" (The game drops to 1-2 FPS but keeps rendering which allows me to use the menu to leave the world).
Other than that, the only crashes I experience are usually things that crash other users as well (IE avatars with just insane shaders, lots of resource-intensive avatars in a small area). I started noticing that with 1.2.10, but that could just be because I've spent many many more hours using 1.2.10 than using any other version. I've also noticed that opening and closing the SteamVR Dashboard overlay too many times too quickly can crash the game as well. I've noticed this happens more when the game has locked up/crashed however it handles it perfectly fine sometimes. Sometimes when killing the game (clicking the X until KDE prompts to kill wine), it will completely or partially crash SteamVR. Worlds with lots of really fancy shaders also seem to crash the game, but it could also just be something like shader (re)compilation taking so long that I think the game died. Any world that has an auto-activated web player will crash me within a minute, hitting the button to turn it on in any world where it must be activated will crash right away. The only things I've found that consistently crashes me 100% of the time is the ingame embedded web player and some shader-heavy worlds. So far the game has been working fine with Proton 3.16-7 Beta. Since my last system specs post, I think I've bumped to Mesa 18.3.x, but that is about the only notable change. I've put over 100 hours into the game at this point, and can say that it works pretty well.
0 kommentar(er)
