Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
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