Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción










https://steamproxy.net/sharedfiles/filedetails/?edit=true&id=2479456277
Vortex ♀ Pixalation is aware, but did not want to do anything about it at this time, as is their right.
Thank you!
In any case, yes, I definitely agree that the action camera's viewpoint is seemingly the trigger of whatever it is that causes the issue. It may well be just a single specific "matinee" (I think that's what they call the variations on the cinematic camera in the .ini files?) that causes all of this.
What I don't get, honestly, is it's always the burning flames sound that accompanies the white screen, and that sound has nothing to do with whether or not flames are involved in the current battle, in my experience.