Ooh, ancient thread.

So in my experience with the error, which I'll write out to save time,

ERROR: 'EXCEPTION_ACCESS_VIOLATION' (assert: 1)

is that there's way too much going on with the model. Can't remember if it's bones, vertices, bodygroups, faceflexes, all of the above; that's usually when the error shows for me.

You need to enable the zombie skins within Spy's main SMD file, it's either called "reference" or "morphs_low"; that's most likely still using "spy_red" and "spy_head_red" regardless of what your QC says.

SMD files can be opened in Notepad, so when you do that, hit Ctrl+H and replace "spy_head_red" with "spy_head_red_zombie_alphatest", and "spy_red" with "spy_red_zombie_alphatest".

Okay this one's a legit bug this time, promise.

When decompiling with 0.68, pieces of the model if not a majority of the model go missing. For example, when decompiling TF2 Pyro, only a corner of the pack is what survives. No errors in the decompile log, and this issue isn't present in 0.67. Feel free to poke on Discord for pics and/or faster communication.

Good news, nothing to do with Crowbar, I just got the same error when launching TF2 in general, so things are straight up broken on my end, adjlkadlsa

Go ahead and delete or archive this thread, my bad.

I hope to gods this isn't some random wacky error again, but I suddenly can't get Crowbar to compile anything, even if I make zero changes upon decompiling, and it spills out this error:

// Created by Crowbar 0.67

Compiling ".\demo.qc" ...
Output from compiler "D:\Steam\steamapps\common\Team Fortress 2\bin\studiomdl.exe":
Tried to add D:\Steam\steamapps\common\Team Fortress 2\tf\custom\sound as a search path.

This is probably not what you intended.

Check D:\Steam\steamapps\common\Team Fortress 2\tf\custom\readme.txt for more info

CROWBAR: Deleted empty temporary compile folder "D:\Steam\steamapps\common\Team Fortress 2\tf\models\player".
... Compiling ".\demo.qc" finished. Check above for any errors.

EDIT: Apparently it's the TF2-specific compiler that's doing it. Swapped over to GMod's compiler and it worked.

Make sure your Crowbar is updated to 0.67, there was an issue with 0.66 that destroyed models similarly to this. I just decompiled Spy with the new version and there's no errors.

Crossed everything out since it was apparently some odd fluke on my end, feel free to archive, pfft.

This is with the newest Crowbar, 0.66. Upon decompiling a model, well--
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1982459217
I looked into the files and it commented out everything within the .smd file except for a couple places. After removing all the '//' lines and attempting to compile with that, Crowbar gives me this:

SMD MODEL w_scattergun_reference.smd
WARNING: unknown studio command "Created"
ERROR: bogus bone index
15 w_scattergun_reference.smd :
39 1.000000 0.000000 0.000000 0.000000 -2.627628 4.831095 7.507513 1.886843 63 39 0.954415 136 0.000548 98 0.122333
ERROR: Aborted Processing on 'weapons\w_models\w_scattergun.mdl'
WARNING: Leaking 1 elements

Issue seems to occur with every TF2 model I attempt, tried with Demoman next and every .smd file had the issue. Swapped back to version 0.65, issue doesn't exist.

Meant to report this with the last update, whoops--

So the 'Update' tab has a 'Check' section, 'Download' section, and 'Update' section, all self-explanatory. The 'Check' and 'Download' sections function as expected, however the 'Update' section only downloads the update as a .7z file without actually installing it. Checking 'Update to new folder' installs the file in the specified location like the 'Download' section, but unchecking the option downloads it--some place I have no idea--

I got Crowbar to somehow restart itself once after attempting to update, but it came back with the previous version instead of updating to the new one. Doing this also causes a '7-Zip Reduced Standalone Console' to run, not sure what that is exactly-- I can provide images through Discord if needed.

Originally posted by ZeqMacaw:

While working on the bug where all model vertices are written to a VTA file instead of just a bodygroup's vertices, I realized that was probably the cause of the weirdness with Heavy's recompiled model. After some testing with heavy and two other models from different games, my realization proved correct.

Thus, this reported bug will finally be closed, and the fix will be in next release.

It only took me 4 years. :rfacepalm::lunar2019crylaughingpig:

Hey hey, you still did it in the end, power to you.