Jump to content

  • Log In with Google      Sign In   
  • Create Account


#Actualkeym

Posted 04 February 2013 - 11:27 AM

I use float4 and int4 but I also pass 3d vector - weight position - that is part of MD5 format (maybe there is a workaround for this?). That's why it's so crowdy in there... Bones itself are 3d vectors (pos) + 4d vectors (orient).

So just to clarify - there's no way to pass more attributes other than pack them through ATTR0-ATTR15? I'm asking cause MJP's post:

"You should be able to pack as many bones + weights as you want in your vertex."


gave me the impression that I can pass more data and I just don't know the trick.

#2keym

Posted 04 February 2013 - 11:27 AM

I use float4 and int4 but I also pass 3d vector - weight position - that is part of MD5 format (maybe there is a workaround for this?). That's why it's so crowdy in there... Bones itself are 3d vectors (pos) + 4d vectors (orient).

So just to clarify - there's no way to pass more attributes other than pack them through ATTR0-ATTR15? I'm asking cause MJP's post:

"You should be able to pack as many bones + weights as you want in your vertex."


gave me the impression that I can pass more data and I just don't know the trick.

#1keym

Posted 04 February 2013 - 11:26 AM

I use float4 and int4 but I also pass 3d vector - weight position - that is part of MD5 format (maybe there is a workaround for this?). That's why it's so crowdy in there... Bones itself are 3d vectors (pos) + 4d vectors (orient).

 

So just to clarify - there's no way to pass more attributes other than pack them through ATTR-ATTR15? I'm asking cause MJP's post:

 

"You should be able to pack as many bones + weights as you want in your vertex."

 

gave me the impression that I can pass more data and I just don't know the trick.


PARTNERS