Hm. That sounds interesting. Thank you for responding.

Note: The following is directed at Artfunkel.

Before "Mark as sharp" was implemented in Blender 2.70 or 2.71 or whatever, were there plans for using the Edge Split modifier to make sharp edges sharp when importing SMDs and DMXes?
And after "Mark as sharp" was implemented, have those plans changed to-/were plans made for- using sharps in the same way as the Edge Split modifier was to be used?

I'm not bugging about importing smooths everything out, I'm asking if there have ever been plans for fixing smoothing in imports, and if it is technically possible to fix it if you have enough time on your hands.

Well... This may or may not help you: https://developer.valvesoftware.com/wiki/Material Just remember to read more than what is in that exact article. But editing a VMT can still be a good way to make VMTs, remember that.

...The model doesn't include the textures. It never does. The textures are referenced in materials, and models reference materials. Even then, materials are still not included in the model.

Also, if this is of any help, this is the command-line thing I use to compile models for Team Fortress 2, which works after SteamPipe:

"F:\SteamLibrary\SteamApps\common\Team Fortress 2\bin\studiomdl.exe" -nop4 -r -game "F:\SteamLibrary\SteamApps\common\Team Fortress 2\tf" "[QC path and filename].qc"

The first thing is the path and filename of StudioMDL (Source FilmMaker also has a StudioMDL included, but Garry's Mod doesn't, so it depends on the game), the -game variable is, well, pointing at where I want the model to be outputted (it must have a proper gameinfo.txt), and the last thing is the QC to be compiled.

Sure, it doesn't really help with compiling in Blender nor other third-party tools, but it may still help you with compiling in general.

Początkowo opublikowane przez CDw/P~Monochrome:

What has gone wrong here -

You tried to compile a model using Blender.

Początkowo opublikowane przez CDw/P~Monochrome:

- and how may I correct it?

Don't use Blender to compile models.

Seriously, though, it's recommended to use the command-line StudioMDL itself manually, or using a third-party tool (like GUIStudioCompiler or something).

Początkowo opublikowane przez Artfunkel:

- Comparing weightmap data as well as vertex location should sort the problem out.

Well, yes, but some models actually have faces that are just the same, but with a flipped normal direction. Sure, that should only be the case for really on-purpose-lowpoly models, though, so it should be alright to just compare weight-map data. Bleh. :P

Of course. The SMD extension is used for SMD meshes, not DMX meshes.

Actually, what I meant was take 2DS Max, did I just type 2DS Max?
Take 3DS Max, import the mesh, then move one of the swords a bit in one direction (it'd be best if you could move it by something memorable, like 10 whole units or something, for example +10 in the X direction), then export it, and Blender should like it perfectly (possibly except for the smoothing). Then just select the sword in Blender, make changes if needed, and move it back in the opposite direction by the same amount (for example -10 in the X direction). Seperate the two swords into two different Blender objects if you want, too. Oh, and Blender has nothing against overlapping vertices when using the DMX format.

...Okay, let me explain what I explained earlier, again.

When importing an SMD with the Blender Source Tools, all triangles get imported on their own, then all vertices on the exact same coordinates gets welded.

I don't think there is any way to get around it without every single triangle being seperated.


Anyway, firstly, having overlapping vertices in a model on purpose is a really bad design choice, no matter what. Secondly, depending on what you want to do, can't you just take all the vertices, assign them to one of the bones, then duplicate it and assign those vertices to the other bone (while making changes if necessary)? Thirdly, you can also just use 3DS Max, even if just for seperating the blades for Blender.

Yeah. Except, you know, noone would ever turn the override on for anything other than curiousity. Could you explain to me exactly what you would want the override to do?