No Model Compiling Makes Me a Dull Boy Created 16 years ago2008-01-02 23:12:30 UTC by RotatorSplint RotatorSplint

Created 16 years ago2008-01-02 23:12:30 UTC by RotatorSplint RotatorSplint

Posted 16 years ago2008-01-02 23:12:30 UTC Post #242358
So... the Orange Box keeps breaking one thing right after an other.

I'm trying to compile a model for Episode Two, but I get a big fat error every time I run StudioMDL. If I run the Orange Box version of the compiler (by that, I mean the executable found in sourcesdk/bin/orangebox/bin/), this is the error I get:
User posted image
There are two of them, the second poping up after I close the first one. Then StudioMDL quits and I have no model.

If I run the Episode One variant of the compiler (sourcesdk/bin/ep1/bin/), this is the error I get:
User posted image
The compiler quickly displays that and immediately quits (It was hard to get the screenshot), and I still don't have my model :heartbreak: .

The same exact errors are returned with models that previously compiled properly and now no longer work, so I know it can't be some syntax error I may have made. I've also tried cycling through starting the SDK in both the Orange Box and Episode One modes. No go.

Please help meh. :nya:
Posted 16 years ago2008-01-10 17:26:18 UTC Post #243130
So no one has any idea how to fix this problem? :heartbreak:
Posted 16 years ago2008-01-10 19:51:17 UTC Post #243153
nope.. :x
TheGrimReafer TheGrimReaferADMININATOR
Posted 16 years ago2008-01-10 20:14:01 UTC Post #243160
have u tried a re-install?
Posted 16 years ago2008-01-11 18:02:12 UTC Post #243220
You should include "-nop4" command (e.g. studiomdl -barney.qc -nop4), while compiling models for the Orange Box version of engine.

You can also try “refreshing your SDK content, and “resetting your game configurations”.

There is another popular (rare) bug, causing studiomdl to crash. To prevent this from happening, you have to create folder(s) for your model, instead of letting studiomdl to create them for you (automatically).
You must be logged in to post a response.