安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
If your disabling mods, remember not to try the same save (go back to before you added them, or start a new game). it won't end well otherwise, as the game will still have those mods within the save. It'll just break things.
Only thing you can do to test is disable the mods, start a new game, and run there (which you can do at level 1)
Then, reenable and try it again. If it crashes you know it's a mod causing it. If it doesn't, your mods are good, and the current save is broken.
Then try disable all mods and reload your current save.
If that does not work you may have to disable all mods and start a new game. As noted you can run straight to Far Harbor. That sucks I know.
The other thing you can do actually, maybe do this first, is do a hard save and then delete all your quicksaves and auto saves. You can get save file corruption on the PS4 just like you can on the PC, from repeatedly overwriting the same auto saves and quick saves, and the symptoms can be very weird.
Worst case you may have to reinstall the game. Be careful to save your save games to Cloud save, BUT, beware also that your saves may be 'contaminated' with corrupt data.
Another approach is to go back through saves, most recent first, and if they error out, delete that one, and go to the previous one. And so on. This is after disabling all mods.
With the PS4 you do not have a lot of options when things go wrong. Luckily they do not go wrong very often (except for mods), otherwise Sony get Todd in their back room and starting adjusting his number of digits.
So I ran around on Far Harbor for a while, making sure to go to one spot that it always crashed and had no problem at all. Smooth as silk. So I enabled the mods... and crash. So I started going through each mod until I eliminated all but one. Turns out the unofficial patch was the culprit.
So I'm pleased. It means I can play it. In a couple of months when I do another playthrough I'll have something new to look forward to. I'll just start without the unofficial patch, play Far Harbor sooner rather than later, and enable to patch when I've finished.
I wouldn't have thought to do this unless you'd suggested it, and had written off ever getting to play it. So thanks.
I'm wondering if I should let the patch guys know about this.