Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
"To access Scaling for an object, right click the model or bone in the Animation Set Editor, and select Utilities -> Add Scale Control for Models. Once you have done so, a new controller will appear for that object within its slider controls: rootTransfrom - Slider. Sliding left will make the object smaller, right is larger."
https://steamcommunity.com/sharedfiles/filedetails/?id=1826909237
Instead, select the model's other root bone (the pelvis bone for characters, weapon_bone for weapons, static_prop for props, et cetera), right-click it, and choose "Add Scale Control To Transforms".
You should then get a slider beside that in the Animation Set Editor, with the same name as the bone followed by "_scale".
This slider also scales all bones connected to that bone (whether by default or through locks), so if you scale a character's pelvis bone, it will usually scale the entire character, not just the pelvis.
Seems like a worthwhile workaround alternative that is just as easy to do and if it means avoiding potential problems with the model disappearing, that sounds like an added bonus. Alright, will keep this in mind for the future. Cheers. Hopefully OP see's that.
Zappy makes a good point, I'd mark them as the answer instead.
Maybe it's something that used to be an issue in an earlier version of Source Filmmaker, but the latest version is from the 12th of January, 2015, and I'm certain that I've had that issue since then too.