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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
Many people have been helped fixing issues in the game on the forums. But submitting a bug report isn't bad advice either.
Visual Studio runtime libs are part of the Steamworks SDK/Common Redist. Why would anyone need to update them manually? Do steam install them incorrectly?
Crash files here
I am not saying you have a point but most people which have problems CS have a problem that they do not know how windows or any OS works and windows itself need a pagefile and that can go as 3x your RAM.
The issue is that this game needs a lot of RAM, especially if you have all DLC's and some mods and assets.
How RAM management works in an OS is that everything which is not needed now to run the program gets to push out into the pagefile so it is quickly accessible for the OS but it is not clogging up the RAM which is needed for other more important tasks.
The OS/Windows does NOT know you are only gaming so it doesn't treat CS differently. There is where you problem lies.
So please stop arguing and try to have RAM and a pagefile defined. If it is still failing we can have a look at other issues.
One issue is as well this game does not purge the RAM after you exit the city. That can be said for a lot of other programs as well. The issue again is there that CS eats RAM like peanuts.
First thing you do: set pagefile to at least 2x your RAM. As the base game and all DLC's need about 10-15GB alone you need 8GB RAM (you can only use about 6GB of that) and about 32GB pagefile.
Then reboot the computer and start nothing else! Launch CS. If it works guess what? I have proven my point.
If you still don't, believe me, I am happy to explain you have the RAM works in technical terms!
While access violations are typically not a hardware issues that is not always the case.
Six months ago I started having issues with programs crashing but only those that needed memory above a certain address. What I discovered was that the ram stick in the last slot had gone bad. There was no warning on boot and everything ran fine in Windows until a program tried to use the ram in that last slot.