Difference between revisions of "Talk:SetPos"
→Havok, setPos, and MoveTo: Note on items
imported>ABO (→Havok, setPos, and MoveTo: added setPos, getPos, and swimming) |
imported>Haama (→Havok, setPos, and MoveTo: Note on items) |
||
| Line 48: | Line 48: | ||
I've been doing some experiments and one thing to keep in mind is setPos is ignored by havok... so any velocity the object had before calling setPos will be retained, and havok will apply it's gravity and collision rules at the new position to update that velocity. This means if you do a "levitate" spell that uses setPos to hold the actor up in the air, the actor will accumulate velocity from gravity, so when your spell wears off he will slingshot into the ground. [[User:ABO|ABO]] 22:35, 21 May 2008 (EDT) | I've been doing some experiments and one thing to keep in mind is setPos is ignored by havok... so any velocity the object had before calling setPos will be retained, and havok will apply it's gravity and collision rules at the new position to update that velocity. This means if you do a "levitate" spell that uses setPos to hold the actor up in the air, the actor will accumulate velocity from gravity, so when your spell wears off he will slingshot into the ground. [[User:ABO|ABO]] 22:35, 21 May 2008 (EDT) | ||
:I'm not sure if I heard this about '''SetPos''' or '''MoveTo''' (I believe it was SetPos), but it did stop the velocity of arrows. That is, if you use '''SetPos''' to offset an arrow to the side, it will stop right there and drop to the ground.--[[User:Haama|Haama]] 11:54, 26 June 2008 (EDT) | |||
=setPos, getPos, and swimming= | =setPos, getPos, and swimming= | ||