STEAM GROUP
Blender Source Tools BleST
Join Group
STEAM GROUP
Blender Source Tools BleST
6,738
MEMBERS
312
IN-GAME
2,010
ONLINE
Founded
8 November, 2013
Overview Announcements Discussions Events Members Comments
By: SD
Showing 1-3 of 3 entries
In forum "Blender Source Tools Help"
10
Possible to disable corrective shape key checks for Source 2 exports?
Originally posted by Rabbitfox:
For stereo flexes, can't you just set the "stereo" "bool" in the DMX file to "1" instead of "0" for the flexes in question? Works for me in Source 2 and I don't need the left/right prefix then. Also where did you get the information that corrective flexes are defined with "__"? I tried that out and Source 2 doesn't recognize that as a corrective flex, it just makes a separate controller with the two underscores in it.
The stereo bool still works fine. The issue is that modeldoc for some reason doesn't correctly use the Stereo flex balance causing the left flexes having parts of the right flexes move and vice versa. This also breaks how wrinkle maps behave as they appear on opposite wrong sides.

A video demonstrating this: https://streamable.com/h4f3pw
Corrective shapes as defined in modeldoc is "Morph combination shape". The description states: https://imgur.com/a/CNqbINE

You can see a majority of what im talking about if you open an HLA character in modeldoc
Originally posted by Zappy:
For Source 1, there's a difference between a "flex" (shape key) and a "flex controller" (the slider/input in Source Filmmaker/Garry's Mod/other games).
You can then use "advanced" DMX flexes to give a "flex controller" (the "name" in the flex definitions) a different name than its "flex" (the "rawControlNames").

With this, you can name a shape key as "Left-Example" and "Right-Example", then do something like this in the flex definitions...
"DmeCombinationInputControl" { "id" "elementid" "ee4bf229-d43a-3a8c-bdd2-5804d0dd1263" "name" "string" "right_Example" "rawControlNames" "string_array" ["Right-Example"] "stereo" "bool" "0" "eyelid" "bool" "0" "flexMax" "float" "1.0" "flexMin" "float" "0.0" "wrinkleScales" "float_array" ["0"] }, "DmeCombinationInputControl" { "id" "elementid" "1322da48-cd70-3e12-8f28-a1e4476b13ad" "name" "string" "left_Example" "rawControlNames" "string_array" ["Left-Example"] "stereo" "bool" "0" "eyelid" "bool" "0" "flexMax" "float" "1.0" "flexMin" "float" "0.0" "wrinkleScales" "float_array" ["0"] },
...and then Source Filmmaker will treat it as a single stereo flex.


I'm not proposing this as a "fix", just a "workaround", and I don't know if it works this way in Source 2.
Doesn't work like this unfortunately. I tried it, Modeldoc will instead create a duplicate flex controller with underscores while the controller defined in the dmx text file has no function/ slider doesn't work
https://imgur.com/a/pB7r8Ef
In order to author stereo flexes in modeldoc. Shape keys must be exported with Left_ and Right_ prefixes. The current version of BST will always define shape key names with "_" as a corrective shape while in Source 2 corrective shapes are defined with "__". Would it be possible to disable this check or update it specifically for Source 2?

I've recently figured out that Source 2 can still accept wrinklescales for individual shapekeys rather than relying on ComputeWrinklescales, but this becomes problematic when the flex controllers only accept default shape key names with no underscores.
Showing 1-3 of 3 entries

Discussions Rules and Guidelines