Im not quite sure what happened, as far as i can tell there is a corrupt input in the objects history and when you then parented the rock to something it effected the UVs, doing this -

Solution 1 = Delete the history - Fail.
More unknowns but if you delete the history of the rocks it does this to the rig.

Working solution:
Open the scene.
1. First thing you've got to do is delete the existing rocks from the scene.
2. Alongside the textures that i'm about to put onto Adrive is a file called MachoRocks.mb, import this into the scene.
3. Go to frame 32 - you should see the rocks line up with this geometry on this frame
4. Still on frame 32 parent the new rocks to the respective wrist_control joint

Lemme know if theres any issues.
Edit- Right the rock textures and MachoRock.mb are on the adrive in the textures folder
if your in tomorrow - I'll have 10 mins with your file alone :p
ReplyDelete