Problem with the HL2 custom sequence tut Created 17 years ago2006-12-12 20:49:05 UTC by ultragamer ultragamer

Created 17 years ago2006-12-12 20:49:05 UTC by ultragamer ultragamer

Posted 17 years ago2006-12-12 20:49:05 UTC Post #205929
Yea I was looking on this tutorial http://www.twhl.co.za/tutorial.php?id=102 :lol:. And i read it, it was all working fine, then I made the studiomdl.exe shortcut to my desktop :|. Then dragged the male_06_sdk.qc to the studiomdl.exe shortcut, it only decompiled for about 4 seconds. So i do what it saids and open up the source sdk half-life model viewer :quizzical:. select file/load model.... Then look for the models/sdk folder. It's not there :tired:. I don't see an sdk folder in the models folder. can any of you guys help me out please? Thanks :glad:. Because it would be awesome to make my own animations :lol:.
Posted 17 years ago2006-12-12 22:13:41 UTC Post #205937
Open the file male_06_sdk.qc in any ASCII editor (Notepad, notepad++,context, etc.) and find the line:

$include "../male_animations_sdk/WeaponAnims_shared_sdk.qci"

Comment that line out by prefixing the line with // to get:

//$include "../male_animations_sdk/WeaponAnims_shared_sdk.qci"

Save the file and try it again.

Unfortunately, since that tutorial was written, the SDK has been "updated" several times. The "updated" studiomdl.exe now produces errors which it did not in the original release. Also, unfortunately, Valve did not update the files which produce the errors. WeaponAnims_shared_sdk.qci is one of those error-producing files.

Please post to let us know if that works (it did for me).

Also, get a copy of the Context editor and setup the F9 key as the user command:

C:Program Filesvalvesteamsteamapps[your username]sourcesdkbinstudiomdl

Pressing F9 in Context will compile an open qc file using studiomdl and capture the output so you can see what errors (if any) it produces.
Posted 17 years ago2006-12-12 23:39:51 UTC Post #205940
AWW SWEET :glad:. The compile proccess was a ton longer and I think it works now, thank you.
You must be logged in to post a response.