If someone could look at the Python console and narrow it down to the Source Tools plugin, they might, in theory, be able to copy and edit huge amounts of the code to make it more GoldSrc friendly, albeit a little more unstable.

But obviously, that doesn't help us here; I'm just theorizing.

As for the Milkshape thing...

If only there were some other way to obtain a keycode for activating the software, a way to obtain a key for no cost, a tool of some sort that could generate a keycode.

Sorry I'm not super helpful. Have you tried consulting any of these?

https://developer.valvesoftware.com/wiki/Blender_Source_Tools_Help
https://steamhost.cn/steamcommunity_com/groups/CrowbarTool

I've had that issue. In fact, I was working on a custom model earlier this summer, and I had to set it aside cuz I got bogged down with work, and didn't have time to figure out how to fix that exact problem.
I assume you're exporting the mesh that has the skeleton tied to it as a .SMD file, so if you're doing that, we could eliminate the filetype issue.
Is the skeleton set as a "parent" to the mesh, or did you set it as an armature that the mesh is tied to? They both serve the same purpose if done properly, but sometimes there can be noticeable differences when working with them.
I might open up the Blender file for my model, to try and see what the exact issue was and compare it to yours. Maybe we'll come up with something.

Edit: another thing you could try if you don't get a proper answer from someone who actually knows more about the Blender Source Tools than I do...
try exporting the mesh, uv maps, etc. to Milkshape 3D, and if you can't import the skeleton into Milkshape 3D, then just create a quick, lazy rigging for your mesh, export it, and see if that works in HLMV. It might just be that the Blender Tools are oriented towards the Source Engine so much that it's harder to work with GoldSrc.

First off, I love your content.


You can decompile GoldSrc models into .qc, .smd, and UV Map files, which you can then just import into Blender. It includes the rigging, the textures, the animations, etc.
It's been a little while since I've used Blender for GoldSrc modding, so forgive me if there's been an update that's changed what I'm used to, causing everything I just said to be incorrect.
What is it specifically you're looking for to be improved in the import/export process?

Personally, one issue I've had is when Jed's model viewer's compile command line will say that a bone is in error, or it's missing a texture that's been applied and sorted properly.

Ok, thanks; sorry for all the trouble, I'm kind of a noob at this.

Alright; where is the UV map file found?

Ursprungligen skrivet av Zappy:

Didn't you notice this part, levit123?

Ursprungligen skrivet av Zappy:

Secondly, no, Blender Source Tools doesn't import textures nor materials.

Dang, I must've missed that.
So, once I manually apply the image to the mesh, is there any way besides UV mapping to properly align the image?

Ursprungligen skrivet av Zappy:

Ursprungligen skrivet av levit123:

Import Textures Using .qc File?

Firstly, why not SMD/DMX? They have the material names, after all.
Secondly, no, Blender Source Tools doesn't import textures nor materials. (Although it makes basic materials tinted differently so one can tell each material apart.)

Oh, ok, I'll try SMD/DMX, see if that works.
Thanks for the help.

So, I've used Blender Source Tools with GoldSrc models, and it's been a breeze. But, I've decompiled some Black Mesa models, and, when working with them in Blender, everytime I import a .qc file, all of the necessary .smd files get imported, but the textures are not imported.

I've extracted the textures to a folder on my desktop using GCFscape, then converted them to .tga files, but I noticed that the .qc file lists the texture as: $CDmaterial models\humans\hev_gordon\hev_suit_d

Do I need to extract the hev_suit_d texture to a specific folder in the Black Mesa steam folders? Or should I change .qc file in some way?

Any help would be greatly appreciated; thanks.