of     1   

dosinuyasha
#8235868Tuesday, May 05, 2009 8:41 AM GMT

Asking if anyone has made a remodel of move to of their own. 'Cause I just noticed it was removed and its removal is ruining one of my many place ideas. I made the velocity return; however I cant seem to quite get the CFrame turn right. I'm not asking for help; just seeing if anyone has.
dosinuyasha
#8235951Tuesday, May 05, 2009 9:18 AM GMT

Nvm. I found a complicated way to fix :MoveTo() to work again =D
level140roblox
#8236744Tuesday, May 05, 2009 11:24 AM GMT

i didnt think they deprecated it......
XlegoX
#8238076Tuesday, May 05, 2009 1:19 PM GMT

Is your stuff all anchored?
twwig
#8238371Tuesday, May 05, 2009 1:50 PM GMT

Dont you need a humanoid in the model?
XlegoX
#8238415Tuesday, May 05, 2009 1:53 PM GMT

He's talking about Model::MoveTo(pos), not Humanoid::MoveTo(pos, part)
MrDoomBringer
Top 100 Poster
#8245197Tuesday, May 05, 2009 8:03 PM GMT

:MoveTo(vector3) is still a valid function inside of the Model object.
Meelo
#8245230Tuesday, May 05, 2009 8:04 PM GMT

Yeah. I use it occasinaly. Although, I recommend using CFrames. Much more possibility.
level140roblox
#8245288Tuesday, May 05, 2009 8:05 PM GMT

Technically the correct syntax is :MoveTo(Vector3, Part), but neither me or any other scripter has found use in the Part... To move a model... Model:MoveTo(Vector3.new(#,#,#)) And the model will move over to there...
Intile
#8245387Tuesday, May 05, 2009 8:07 PM GMT

Oh, sheesh, don't scare me like that.
level140roblox
#8245430Tuesday, May 05, 2009 8:08 PM GMT

Lol. As Meelo sais, changing a part's cframe that is touching a part will move the touching parts too. Part.CFrame = CFrame.new(#,#,#)
Meelo
#8245478Tuesday, May 05, 2009 8:09 PM GMT

I never said that because that's not true. It only works on motors (I think. An update broke it for welds, snaps, etc.)
level140roblox
#8245543Tuesday, May 05, 2009 8:11 PM GMT

Really? It used to move the models, I used to switch cframes to move model around... Maybe I did that with characters... which would explain the motors...
MrDoomBringer
Top 100 Poster
#8245565Tuesday, May 05, 2009 8:11 PM GMT

@level: There's no argument for a part, that's the humanoid:MoveTo() function.
level140roblox
#8245666Tuesday, May 05, 2009 8:13 PM GMT

Really? Why am I so off today...
DingDong272
Top 100 Poster
#8245668Tuesday, May 05, 2009 8:14 PM GMT

I think WalkToPoint and WalkToPart are more efficient.
foofoogouls4
#8248698Tuesday, May 05, 2009 9:22 PM GMT

WalkToPoint kills you if theres lava in the way . . . .
1waffle1
#8252888Tuesday, May 05, 2009 10:42 PM GMT

LOL @ Foofoo. xD
Davidii
#8255172Tuesday, May 05, 2009 11:29 PM GMT

What I would appreciate is a MoveToExact() that would move a model to a position EXACTLY instead of moving it up. Or at least, being able to use MoveTo when the Model is not in game.Workspace.
blobbyblob
#8255329Tuesday, May 05, 2009 11:32 PM GMT

Hmm... I think I'll make that, David.
Davidii
#8259402Wednesday, May 06, 2009 1:02 AM GMT

Lol.
blobbyblob
#8260187Wednesday, May 06, 2009 1:19 AM GMT

Wow, I made that then forgot to post it. Here. _G["MoveToExact"]=function(model,position) xL=model:GetChildren()[1].Position.x xR=model:GetChildren()[1].Position.x yL=model:GetChildren()[1].Position.y yR=model:GetChildren()[1].Position.y zL=model:GetChildren()[1].Position.z zR=model:GetChildren()[1].Position.z for count,a in pairs(model:GetChildren()) do if xL>a.Position.x then xL=a.Position.x end if a.Position.x>xR then xR=a.Position.x end if yL>a.Position.y then yL=a.Position.y end if a.Position.y>yR then yR=a.Position.y end if zL>a.Position.z then zL=a.Position.z end if a.Position.z>zR then zR=a.Position.z end end center=Vector3.new((xL+xR)/2,(yL+yR)/2,(zL+zR)/2) t=center-position for count,b in pairs(model:GetChildren()) do b.Parent=nil b.Position=b.Position-(t) b.Parent=model end model:MakeJoints() end
MicroUser
#52316489Monday, August 08, 2011 3:49 AM GMT

Nah

    of     1