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



When you import a VTA file using the Blender Source Tools, it will try to match the VTA file's "reference" vertice positions to the mesh object you have selected or such. Then any of the "reference" vertices that are close enough to vertices of the mesh object will affect those vertices for the flexes.
But if any "reference" vertices are not close enough to vertices of the mesh object, the Blender Source Tools will create an object with vertices in the "reference" vertice positions, for no purpose other than to help you manually identify where any unaffected vertices of the mesh object are supposed to be for the flex(es) to be imported correctly.
Again, the vertice-only object has nothing to do with exporting VTA files, only being able to identify where vertices should be for importing a VTA file properly.
As for exporting VTA files, this happens automatically when you export an SMD file with an object that has shape keys in Blender (which should be the mesh object that has polygons everywhere, not a vertice-only object).
It might be worth considering using DMX instead of SMD, as then the flexes will be embedded within the DMX mesh export while not requiring you to do any flex-related stuff in the QC file, as opposed to being in a VTA flex export, requiring flex-related stuff in QCs, separate from an SMD mesh object.
Thanks for your reply, I'll give it a go and see!