安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
looked online for any answers have found none, game settings are completely stock no change to graphics or anything default settings
I also updated the graphics drivers, and went as far as to drop my resolution from 4K to 2560x1440 & played in a window, with the same result.
By thee way, I came across a player on Reddit who was having the same problem, and that person also had a 1080 Ti. I hope it is not a problem with this card (especially as it is VERY HARD to replace these cards right now.)
Just tried that - didn't work (the game window stayed frozen.)
What is interesting is that only the game itself is being affected - other programs can be opened and ran with no problems, and I can close the game window without bringing the rest of the system down.
Intel Core i7-8750H @ 2.2 GHz (@4.5 GHz), 12 Threads
NVidia GeForce GTX 1070, 8 GB VRAM
Windows 10, 64 bit, 32 GB DDR4 RAM
Having the same problem, but only when I try to go into space. I'll launch off the planet, and within 20 seconds or so it will freeze on a frame, say the solar map. But I can still hear the mech flying, I can move it, I can pull up other screens like the dyson management screen or the guide screen, even pause the game, but I can't see any of it. If I leave it running long enough and the game autosaves, and I load that autosave, I can tell the game was running while I couldn't see due to the mech being far from the last known position (by that I mean where it was when the bug occurred). Only way out is Alt-F4 or taskmanager.
Before bug, I'm running about 10-25% CPU, about 20% RAM (I think, didn't really check it oops), and 99-100% GPU*. Disk utilization is low, about 0-15%.
After bug, I'm running a pretty consistant 17% CPU, about 10-20% RAM (I can't remember, didn;t see it as important), and 0% GPU*. Disk utilization is about the same, 0-15%.
*These are from taskmanager, I haven't run the game while watching GPU-Z or anything yet so I'm not sure what the actual CPU and GPU loads are, or if there's a perf-cap going on.
It's a really weird bug, I haven't seen anything like it but given the massive disparity of my GPU loads pre and post bug, and the fact that I can tab out and the PC runs just fine otherwise, I think the game is getting stuck in some sort of loop? Like it borks up for a second and then just keeps telling the GPU to display that one freeze frame while the rest of the game continues on like nothings wrong. Idk, it's very strange, hopefully it's an easy fix, like a game setting or something.
But when it actually occurs is super random. Sometimes I'll get it within 5 minutes of turning on my computer. Other times I'll be playing the game for hours before it occurs. And most of the time I never encounter the issue.
[Edit] Specs, I suppose.
Intel i7 6820HK @ ~2.7 GHz
32 Gigs RAM
NVIDIA GeForce GTX 980M
I'm on an i7 8700k and GTX 1080, both heavily OCed (but under water so they stay super cool) and have had absolutely zero issues with this game as far as crashes or performance problems.