After recomposing reassign the matrix to the object . It must work .also when you decompose the right way is to specify the type of it like Quaternion or Euler or Matrix . What I did found that was really strange to me is this: Let's say matrix1.rawData[0]=1 or any other number matrix2.rawData[0]=0.3 or any other number Now if I try : matrix1.rawData[0]=matrix2.rawData[0]
The first matrix value remains the same . Very interesting ... Had to use cloning or referencing the whole matrix in order to solve this Sent from my iPhone On Dec 2, 2010, at 5:29 PM, John Brookes <[email protected]> wrote: > Away3.6 > Just as an example say you have a cube c and add the following in the enter > frame > > trace(c.transform.rawData); > matrixComponents = c.transform.decompose() > matrixComponents[0].x += 1; > Matrix3D(c.transform).recompose(matrixComponents) > > The above should move just the same as c.x +=1 > but it doesnt move even though the matrix is changing > > A hack is to do > c.y+=0.1 > c.y-=0.1 > > Then the cube moves. > > Better way?
