安装 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 a test, I've now switched to using the original 256x256 .tga converted to indexed color PNG - and it seems to produce very accurate polygons.
But you didn't use this method because of some problem with it that I'm missing?
(well, other than having to adjust a bit the origin coordinates in the .pgw due to the size difference)
What exactly prompted you to create a huge layer of zones in heightmap's size?
(I hope my terrible English doesn't confuse you)
Thanks in advance!
I can add a json export to the tool for that pretty easily, at least, assuming I finish and release it someday. Today is not that day, but maybe soon, IDK, still need to solve a few issues
https://imgur.com/a/x3xQ0Dg
I ended up writing up a decent summary of the file format, in the process of trying to talk myself into understanding it, might as well post it in case anyone's interested:
https://docs.google.com/document/d/1hJL2xCvnHT40zjKlKTJ5jyBQFcw5oxTBr-xcB3gFmT0/edit?usp=sharing