|
| 18 Nov 2012 11:17 PM |
| Is having a brick with a BodyVelocity moving it more efficient then having a script change it's CFrame in a for loop? |
|
|
| Report Abuse |
|
|
miz656
|
  |
| Joined: 19 Jul 2010 |
| Total Posts: 15336 |
|
| |
|
|
| 18 Nov 2012 11:33 PM |
| Which causes less lag, if any? |
|
|
| Report Abuse |
|
|
miz656
|
  |
| Joined: 19 Jul 2010 |
| Total Posts: 15336 |
|
|
| 18 Nov 2012 11:38 PM |
| You really shouldn't worry about lag since this is such a simple task. |
|
|
| Report Abuse |
|
|
|
| 18 Nov 2012 11:41 PM |
| Not really because I have a huge wave that passes over a large map destroying whats in it's way. And I need to know if CFraming it in a for loop to move it is less laggy. |
|
|
| Report Abuse |
|
|
miz656
|
  |
| Joined: 19 Jul 2010 |
| Total Posts: 15336 |
|
|
| 18 Nov 2012 11:43 PM |
Like I said that's still a simple task because Roblox already made a physics engine that has a property called Anchored. So just set the parts properties to false.
Still going with velocity. |
|
|
| Report Abuse |
|
|
|
| 19 Nov 2012 01:38 AM |
| I'd personally go with CFrame, Velocity can glitch alot. |
|
|
| Report Abuse |
|
|
Wowgnomes
|
  |
| Joined: 27 Sep 2009 |
| Total Posts: 26255 |
|
|
| 19 Nov 2012 01:41 AM |
| Generally velocity is less lag. |
|
|
| Report Abuse |
|
|