anna lesbo sex lähetti viestin:

So how can I find the problem vertex? -

Besides manual checking, I don't know. But there may be a weight-map tool that will automatically "normalize" (make the weight sum 1.0) all vertexes. If there is, it will probably contain "normalize" in the name, and you can then try using it or such (while in "Weight Paint" mode).

anna lesbo sex lähetti viestin:

I'm exporting as .DMX though, so that's not much help. -

Then I think the blender_implicit bone automatically gets exported if, but only if, there's any vertex of the mesh where the total weights, when added together, does not add up to 1.0 or more.

For example, if you have a vertex that's weighted 0.2 to a "bip_hand_L" bone and 0.7 to a "bip_lowerArm_L bone", it will automatically weight the remaining 0.1 to an automatic "blender_implicit" bone to get a total weight of 1.0.

You may have vertexes that have weights adding up to 0.99999 or so, so it looks very close to 1.0, but there will still be 0.00001 remaining up to 1.0.

anna lesbo sex lähetti viestin:

I have absolutely no idea how to enable or disable this "implicit motionless bone" option. I can't find it anywhere, and I have the latest release of Blender Source Tools.

See https://imgur.com/Y7Pc7J3 for a visual clarification of it. (Though you should make sure it's not enabled, unlike in the screenshot.)

That bone is there in SMD exports if "Source Engine Exportables" > "Armature Properties ([Armature name])" > "Implicit motionless bone" is enabled... but unless you've added an $Attachment or $DefineBone for that bone, it shouldn't be there once StudioMDL removes all unused bones, unless you have vertices on the mesh whose total weight link sum for other bones doesn't add up to 1.0 (as any remainder up to 1.0 beyond the other bones' sums gets added to the blender_implicit bone).

Bean lähetti viestin:

- Granted the outline basically disappears at a certain point but that's expected. -

Yes, and if Garry's Mod is (incorrectly) using a low enough mipmap for the outline to disappear on some sides...
In other words, I think the issue here is that the outline basically disappears on two of the sides past a certain mipmap.

You might want to either model the edge to use a different material, with the outline material being black and the fill material being white, or model the outline to use a different UV part of the texture than the fill, with the outline part being fully black and the fill part being fully white (like the outline using the right half of the texture and the fill using the left half).

If you open the texture VTF in VTFEdit or such, does the texture have the black outline on all sides? And what about on the various mipmaps of the texture (if the texture has them)?

Pte Jack lähetti viestin:

- I said the Influences Over condition should abort and not produce SMDs, -

Exactly. (And by that, I mean "yes, exactly, that's what you said", not "yes, exactly, that's how it should be".)

Pte Jack lähetti viestin:

Where? If you try to compile a DMX or a SMD where there are influences over 3, StudioMDL will belch and the model won't compile. I don't see your logic in that statement. -

By "even outside of Source 2-related things", I put the "even" there to imply that I didn't mean in Source 1-related things. Granted, that may not have been very obvious, but still...

SMD and DMX aren't limited to StudioMDL. That they can be imported into other modelling tools (for example Blender) means that they can also be useful for other purposes. Purposefully restricting such freedom makes no sense at all. The best comparison I can make would probably be like making a video editor, but only allowing things in it to last for multiples of 0.01 seconds rather than an arbitrary amount (e.g. 0.0166666... seconds, or a 60th of a second).

Pte Jack lähetti viestin:

- What I would like to see is a influence culling slider in BleST for SMD exports. That would be my only request on this matter. -

Why? StudioMDL itself culls SMD meshes (yes, even though it doesn't cull DMX meshes).

Pte Jack lähetti viestin:

Zappy lähetti viestin:

For most of this thread, I've fought for the argument that the Blender Source Tools should import (and also export) SMDs even if they're not going to be compatible with Source as long as the SMD format itself is valid, and the very same definitely goes for DMX in my opinion.

I thought I just proved that it does.

Yes, you proved/explained that it does import/export SMDs that the Source engine doesn't support, and then you immediately went on about saying "it should not be possible to export DMXes that the Source engine doesn't support", to which I replied that there's no reason to prevent people from exporting completely valid DMX files just because the Source engine doesn't support them.

Pte Jack lähetti viestin:

- The "Influence Over" warning should actually be an error and BleST should punch out without exporting. -

Absolutely not. Even outside of Source 2-related things, there are several cases where having a DMX file with more than 3 bone influences for a vertex is useful (e.g. for exporting... well, a DMX file with more than 3 bone influences per vertex).

For most of this thread, I've fought for the argument that the Blender Source Tools should import (and also export) SMDs even if they're not going to be compatible with Source as long as the SMD format itself is valid, and the very same definitely goes for DMX in my opinion.

Y E L L O W_ lähetti viestin:

- i still get blur between pixel, and i really have no idea why, -

If you don't know why, refer to comment #1 of this thread. The one where Artfunkel explains that texture filtering is an entirely intentional feature.

If you want to disable it for a Source engine VTF texture, enable the "Point Sample" flag of the VTF texture file using VTFEdit or such.
If you want to disable it for Blender's viewports, click "File" > "User Preferences..." at the top-left of Blender, switch to the "System" tab, and disable the "Mipmaps" box near the top in the middle column. (I think that doing this will also disable texture filtering.)