Instalează Steam
conectare
|
limbă
简体中文 (chineză simplificată)
繁體中文 (chineză tradițională)
日本語 (japoneză)
한국어 (coreeană)
ไทย (thailandeză)
български (bulgară)
Čeština (cehă)
Dansk (daneză)
Deutsch (germană)
English (engleză)
Español - España (spaniolă - Spania)
Español - Latinoamérica (spaniolă - America Latină)
Ελληνικά (greacă)
Français (franceză)
Italiano (italiană)
Bahasa Indonesia (indoneziană)
Magyar (maghiară)
Nederlands (neerlandeză)
Norsk (norvegiană)
Polski (poloneză)
Português (portugheză - Portugalia)
Português - Brasil (portugheză - Brazilia)
Русский (rusă)
Suomi (finlandeză)
Svenska (suedeză)
Türkçe (turcă)
Tiếng Việt (vietnameză)
Українська (ucraineană)
Raportează o problemă de traducere
So... exit/restart the game (or whole PC) periodically and get a defragment program that allows you to degrag individual files. Like Defraggler.
Other than that ... probably just the chunk-loading issue, as already mentioned. Not much one can do about that, really...not at this unoptimized stage. It does seem a little worse in 13 than previous versions. More to load I guess, plus loading everything, not just what you can see.
I assume you've tried turning sight-distance of land/trees/grass and such lower to see if that helps at all?
I have 12RAM (+gtx 980ti) and it doesn't even get close to using all sys. RAM at once (less than 40%, in SP) even after hours of the game being on.
I have computers with 16 gb ram as a minimum and I've played around with turning off the swap file and usually it ends up with badly coded windows programs crying and slowing the system down. I would suggest you get an SSD or raid some hdd's together. If it's a laptop then the SSD route is the best to go for.
Linux does not have this problem, and has a completely different swap file management philosophy - don't touch it until we run out of physical ram. The swap file remains untouched until physical memory is close to exhausted. Because of this, you are better off with a swap file in Linux, and without in Windows.
YMMV - don't dinker with the swap file if you don't know what you are doing.
But the current 7d2d client has a memory leak and in time will exhaust all physical ram and start to dip into the swap file and/or crash.
I've found that with Windows 7, if and only if you have enough physical ram, you get better performance by minimizing the swap file. I've done it both ways for years.
The risk here is that you really need 16GB or more because if you are not careful, you do something stupid and run out of memory and crash city. I would never recommend to a client to turn off the swap file, but on my few remaining windows boxex (I've switched most of them to Linux, problem solved), I always minimize the swap file and get better performance.
I totally agree. A large part of the windows swap file issues stem from allowing programs to control what and how the swap file is managed. It's unfortunately common windows practice to use the swap file as on disk storage and not just for extra ram. There are good reasons to give programs control of their swap behaviour but unfortunately plenty of coders do it wrong.
Unfortunately a ramdisk solves plenty of these issues but also invokes plenty more :(.
Windows 2k used to have kernel turning options that allowed the kernel to not swap from ram. now if you have 16 or 64gb or what ever the kernel will still insist on swapping out. It's rather a shame that this behaviour can't be controlled by the user, but hey, what do we know? right? :D
I use dynamic swap and put some of it on a raid array. Even mirrored raid for the read performance boost is much better than a single disk. I find that raid is such a cheap and good performance boost these days that it's well worth the time and effort to set up. Even if it's a cheap $80 raid card it'll still be well worth it.