安装 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.
thanks for that info btw never knew what that nonsense was at all, I believe it only seens to occur with the action camera on
But, again, I believe that was just the mod author's best guess. It seems to be a fairly hard-to-pin down bug. (I was convinced it was Cinematic Rapid-Fire myself, but I uninstalled and still have had that glitch.)
As Vortex has said, he's gotten it with an un-modded game (I never have). Perhaps the camera mods (and others?) just make the glitch way more likely.
Are you using any camera mods? According to (if I recall correctly) the author of the "Updated Improved Camera - WOTC" mod, this is an engine bug that can pop up with any camera mod that goes to 45 degree increments.
His suggestion was to mitigate ending your turns at the 45 degree angles (that is - end your turns at default camera angles), and it seems to work well enough in my experience to vastly decrease the "white screen + fire sounds" bug.
My apologies for blaming your mod. Yours is the first- and last i`ll blame.
Please don`t worry. I understand, the internet and comments section can be a hostile place. People don`t know how to be polite. Thankyou for understanding.
I`m still looking at the issue and testing. Will get back to you.
Perhaps it`s not your mod- perhaps it`s a combination of things, but believe me i`ve been trying everything from new graphic drivers,changing all my pc settings, even going into the BIOS and changing that. I`ve reinstalled Xcom 2 twice and re-added the mods, taking some mods out and so far it`s calmed down when I removed this one. It may not be your mod but all my pc problems have started from when I put this one, plus a couple of others in. I have never had these problems before then.
I`m still testing. I will update if I find it is not your Mod and apologise.
This has been going on for days causing all kinds of weird lockups even when not playing the game.
I took off this mod and all seems ok so far. I just read below something about it `running off the cpu`? So i`m pretty concerned this mod is at serious fault. However, it could be in conjunction with a couple of other mods, but haven`t figured out what they are yet. Anyway, without your mod so far, so good.
- In my testing, any mod that's compiled with the new SDK will not work with the legacy version, even if there are no WotC-specific changes. The reverse is not true - legacy mods will still work in WotC (assuming no code-changes are required)
.exe is
bDisablePhysXHardwareSupport=True