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