Originally posted by Sandslash:

On it - I've tried decompiling female0, female1 and female_wraith

I've got a feeling it might be something with some language option somewhere in windows, but who knows.
https://dl.dropboxusercontent.com/u/6252145/extramodels/ltc_scifi_citizens_mdl.zip

*snip*

I have looked at the files and all the ones I looked at have the very first byte missing. For example, the female_oo.mdl file starts with "DST" instead of "IDST". The expected first byte of the phy file is also missing. The missing first byte in the phy file is what causes the UTF-8 error, because the file is corrupt (i.e. it is not in the right format for Crowbar to read it).

Having looked at the female_oo.mdl file further, the internal file size field (where it should be in the file) matches the actual file size, so I looked at the very last byte of the file...and there was the "I" that should be at the start of the file. Somehow you got files where the first byte got moved to the last byte.

:)

Yeah, maybe a language setting in Windows is causing a problem. What "Region and Language" Format are you using? Mine is English (United States). I have experienced odd errors like this in my other programming, so I'll check out different formats while using Crowbar.

Likely, I have already fixed the error you get with the Female_wraith model.

:)

Decompiling mdl files that are used with $includemodel ($include is something different) are usually paired with ani files, and that feature is already on the ToDo list.

I should post a topic with my ToDo list.

:)

Hmm, interesting about the utf-8 characters. I'll look into it.

Edit: Would you zip and link me to the model files (mdl, *.vtx, phy, vvd files for the one model) you tried to decompile that caused that error? I downloaded and decompiled all models from the "Sci-Fi Citizens v4" addon on the Garry's Mod workshop, but they all decompiled without error.

:)

Ha. Check the announcements.

:)

This particular bug (the one with "at Crowbar.SourceQcFile.WriteHboxRelatedCommands()" at top of Call stack) has probably been fixed in a dev version to be released sometime this month.

Sorry for the delay.

:)

The quickest fix for the error would be to comment out the line giving the error. Commenting out just that one line allows it to finish compiling.

=== A short tutorial of how I went about getting around the error. ===
For example, when I try to compile the given model on my computer, I get this:
"ERROR: c:\users\zeqmacaw\downloads\crowbar tool tests\bayonetta_decompiled_0.12 from [vie]@dragon\decompiled_bayonetta\bayonetta_hlmv.qc(75): - Rule for unknown flex NULL"

It Gives the file name of the qc file and the line with the error in parens: (75). So I open up the qc file in Notepad++ (or any good text editing tool), and go to line 75. This is what I find there:
%NULL = NULL
This is related to face anims, and for some reason either Crowbar put something in that isn't used, or missed something. For now, let's comment it out, using two slashes at the start of the line, like this:
// %NULL = NULL
Save the file. Click, in Crowbar, the appropriate Compile or Recompile button. I am using Recompile because I still have the attempted compile still in Crowbar.
======

Thanks for the model files; I'll fix Crowbar as soon as I can to properly decompile that model. (There are also several other models that Crowbar still messes up on those particular set of lines.)

:)

It looks like Maya's SMD plugin is wrong. It is probably expecting no space allowed at start of some lines, but spaces *are* allowed. The plugin should be fixed, not Crowbar.

Actually, I have spoken directly with the MESA developer before about this. It sounded like he was going to fix it.

:)

:D

I (and probably many others) would very much appreciate seeing Crowbar used in tutorials.

I plan to work on Crowbar next month. I'd like to fix Crowbar's problems with decompiling Dota 2 models, specifically, but also try again to fix animation decompiling.

:)

That's text straight from studimdl.exe.

I've seen those kind of errors before, and it seemed to be from having options that were not allowed together.

I just noticed there is a line with just the following. It could be the problem or could be from the post being re-formatted:
Cloaking

:)