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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
The .NET framework that is in the Steam directory would not install on a 64 bit machine. I downloaded the latest .NET 4.5 from Microsoft but it still wouldn't work. That's when I realized that perhaps it was the reduced privileges of the guest account that might be causing the problem. Logging in as administrator solved it, and the game started up normally. I tried running the executable from the Steam directory as administrator but it didn't work. I actually had to log off the guest account and log in as administrator on my PC for it to work. I'm not sure what's happening here.
I still haven't played it yet, since I was so happy to get passed this startup bug that I wanted to share. The game must be trying to access some part of the drive that it shouldn't have access to, and the windows guest mode is really strict about that. This is not the first program that I've had this problem with, but it isn't very common. It would be nice not to have to log in as administrator every time I want to play this game.