The picture can't be viewed with that kind of link, only your computer can see that, but make sure you have every file for the model in one place before you decompile rather than just the .mdl file. You're missing the .dx80, .dx90, .sw, .vvd, and .phy if available.

Updated the "Expected" area after decompiling the same model with 0.19.0.0. Even with that, the eyelids were still a tad wonky, but at least they were parsed.

If it's the same 'googly eyes' I'm thinking of, you need to add $upaxis Y into the QC. It flips the model, but the eyes roll around properly, so you'd just need to decompile and recompile a few times to get the model standing right again. Not sure if there's a better way to do it.

Crowbar's always been a tad funky with the eyelids, so you'd have to edit those lines. I'm not sure what would be the best lines for the game, but I've always used these when making ragdolls for Garry's Mod:

%CloseLidLoL = 0.5 + (left_CloseLid / 2.0) - ((multi_CloseLid / 2.0) * (1.0 + left_CloseLid))
%CloseLidLoR = 0.5 + (right_CloseLid / 2.0) - ((multi_CloseLid / 2.0) * (1.0 + right_CloseLid))
%CloseLidUpL = 0.5 + (left_CloseLid / 2.0) + ((multi_CloseLid / 2.0) * (1.0 + left_CloseLid))
%CloseLidUpR = 0.5 + (right_CloseLid / 2.0) + ((multi_CloseLid / 2.0) * (1.0 + right_CloseLid))

As for the textures, my friend and I have been getting those errors as well and sadly neither of us know how to fix it. It never used to happen before.

Originally posted by ThatAnthroGamer:

Here's the image I took a few days back. https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=548012253

Apologies for the late reply. That screenshot might be Friends Only or Private, so I'm unable to see it.

Originally posted by DirtyVenom:

Same problem, trying to get a NSFW model to work. (Yes, I know I'm horrible.) So I can't post the .QC, but it keeps giving me this error

"1. Read http://www.valve-erc.com/srcsdk/faq.html#NoGameDir
2. Run vconfig to specify which game you're working on.
3. Add -game <path> on the command line where <path> is the directory that gameinfo.txt is in." I've tried running Vconfig, it just gives an error and crashes. And that website is down now, so I'm screwed.
Please help ASAP.
The error Vconfig is giving is "Can't find steam app user info"

If I'm reading the error right, it seems that you haven't set up the path of the game you're compiling for. In the Compile tab there's a "Set Up Games" button that should be able to help.

I'm not sure what you've tested so far, but I'll just list everything I usually do if I ever get texture errors:

- The $basetexture in the VMT file is correctly pointing to the VTF file.
- The $cdmaterials line in the QC is the same as the materials' folder path to said VMT and VTF files.
- The $texturegroup lines correctly match the corresponding VMT file names. (personally for me I don't write the folder paths in this area in case I decide to change things around later)
- The lines in the SMD file(s) also match up with everything else.
- There are no other overriding files from other models.

The latter with the SMD files used to be a big issue with some friends of mine because they would change the original folder paths to where their VMT and VTF files are, however in the SMD it would still hold the original path and tried to search for the textures there. Another thing to check would be if there's already a c_rope_red/c_rope_blue file existing, but pointing to a nonexistent texture.

I'm not sure if either of these are correct, but it sounds like either the eyes are locked on the center of the map or they're not following the model's axis properly. Something like that, but in your QC file try adding "$upaxis Y". It'll flip the model over, but if it fixes the eye problem, then you just need to decompile and recompile the model a few more times. If it doesn't, maybe send a screenshot of the eyes so we can see what they're doing exactly.

Crowbar Version:
0.33.0.0

Steps Taken:

• Extracted a mercenary's model files from Team Fortress 2 (tried with all nine, though using scout.mdl specifically here)
  
• Decompiled model with the following checked:
  
  • QC file
    
  • Reference mesh SMD file
    
  • Bone animation SMD files / Place in "anims" subfolder
    
  • Physics mesh SMD file
    
  • Vertex animation VTA file (face flexes)
    
  • Procedural bones VDR file
    
  • Format for stricter importers

Expected:

Issues

// [Decompiler failed to parse expression. Please report the error with the following info: this qc file, the mdl filename that was decompiled, and where the mdl file was found (e.g. the game's name or a web link).]
// [Decompiler failed to parse expression. Please report the error with the following info: this qc file, the mdl filename that was decompiled, and where the mdl file was found (e.g. the game's name or a web link).]
// [Decompiler failed to parse expression. Please report the error with the following info: this qc file, the mdl filename that was decompiled, and where the mdl file was found (e.g. the game's name or a web link).]
// [Decompiler failed to parse expression. Please report the error with the following info: this qc file, the mdl filename that was decompiled, and where the mdl file was found (e.g. the game's name or a web link).]

QC File[pastebin.com]
MDL Filename :: scout.mdl
Origin :: Game's default file, tf_misc_dir.vpk

Operating System:
Windows 8

Notes:
Normally I would only see this kind of error among the hardware morph models, though I think this issue started a while back, I can't remember which version exactly. The 'Expected' example came from an older decompiled model from version 0.19.0.0 (jeez, that was a while ago--) and sadly I can't remember which version first began spitting out this error. I think it might have been mentioned with this:

In the QC file, eyelid lines might have incorrect lowerer and raiser frame values, due to Crowbar having to guess which eyelid frames are which. Not sure if there is a way to figure out which frame goes with which lowerer and raiser.

Though that was when the eyelids would still recompile correctly rather than giving an error. I also found this thread from Pte Jack back in July, but that refers to the hardware morph models and not the standard.

If the model is shown as an effect rather than a prop, that's because the model is missing the .phy file. If the original model had one, just copy it over and rename it if you need to. As for the eyes, are they not following the Eye Poser Tool correctly or do they seemed locked on a seemingly random position? Or is it something else?

I've seen this bug usually among hardware morph models and figured that's just because the flex files were too... complex, or something like that. It never showed up with the standard models, however I just noticed the bug happening with them now as well, but only for the eyelids. I think it started happening with the newest release of Crowbar or another release back, though I'm not entirely sure since I haven't decompiled the models in a while.

To fix the pupil part, the line "$upaxis Y" needs to be included into the QC file. I'm not sure if it matters where, I usually place it near the beginning after the "$modelname" line. It flips the model, but the eyes will be lined up properly. If someone wants to make the model stand up properly again, they'll need to decompile and recompile a few times until the model comes full circle, and "$upaxis Y" needs to be included in the QC file each time.