Start over by downloading from the Download page found via this group's Overview page.
Unzip the downloaded file to your My Documents or Documents folder.
You should see a Crowbar.exe file and a Data folder.
Double-click the Crowbar.exe file.

Let us know what happens after that last step.

This is by design, based on Crowbar calling the actual compiler program, studiomdl.exe, that typically comes with each game. When using the define bones option, the studiomdl.exe simply writes out the definebone lines.

It seems I'll have to make this more explicit in the interface.

Making a note here that this model uses two bodygroups to make entire mesh. The original problem was Crowbar 0.24 was not decompiling the second bodygroup mesh.

I already explained why Crowbar moves the files. When I made the change, I did not know that other games might require having the models left in the game folders instead of in VPK files. This is why I need this group and the feedback via the discussions. I am already revising the Compile "Output Folder" options to include keeping the compiled files in the game folders where they are originally created.

The option to check the models is done now via the "Use in View" button. Probably not the best label for the button, but this copies the selected MDL file name to the View tab where more info is shown about the model and has the "View" and "View as Replacement" buttons for showing the model in HLMV. Based on my own use of this, I feel it needs a bit more streamlining. The View tab should probably change to the selected game from the Compile tab. Not sure why I didn't think of that before.

The purpose is to keep the game folders clean, because every mod should be in a vpk. Also, keeping the game folders clean prevents a common problem of seeing your mod work on your game, but others not seeing it work because you forgot to include the files in the right place in the vpk.

The QC file dictates how to compile the model. Crowbar tells the compiler (studiomdl.exe) to do the compiling and then Crowbar moves the compiled files to the output folder you chose, which should be where you have organized the addon's files for vpk packing.

Most likely, many modders do not understand the "vpk" way of modding Source-engine games, due to it being a more recent change. I'll probably have to start a new discussion to explain this more fully. For now, just know that you are not alone in not understanding this change.

I am also considering some other options if this change proves to be bad for too many people.

Hiya, CrazyBubba! Glad to meet you. I'll add you on Steam.

I download the following addon from Garry's Mod workshop and decompiled the bullsquid_leak.mdl found within. I saw the same log as in the above report.

https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=251862124

Upon debugging, it seems the PHY file is in an unusual format and will need further investigation.

Reported by MagicalFruitBasket in Crowbar group Comments:

"Decompiling with Crowbar 0.27.0.0: "C:\Users\Home-PC\Desktop\new\Half-Life 2 Leak Prop pack\models\bullsquid_leak.mdl" ...

Decompiling ".\bullsquid_leak.mdl" ...
Reading data ...
Checking for required files ...
Reading MDL file header ...
... Reading MDL file header finished.
... All required files found.
Reading PHY file ...

... Decompiling with Crowbar 0.27.0.0: "C:\Users\Home-PC\Desktop\new\Half-Life 2 Leak Prop pack\models\bullsquid_leak.mdl" finished."

And then i got a folder with nothing in it.

Hmm. Interesting idea. I might be able to have Crowbar write out as much of the equation as possible in a comment that might be useful for redoing into DMX format.

I thought I mentioned this elsewhere, but the failed parsing is due to the expressions being DMX-only expressions that can not be expressed with SMD format. The only fix for these is to decompile to DMX format, which I have planned, but not sure when I will get to it.