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



Don't use Blender to compile models.
Seriously, though, it's recommended to use the command-line StudioMDL itself manually, or using a third-party tool (like GUIStudioCompiler or something).
Well people do it, and it can be done, so that answer doesn't really help me. I also can't find a tutorial post steam pipe update. but I will continue to try using crowbar, blender, and everything else I can find until I can get a model with a texture from one of them or someone actually answers my question.
Also, if this is of any help, this is the command-line thing I use to compile models for Team Fortress 2, which works after SteamPipe:
"F:\SteamLibrary\SteamApps\common\Team Fortress 2\bin\studiomdl.exe" -nop4 -r -game "F:\SteamLibrary\SteamApps\common\Team Fortress 2\tf" "[QC path and filename].qc"
The first thing is the path and filename of StudioMDL (Source FilmMaker also has a StudioMDL included, but Garry's Mod doesn't, so it depends on the game), the -game variable is, well, pointing at where I want the model to be outputted (it must have a proper gameinfo.txt), and the last thing is the QC to be compiled.
Sure, it doesn't really help with compiling in Blender nor other third-party tools, but it may still help you with compiling in general.
Please also upload your blend file: http://www.pasteall.org/blend/
*EDIT* Nevermind