• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

Is it ok to delete bones that only have skin weights?

Is it ok to delete bones that aren't a parent and aren't in any vertex groups or matrix groups (i.e. nothing is attached to it), but that do have skin weights? Or would that cause problems?

If it's not obvious i don't really know what a skin weight is or what it does xD

Edit: it seems like skin weights kinda sorta replace vertex/matrix groups? So probably not a good idea to discard them
 
Last edited:
im not sure but i think the situation is like this:
skin weight replace matrix group from model version 800. Matrix groups served as a container that multiple vertices use to know which bone they are attached to. This is memory-efficient and size-efficient. Now the skin weights that replaced them are equal inside hte file to the number of vertices which is not filisize efficient.
Each skin weight has 8 values - 4 for the bones and 4 for the weight they have. Because one vertex is allowed to be attached max to 4 bones.
If a vertex is attached to just one then the others are .. 0 ? And the weight is represented as a byte for percentage.
How the line goes: { 1, 0, 0, 0, 255, 0, 0, 0}
 
Last edited:
im not sure but i think the situation is like this:
skin weight replace matrix group from model version 800. Matrix groups served as a container that multiple vertices use to know which bone they are attached to. This is memory-efficient and size-efficient. Now the skin weights that replaced them are equal inside hte file to the number of vertices which is not filisize efficient.
Each skin weight has 8 values - 4 for the bones and 4 for the weight they have. Because one vertex is allowed to be attached max to 4 bones.
If a vertex is attached to just one then the others are .. 0 ? And the weight is represented as a byte for percentage.
How the line goes: { 1, 0, 0, 0, 255, 0, 0, 0}
Sounds about right. Probably best not to touch it xD
 
Back
Top