|
| 17 Nov 2014 03:40 PM |
| What is the difference between Position and CFrame? |
|
|
| Report Abuse |
|
|
|
| 17 Nov 2014 03:44 PM |
Let's say you put the position as (0,5,0). But wait! there's a part there. It will go over that part, then. CFrame will go through anything no matter what, and CFrame allows rotating too, while ordinary rotating will act like position. |
|
|
| Report Abuse |
|
|
|
| 17 Nov 2014 03:44 PM |
CFrame is a matrix, Position is a vector.
CFrame contains a position vector, mind. |
|
|
| Report Abuse |
|
|
maxomega3
|
  |
| Joined: 11 Jun 2010 |
| Total Posts: 10668 |
|
|
| 17 Nov 2014 04:03 PM |
Let's talk laymans terms.
Vector3 is wimpy, it's used in sizing and MoveTo (), but if it's used for positioning, then it'll check to see if something is already occupying its assigned space. If so, then it will go just above it.
CFrame is ignorant. It doesn't give a flying noob if something is already there. It will occupy that space anyway. That's why you can have bricks that merge into each other. CFraming is also used in Camera Manipulation |
|
|
| Report Abuse |
|
|
|
| 17 Nov 2014 04:37 PM |
Actually, that is just what they CAN be used for.
CFrames are actually far superior, even without that. Their main purpose is not to put parts inside of each other. It gives us much more advanced and easier to use methods for determining position and such. |
|
|
| Report Abuse |
|
|
anaIyze
|
  |
| Joined: 29 May 2014 |
| Total Posts: 2048 |
|
| |
|
|
| 17 Nov 2014 05:23 PM |
| Im so happy for analyze, now most of the forums that he trolls is all in one place! Yaass! |
|
|
| Report Abuse |
|
|
anaIyze
|
  |
| Joined: 29 May 2014 |
| Total Posts: 2048 |
|
|
| 17 Nov 2014 05:27 PM |
| @Above is kewl axaxaxa ;dd |
|
|
| Report Abuse |
|
|
|
| 17 Nov 2014 07:29 PM |
| @Jarod: A Vector is just as useful as a Matrix. |
|
|
| Report Abuse |
|
|