Culling the weight killed some of the influences that bones over the count of 3 had on those vertexes. (Blender is really bad at controlling this imo). On compile the model now only has 3 (max) bones influencing them.

The best thing to do is decompile your SFM model and load it into Blender (make sure weight limits are set to 3). Take the model into edit mode and select one of the vertexes that are really bugged out. Press N to open the transform window, select Item, and at the bottom of the values you should see the Vertex groups/bones that are influencing that vertex. Then decide what you have to do in order to fix the weight painting (change the influences of the bones, add or delete bone influences (to a max of 3 bones), etc).

I just checked and BleST 3.0.3 still works with Blender 2.83.

There is a newer beta version of BleST available (3.1.0) on Artfunkel's GitHUB page, but he is still developing it for release, so if you decide to go that route, expect things not to be perfect.

If you are using Blender versions earlier than 2.8x (ie still using 2.79) then you'l have to go into the BleST archives and find the version of BleST that best matches the version of Blender you're using. Those archives can be found here.
http://steamreview.org/BlenderSourceTools/archives/

For Blender 2.79, the version you should be using is BleST 2.10.2.

BleST 3.x.x versions are strictly for use with the Blender 2.8x versions.

Magic, I just updated my Blender Version to 2.83 and I'm just now starting to check add-ons. Give us a bit to find out what is working and what is not. Current stable BleST for 2.8x is 3.0.3 and I'm not sure if it still works or not.

Yeah, I can see your point now that Valve is moving Source2 towards VR. But still, I think it would be better control on the modeler's side instead of looking for a variable in a add-on. We'll have to wait and see what Artfunkel has to say about it.

I have just started to play with Source2 models, so I am still not familiar with how they are truely constructed or what is required for bone rotations or connections.

Are you sure ALL bones are X-F, Z-U and Y-L/R? What type of model? Prop, Character, Bipedal or quadripedal, maybe vehicle? How are finger rolls maintained so they don't rotate weirdly? Most require some sort of roll so they rotate cleanly into a fist.

And, I'm not following this scale option request. Why do you scale by 39 for export then have to scale it back? Scale what back to what?

Why not just scale by 39 before working model and work it at game scale?

Personally, I work a model at import or creation scale. Once finished, I import a character from the universe I want to use the model in and scale it to its proper size. Then I apply transforms and then export. As I said, easy-peasey. If I have to do more work, the model is at game scale, so it's just a simple export after that.

You use the metric system, but I use standard blender units when modeling, so should Artfunkel make allowances for me as well? And what about the people that use Imperial units?

What if I want to port an XPS or a MMD character model, or some random OBJ or STL as a prop into Source2. These all have different scales when imported to Blender. How would a simple option to rescale know what value to use to scale a model for use in game?

It's not really a simple change to code to add this kind of feature. There are a lot of parameters that have to be considered.

Sure, for you it's a repeatable thing, I understand that, but something like this should be a local script based on the way you work and your system is set up. It should be run just before exporting.

In my opinion, this is all part of the modeling process and modelers have to do this kind of thing manually as all model are unique.

Disconnect bones, scale the model and apply transforms before exporting. Easy-peasey. Welcome to modeling101.

There is no way that a programmer can say, this model is this big and needs to be that big for any game. That's a modeler's job. Same goes for bone rotations. An add-on programmer can't say this bone needs to be disconnected and this one connected or this one needs to be pointed in this direction where that one needs to be pointed in that direction and precise roll of xx degrees. This is all stuff you as the modeler have to apply to the model as you build it.

Take a screen shot of the BleST panel and how you have it set up, like this

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

and

Are you using relative paths?

What are you using to compile, how are you sending the qc to Studiomdl? Blender Source Tools, Crowbar, drag and drop? The g_path looks wrong

add a \ to the end of the $cd statement like this
CD "D:\Models\honkai\Assets\jizo-mitama\Source-engine\DMX\"

or

Remove the $cd statement from the qc and put the qc in the same folder as the DMX you're trying to compile and run it from there.

That DMX file is not in the folder path Studiomdl thinks it is StudioMDL thinks the path is

"D:\Models\honkai\Assets\jizo-mitama\Source-engine\".

Doh, that might be it too. LOL

I forgot to close the $body statement with a "

$CD "D:\Models\honkai\Assets\jizo-mitama\Source-engine\DMX"

$modelname "Aevee\weapons\Jizo Mitama\Jizo Mitama.mdl"

$body "body" "jizo Mitamo.dmx"

$mostlyopaque

$cdmaterials "models\Aevee\weapons\Jizo Mitama\"

$sequence "idle" "Jizo Mitama.dmx" (
fps 1
)

Try that...