|
| 29 Nov 2014 08:34 AM |
when you use while true do brick.position = brick.position + vector3new(1,1,1,) end
it doesnt go very fast if you want it to move smoothly. what is the substitute? |
|
|
| Report Abuse |
|
|
llcoolj03
|
  |
| Joined: 20 Nov 2011 |
| Total Posts: 6135 |
|
|
| 29 Nov 2014 08:37 AM |
while true do brick.CFrame = brick.CFrame + CFrame.new(1,1,1) wait() end
9+10 is not 21, IT IS 20! |
|
|
| Report Abuse |
|
|
|
| 29 Nov 2014 08:48 AM |
| You can't add CFrames, llcoolj. |
|
|
| Report Abuse |
|
|
|
| 29 Nov 2014 09:52 AM |
| so it isn't possible?????? |
|
|
| Report Abuse |
|
|
| |
|
|
| 29 Nov 2014 10:07 AM |
| why would i use a for loop? |
|
|
| Report Abuse |
|
|
|
| 29 Nov 2014 10:09 AM |
If you want it to just fly off into oblivion then go right ahead with a while loop
But if you want it to stop, use a for loop.
Oh and grammar matters in Lua
thing.Position* Vector3.new()* |
|
|
| Report Abuse |
|
|
|
| 29 Nov 2014 10:16 AM |
| To make the brick stop, it deletes itself after 3 seconds. That isn't relative anyway. So is it actually possible to move an anchored brick without it looking glitchy?(i.e. without moving position) |
|
|
| Report Abuse |
|
|
|
| 29 Nov 2014 10:17 AM |
Yeah. Set the CFrame or Position. Just interpolate it. |
|
|
| Report Abuse |
|
|
|
| 29 Nov 2014 10:22 AM |
@above when i use position it moves very glitchy; i want it to move smooth. |
|
|
| Report Abuse |
|
|
fret13103
|
  |
| Joined: 15 Mar 2010 |
| Total Posts: 881 |
|
|
| 29 Nov 2014 11:08 AM |
Oh my god, please,rub 2 braincells together, just make it move smaller amounts, faster.
While true do THISPART.CFrame = CFrame.new(THISPART.CFrame.X+.1,THISPART.CFrame.Y+.1,THISPART.CFrame.Z+.1) wait(.1)
make the wait time to .01 if you want it to move faster, and make sure line 2 and 3 are together in the script, roblox forum broke them apart.
|
|
|
| Report Abuse |
|
|
|
| 30 Nov 2014 06:27 AM |
@above if you want to insult people dont make yourself look stupid in the same post. I've already posted reasons why that script wouldn't work.
|
|
|
| Report Abuse |
|
|
Goulstem
|
  |
| Joined: 04 Jul 2012 |
| Total Posts: 7177 |
|
|
| 30 Nov 2014 06:32 AM |
@above, you didn't actually fix his prolem he asked to be fixed though.
|
|
|
| Report Abuse |
|
|
| |
|
ChuckXZ
|
  |
| Joined: 26 Jan 2012 |
| Total Posts: 2996 |
|
|
| 30 Nov 2014 09:39 AM |
you could also do
while wait() do game.Workspace.Part.Position = game.Workspace.Part.Position + Vector3.new(0, .1, 0) end
Chucky Incorporated |
|
|
| Report Abuse |
|
|
|
| 30 Nov 2014 09:46 AM |
| Yes, that doesn't go fast enough without being glitchy. My solution is to use a script that finds all blocks within a position that's equal to touching it, so i don't require canCollide to detect collision. |
|
|
| Report Abuse |
|
|
ChuckXZ
|
  |
| Joined: 26 Jan 2012 |
| Total Posts: 2996 |
|
|
| 30 Nov 2014 09:47 AM |
you forgot a dot between 3 and n
Chucky Incorporated |
|
|
| Report Abuse |
|
|
ChuckXZ
|
  |
| Joined: 26 Jan 2012 |
| Total Posts: 2996 |
|
| |
|
Goulstem
|
  |
| Joined: 04 Jul 2012 |
| Total Posts: 7177 |
|
|
| 30 Nov 2014 07:43 PM |
Oh my god.
srsly
local orig = something.CFrame
for i = start,end,increment do something.CFrame = orig + Vector3.new(0,0,i) wait(interval) end |
|
|
| Report Abuse |
|
|