安装 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://psteamcommunity.yuanyoumao.com/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.