Compiler is erroring out on Line 7 for your QC. It can't find the DMX file

pokekidgirl_reference.dmx

Either you've removed this object from your exports or you've typed the name wrong into the QC, but the QC cannot find that dmx file to compile it.

When I comment out the $upaxis Y statement in the QC, the model imports with the Armature, Mesh and collision model load standing upright on the floor. The VTA vertices import properly, ans as expected. So I have to agree with Zeq here and say it may have something to do with the way BleST is applying the upaxis statement.

But wait, I also think that BleST is applying the first animation (default) it encounters and is posing the model.

https://i.imgur.com/M50RJEv.png

If I remove the $upaxis statement, import the model then take the armature into pose mode and clear all transforms, the model and the VTA Vertice objects snap to the proper and expected position.

GIF of both import methods and result after the Pose is cleared.

https://i.imgur.com/SgEUJBX.gif

Hate raising bug reports, especially on tools like this that have worked almost flawlessly for years, but Blender is changing and tools are breaking as the new versions are released.

This is another problem I'm having where when I import some decompiled models using the QC to import into blender using BleST default setting, the armature, mesh and collision models are importing standing on the floor upside down instead on their backs up the Y axis and the VTA Vertex object imports standing upright on the floor, again instead of in its back up the Y axis as expected.

Importing individual SMDs and VTAs work as expected.

This is a decompiled scout imported using the QC.

https://i.imgur.com/lzhVAoy.png

This problem is intermittent, some models import fine, others not. I have discussed this with Zeq and he has confirmed the problem exists but says that it is not a Crowbar issue.

Again, this is Blender 2.82.7 (Steam Version) and BleST 3.0.3 the Scout Decompile was the TF_Movies HWM Scout from SFM.

On this one, all I can offer is my thanks for your dedication to this tool Artfunkel.

That is true Zappy, however, I think maybe we need a champion with some pull with the Blender Dev team and request an update so everyone gets the added functionality.

Checking Blender, the 63 Character limit is hard coded into the Blender Shapekey name text box itself and that limit has been around forever (looking back at previous versions). I'm actually surprised that this issue hasn't been brought up long before now.

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

But I may have stumbled on something while comparing the QC to the VTA that might be the source of this dilemma and maybe a possible fix.

In the flex definitions of the qc, Flexes and Flexpairs are being defined with flex names less than 63 characters.

For example In the Scout QC the flex #30 is defined as:

flexpair "OpenJaw_OpenLowerLip_OpenUpperLip_Platysmus_SmileFull" 1 frame 30

This is a flex pair and a corrective shape but the definition is only 53 character long, dangerously long but not over the 63 character limit. I believe this is the actual name of the flex used by the model (Corrective or Real) in game.

VTAs are not loaded onto a model in Blender until we import the VTA onto the mesh. Looking at the VTA now, we find Time 30# being defined as:

OpenJaw_OpenLowerLip_OpenUpperLip_Platysmus_SmileFullL+OpenJaw_OpenLowerLip_OpenUpperLip_Platysmus_SmileFullR

This is the name that is being given to the Shapekey on import. It is 109 Characters long and is the name being truncated.

Not knowing how this all comes together on Import, export and compile I can only ask, is there some way for Cowbar (through some sort of written variable into the VTA file) or BleST (on import) to use the actual and real name vs the VTA name as the shapekey name in Blender when the VTA is imported as still have the flex work as intended?

Follow up...

I just checked Blender and found that the shapekey name textbox only accept 63 characters. No wonder why it's being truncated.

Most of the shapekeys that have over 63 characters are Corrective shapes. An example from the scout would be

OpenJaw_OpenLowerLip_OpenUpperLip_Platysmus_SmileFullL+OpenJaw_OpenLowerLip_OpenUpperLip_Platysmus_SmileFullR

This shape has the longest named and is 109 characters long. Iit's being truncated to

OpenJaw_OpenLowerLip_OpenUpperLip_Platysmus_SmileFullL+OpenJaw_

It's no wonder why the compiler can't find flexes and bailing when trying to compile DMX files.

I have no idea how this can be fixed.

A secondary cache holding real names with shapes being give pseudo variables as names??? But how could this be handled if the variable is changed or a new shape requiring over 63 characters is needed? Or how can we compare real names to pseudo names??

I really don't want to have to revert back to writing VTA data and defining Flexes in the qc... That would make DMX files redundant. LOL...

Please GrandMaster Artfunkel, Save Us with your infinite genius and your coding magic.

Artfunkel, help?

I thought I was having a problem with Crowbar at the same time I found the truncation, but the symptoms are leaning more toward BleST as well. This is a video of both problems together.

When importing whole models using QCs I'm finding that rotations are wrong. When importing as single SMDs and VTA files, rotations are correct.

But in both circumstances Shapekey names are being truncated.

https://youtu.be/Vqis0QHeivc

I've left that link in the Crowbar Debug discussion for Zeq to look at as well.

As the problem seems to be trouble with rotations, I am starting to wonder if this OTHER problem I'm having is related to BleST on export of a DMX animation file as well.

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

I can provide Blend, SMD, DMX and FBX files as well if required.

Finding that shapekey names are being truncated to 63 characters on import.

Is this a Blender limitation or is BleST doing it?

https://i.imgur.com/YX4p2Bw.png

Using Blender 2.82.7 and BleST 3.0.3

I have no idea what you mean by Sphere bones, maybe a screenshot of what these are might help.

As for the Y, Z thing, most importers and exporters give you options to set the up axis, be it Y up, Z or -Z forward or Z up, -Y forward. You just have to set the options to import the model to the Up Axis you want it to be. The rotations of a model all depend on how the original author of the model exported it and and what the up axis is for the game engine or purpose it was developed for. So, this is not a Blender thing other than the Blender default being Z Up and -Y Forward and the other popular 3D editors being Y up and Z forward.

This will always be a problem, but manageable, You just have to remember that 7 on the pad is front instead of Top View, and 1 is Top view instead of Front view.

This is a Blender function, not a Blender Source Tools one, which pointed me to that answer...

https://i.imgur.com/2IXRwN8.png You bake the f-curve via the curve screen Key functions

The animations will bake to a SMD file which, by default, Blender Source Tools exports this animation SMD to the anims folder of the export folder.

To add the animation smd to the model, you add a $sequence command to the QC calling that animation SMD ensuring that the FPS is set to the frame rate you made the animation in (if you want it to play at the same rate in SFM). Like this

$sequence "what you want the seq to be named" "anims\smdname.smd" FPS 24

You should see the animation smd in your exportables.