Автор сообщения: ✞ Medic°Strange ✞

- On SFM Team Fortress 2 characters' eyes move without any problems. - my model's eye can only move both at the same time in Blender. On SFM, it doesn't exist. - [Link]

You have to give the left and right eyes separate materials using the EyeRefract or Eyes shaders (with centred iris/pupil textures), and set up the eyes in the model's QC file using Eyeball with centre coordinates of each eyeball, flex controllers named "eyes_updown" and "eyes_rightleft", and an $Attachment called "eyes". This way, you can use Source's dynamic eye UV projection system, like Team Fortress 2 models.
Try to find a guide about eyes in Source Filmmaker, Garry's Mod, or the Source Engine in general.

Автор сообщения: ✞ Medic°Strange ✞

- $Body "silco" "silco.dmx"
}
$Body "silco" "silco.dmx"
}
$Body "silco" "silco.dmx"
} -

Delete these six lines, and add this single line:

Автор сообщения: ✞ Medic°Strange ✞

- The code of its main material has been sent to you. -

Try deleting the $SurfaceProp, $NormalMapAlphaEnvMapMask, $HalfLambert, and $DiffuseExp lines from the VMT.
Also, add two forward slashes in front of the $LightWarpTexture line (to disable it temporarily), like...

Автор сообщения: ✞ Medic°Strange ✞

- $BodyGroup "silco"
{
studio "silco.dmx"
}
$BodyGroup "silco"
{
studio "silco.dmx"
}
$BodyGroup "silco"
{
studio "silco.dmx"
} -

You're loading "silco.dmx" three times, which is bad for flexes.
(Also, if you don't want more than one body group option, $BodyGroup does the same as $Body.)

You should replace these $BodyGroup functions with just...Afterwards, compile the model again, reboot Source Filmmaker, and test the model in a new session.

Автор сообщения: ✞ Medic°Strange ✞

I have made the problems more clear so that you may understand better. - [Images]

Please open one of the material VMT files, copy all text, and paste it in a comment here.

Автор сообщения: ✞ Medic°Strange ✞

- the Shape key will still not work - How to make these Shape keys work normally on SFM? -

Please open the model's QC file, copy all text, and paste it in a comment here.

Автор сообщения: ✞ Medic°Strange ✞

WARNING: 1337 verts on "Silco_mesh" have over 3 weight links. Source does not support this! ~ This error appears when converting with the .dmx extension. >.< But it worked without any errors when converting to .smd. -

If SMD meshes have a vertex that's assigned to more than 3 bones, StudioMDL (the model compiler) can automatically remove anything beyond the third link.
If DMX meshes have a vertex that's assigned to more than 3 bones, StudioMDL will show an error and abort compiling the model.

Therefore, the Blender Source Tools plug-in shows a warning when exporting a DMX with more than 3 bone links per vertex, while it doesn't with SMD.

The Blender Source Tools has a "weight link cull threshold" option near the export button. Slide this all the way to 1.0, then the Blender Source Tools plug-in will automatically remove anything beyond the third bone link when exporting the DMX, allowing you to compile the model (at the cost of the DMX not having all bone links... but since the compiled model wouldn't have that even with SMD, that's not an issue).

Автор сообщения: java.lang.SkillException

- I have a feeling the problem has something to do with the reference mesh being concave, -

That's correct. StudioMDL's triangulation can sometimes mess up with concave polygons, so you should cut the concave polygon into multiple convex polygons instead.

For example, picture that your polygon's edge is a road, and place an imaginary car on it.
Can the car complete an entire lap around the polygon while only turning clockwise (or only counter-clockwise)? If so, it's convex, which is good.
But if it has to turn the other way at some point, the polygon is concave, and you have to split it (at the point where the car turns the second way) to try making multiple convex polygons instead.

In other words, the outside edge must always curve "inward", never "outward". If it curves "outward", you have to cut it where it starts curving out (even if this is for every vertex along a curve).


TL;DR: In this example image (with a cherry pin instead of a door), you'd have to cut at the blue lines in https://imgur.com/LBcHTXE ...or alternatively just use Blender's "Triangulate Faces" option to turn the polygon entirely into triangles.

Автор сообщения: Artfunkel

- I am telling you for the third time that you cannot do it.

You can't have multiple bone parents in SMD/DMX files, but can't you use math to figure out what position relative to one parent bone would be the same as the original position relative to two parents edit: relative to the constraints (automatically baking the animation to just one parent bone)?

(This might look slightly off when interpolating between frames, due to the different parenting, but every written frame should look correct.)

Автор сообщения: EL MAPACHE

- Since I want to use my animations in GMod the MDL files have to be bellow a certain file size. -

Can you compile different animations (or groups of animations) as separate MDL files, and have the "main" animation MDL use $IncludeModel to load the other MDLs?

(This is not a "solution", only a workaround.)

Автор сообщения: Satanism's Nanochips

Ok, by wrong size i mean that even in blender the size is big, - its the same huge size in both Blender and Unity, -

In that case, don't worry, that's normal. That's just due to the Source engine often having big units for models (and maps and such).

Автор сообщения: Satanism's Nanochips

Simple but i need to ask, is there a reason why the models are huge when importing ? -

Source models are just huge.
The default 1x1x1 cube in Blender might look the same size as a 64x64x64 block in the Source engine (due to Blender's camera being very close to the cube by default), but it's only a 64th as big on all axes.
A player model can easily be 70-80 units tall in the Source engine, whereas you might only make it 1.8 units tall in Blender if you'd treat units as metres.

Автор сообщения: Satanism's Nanochips

- it keeps it wrong size when exporting to FBX -

What does "wrong" size mean, exactly? And what are you trying to export it for (the Source engine, another game engine, ...?)?