安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
http://steamcommunity.com/app/421120/discussions/0/392184522710453226/
Uninstall your display adapter drivers in your device manager until you're using the default microsoft drivers... then play Samorost 3. Your framerate will be horrid and the game will be pretty unresponsive but you might be able to get through the area and then continue playing on the other side... :(
I'm just going to wait for a solution...
Have surface pro 4.
Game crashes after getting in the boat with the monk and moving to next screen.
Well, the game doesn't completely crash. There is still sound, and even the cursor (if I reload), but a blank screen. A real bummer!!!
I would love to hear from someone who has managed to find a a decent fix/workaround to this.
Is this a problem restricted to surface pro 4 owners? The other people solving the problem own laptops/comps with an NVidia card as well as the Intel.
Plan B is to install it on my old clunker laptop.
My scenario was:
1) Force NVidida Titan X to be used for Samorost
2) Finished the game
3) Switched back to intel card and wanted to reproduce the crash (monk and big animal screen)
4) It did not crash again
Also the GPU which has a problem is dedicated NVidia or integrated Intel? I would recommend using the dedicated GPU as it makes big difference over just integrated one.
Yes the problem is Surface Pro 4 only has the Intel chip and no other GPU. The fallout fixes probably won't help as they were NVIDIA issues. It's a real bummer because Sam3 is AMAZING on the Surface Pro. Just crazy beautiful.
I will try Hammerheart's suggestion of rolling back the driver when I get the chance.
Thanks for help everyone.
unfortunately, the patch has not fixed the issue on SP4.