Devostated. a écrit :

Hello, I'm super interested in exporting animated models from SFM to Blender, but the positioning is always at 0 instead of walking around as it was animated in SFM. -

In Source Filmmaker, every model is given an extra "root bone" called "rootTransform". The Blender equivalent would be the armature object's position.

If you want to make a "quick and dirty" workaround, you could either...
- In Blender, add a new bone at 0,0,0 called "rootTransform" and parent the pelvis/other root bone to it before importing the animation, or...
- In Source Filmmaker, lock the pelvis/other root bone, use the procedural "Playhead" preset on the "rootTransform" bone to "transfer" its animation to the pelvis/other root bone (because that it's locked and won't be affected by the "rootTransform"'s motion being deleted), then unlock the pelvis/other root bone before exporting the animation.

EmperorFaiz.docx a écrit :

- I'm using the latest Blender (3.5.1) -

The latest version of Blender is currently v3.6.5. (Technically, even v3.3.12 is "later" than v3.5.1...)

I snort worms on a daily basis a écrit :

- it has only the visible/assigned materials, anything else "unused" jsut gets wiped for some reason -

That's normal. If a material isn't assigned to any face, then the material either "cannot exist" or "wouldn't do anything" in an exported DMX, and it "cannot exist" in an exported SMD as well.

If you're trying to use the "unused" materials as additional skins, you should just add them to a $TextureGroup block in the QC file. If you're trying to use them on separate body groups, then you only have to add/assign them on those body groups.

pablo a écrit :

- I need the shape keys to be in the .smd so I can upload it to the Workshop. -

That's not possible - but DMX meshes can have flexes built in, so you can try exporting a DMX instead.

Artfunkel a écrit :

- I've always felt that trying to support both at the same time would be too confusing for users who don't understand the internal details of these formats. -

Plus, Source Filmmaker's exported animations use flex controller names, which might not match up with shape key names - stereo flexes are a single shape key in Blender but multiple flex controllers in Source, a flex controller can drive multiple flexes (and a flex can be driven by math involving multiple flex controllers), and a flex controller can be named something completely different from its shape key(s). This makes it hard to support Source Filmmaker's flex animation exports anyway.

✞ Medic°Strange ✞ a écrit :

Hello Zappy. If you have time, please help me by telling me exactly what to do with this. I made him a new inner mouth. And this is the result... - [Images]

I don't know how to fix or avoid that, sorry.

✞ Medic°Strange ✞ a écrit :

- I want to ask if it is possible to add an inner mouth to his mouth using Blender program. -

Yes, that's possible. For this, you should look up general Blender modelling tutorials and get used to making/editing models.

✞ Medic°Strange ✞ a écrit :

- his eyes returned to normal, but for some reason the eye pupils stopped moving. - [Video] -

In the QC file, make sure that the eyeball co-ordinates are at the centre of the eyes, not the front of the eyes.

If the model doesn't have full spheres for the eyes, you can add a sphere in Blender with the size that the model's eyeballs would have been, move the sphere so that the middle of the front of it intersects with the middle of the front of the model's eyes, use the centre coordinates of that sphere, and delete the sphere.

Imagine that the eye in Source Filmmaker rotates around the coordinates that you use, like if they're coordinates for actual bones that move/rotate the eye mesh. If the "bone" is positioned at the front of the eye, rotating the "bone" won't work. It has to rotate around the (sometimes-"imaginary") centre of the eye-ball.


(After getting good coordinates/settings for one eye, you can usually re-use the same settings for the other eye, except just mirroring/inverting the X coordinate (like your QC already does) and the "cross-eyed"-ness value (which it seems that your QC doesn't do). Similarly, you should re-use the coordinates for the $Attachment lines, with X set to 0 for the "Eyes" $Attachment (like your QC already does).)



TL;DR: In the QC file, your eye coordinates need to be moved farther backwards into the head by increasing the Y coordinate.

✞ Medic°Strange ✞ a écrit :

- Hopefully if I tweak his .vmt configuration code a bit more it will fix this bug. -

You still haven't said what the bug is. Is it that the pupil is too big compared to the iris? If so, try setting $Dilation to 0.5. Is it that the iris/pupil texture seems to move depending on the camera angle? If so, try setting $RayTraceSphere and $SphereTexKillCombo to 0, and potentially adjusting $EyeballRadius. If none of the above, again, what is the issue?

✞ Medic°Strange ✞ a écrit :

- But sadly his eyes could not be fixed. - [Videos] -

If the problem is the "smudgy" effect when moving the camera around, set $ParallaxStrength to 0 in the VMT. If not, what is the problem?