安装 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(越南语)
Українська(乌克兰语)
报告翻译问题






that do not use the same 2 ♥♥♥♥♥♥ base templates
there are so many concepts that I made and which were
dead in the water because of how limiting the 2 base
templates are
What matters in the end is creators having access to more advanced tools. Given Valve's recent support for V-script in maps and similar, propositions outlined in this submission are entirely within Valve's reach.
this submission looks nothing more than a painting rather than a prototyped solution. get real for a minute
As for setting these values per group: it's impossible with the current way patterns are handled within the game. Values and attributes like orient. lock, albedo tint, etc. must be done per-texture. Groups are only a means to apply each texture onto each weapon per its' set values.
Lastly with custom war paints: that's what the UV paint window's for.
You have completely wasted your time even coming up with the idea of this, let alone making anything and uploading it. Valve are not interested in anything that requires any kind of effort on their part.
Oooh, now we talking!~