安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
As far as I can remember, gm_fork wasn't too difficult to make, just very time-consuming. I worked out a technique that made it relatively easy to build smooth roads, but it still required a lot of manual tweaking of individual vertices in order to create height variations and to connect everything to the surrounding terrain. The terrain itself usually also involved moving vertices one at a time, because I wanted to create smoothly flowing lines with more control than what the default displacement sculpting workflow allows for. In hindsight that might not have been necessary, but here we are.
I'd say gm_boreas was a lot worse in terms of difficulty. More switching back and forth between external tools, more custom assets, more interactive things, more optimization work and way more compile limits and random errors that I had to work around.