安装 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(越南语)
Українська(乌克兰语)
报告翻译问题
For the bones, Team Fortress 2 has things like prop_bone, weapon_targe, heck, even weapon_bone, that the DMX sources don't (compiled into the model using $DefineBone to define bones the mesh doesn't have).
Thus, neither of these are a bug with the Blender Source Tools.
The thing is, I never use the Source SDK resources due to the fact that they haven't been updated in 9 years. All of the the models I am using are the latest models in both SFM and Blender (I make sure to keep the playermodels and animations updated), so there is no reason there should be a problem between them.
Also, it seems importing a decompiled version of a taunt from demo_animations.mdl into SFM causes the same issue, but in reverse.