Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский — Испания)
Español - Latinoamérica (испанский — Латинская Америка)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский — Португалия)
Português-Brasil (португальский — Бразилия)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом










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.