You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The best practice i've discovered is to compute the transformation matrix outside and pass it
to the hexagon. This is because usually we use the same transformation matrix not only to the hexagon but other things like legs or coordinate frames (axes). So we'll just compute the transformation matrix only once for all the objects that need it. This is why we don't need these kinds of abstractions anymore.
mithi
changed the title
Remove cloneRotXYZ and replace accompanying tests since this won't be used anymore
Remove cloneRotXYZ and replace accompanying tests with cloneTrot since this won't be used anymore
Jun 7, 2020
The best practice i've discovered is to compute the transformation matrix outside and pass it
to the hexagon. This is because usually we use the same transformation matrix not only to the hexagon but other things like legs or coordinate frames (axes). So we'll just compute the transformation matrix only once for all the objects that need it. This is why we don't need these kinds of abstractions anymore.
hexapod/src/hexapod/Hexagon.js
Line 104 in 8fa9cbc
The text was updated successfully, but these errors were encountered: