Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It is easier to crash it than for developers to fix all the possible ways of crashing. Crash prevention is basically just developers tying your hands behind your back about how many creative things you can do about worlds and avatars that you create.
particle crashers - have maybe 10k particles. blocking the avi or using the newly added particle limiter should stop this (theres an exception maybe, read bottom)
light crasher - every light source doubles everything on an avi. so if your avi has 1million polys, and another avi enables a light source, then it'd have 2 million rendered. turning off light sources in safety settings stop this.
blendshape crasher - an avi with a few million polygons that has several conflicting blendshapes, causing massive rendering. mostly used to cause lag. blocking the avi is the only way to stop that
polygon crasher - ? dont think that exists, think above is the only way to crash via polys
shader crasher - dont know how it does it. but shaders are written in code, so maybe theres a bug to abuse or maybe write it so reduntantly that it uses up all the ram? turning off shaders in the shield setting can stop this (and also make everthing look boring). quest is immune to this, but there's an exception (read bottom)
client crasher - used to be a ton of methods in the past. the only one I know works now is the ram overload method, but this needs the target to have your avi enabled. doesn't matter which shield setting you have
all of these (save the last one), would mark the avi as very poor and give a heads up. but sdk spoofers allowed you to change the statistics to trick vrchat into thinking it was a fallback. sdk spoofers will probably die out this month, when the creator companion becomes mandatory. as for shader crashers on quest...any avi uploaded before the new fallback requirements in 2021 were allowed to keep shaders (so yeah, quest can run cutout shaders, and spoofers can still allow quest to run them). so any shader crasher that was uploaded before that, could still work to crash quest If you want to see some crashes, check out "Execrating VRChat Streamers" on youtube