Scripting Helpers is winding down operations and is now read-only. More info→
Log in to vote
0
Why is this CFrame not working properly?
01 | while wait() do |
02 | for i = 1,10,1 do |
03 | wait(.5) |
04 | script.Parent.Size = Vector3.new(script.Parent.Size.X,i,script.Parent.Size.Z) |
05 | script.Parent.CFrame = CFrame.new(Vector3.new(script.Parent.Position.X,script.Parent.Position.Y+.5,script.Parent.Position.Z)) |
06 | end |
07 | for i = 10,1,-1 do |
08 | wait(.5) |
09 | script.Parent.Size = Vector3.new(script.Parent.Size.X,i,script.Parent.Size.Z) |
10 | script.Parent.CFrame = CFrame.new(Vector3.new(script.Parent.Position.X,script.Parent.Position.Y-.5,script.Parent.Position.Z)) |
11 |
12 | end |
13 | end |
Even though with CFrame, parts can go through parts, for some reason this isn't working properly.
0
How exactly isn't it working? adark 5487 — 10y
0
You know how CFrame allows parts to go through each other? Well It's kinda working as if I just changed the Position. Like the parts won't collide with each other. EzraNehemiah_TF2 3552 — 10y
0
I'm not sure, since i don't use CFrame a lot, but i would recommend you to unanchor the parts first, and then when u end u can anchor them. marcoantoniosantos3 200 — 10y
0
You don't need to anchor them. EzraNehemiah_TF2 3552 — 10y
1 answer
Log in to vote
0
Here is how I generally use CFrame and it works for me every time:
1 | script.Parent.CFrame = script.Parent.CFrame (+ or -) Vector3.new(x,y,z) |
So I reccomend you try something like this:
1 | for i = 10,1,-1 do |
2 | wait(.5) |
3 | script.Parent.Size = Vector3.new(script.Parent.Size.X,i,script.Parent.Size.Z) |
4 | script.Parent.CFrame = script.Parent.CFrame-Vector3.new(0,0.5,0) |
5 | end |