Subject:
|
Can someone explain the method to the madness...
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Mon, 8 Mar 2004 21:20:04 GMT
|
Viewed:
|
566 times
|
| |
|
|
Well, I don’t know if it’s madness or not, but it’s driving me mad, at any
rate.
Can some kind soul explain either or both of the following:
1) What is the conversion system for MLCAD units to POV units, when not using
LGEO?
2) Why does L3P create matrices for the placement of elements instead of using
translate?
I’m cracking my keyboard over my head trying to replace a matrix with a
translate so I can perform a clock animation on it, but I’m having absolutely
no success. Desperation drives one to ask many questions.
Thank you very, very much for any help you can render, pardon the pun,
-Mike
|
|
Message has 2 Replies:
 | | Re: Can someone explain the method to the madness...
|
| (...) One to One (...) Matrix is faster because a matrix defines rotation, translation, scaling, and skewing all in the same statement. (...) You can translate without replacing the matrix. Here's a typical POV matrix: matrix (...) (21 years ago, 8-Mar-04, to lugnet.cad)
| | | Re: Can someone explain the method to the madness...
|
| (...) The first 'matrix' specifies the *size* of the brick (depending on the Seam Width setting). The second one defines the rotation and translation of the brick. The first nine numbers are the rotation matrix, and the last three are the (...) (21 years ago, 8-Mar-04, to lugnet.cad)
|
6 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
