vSpritePos += vSpriteDir * fSpeed * fTime;
I assume your direction is normalized and you have math operators on your vectors that allow you to perform vecA + vecB and such.
Each frame:
vSpritePos += vSpriteDir * fSpeed * fTime;
fTime is the time since the last update.
L. Spiro
[quote name='YogurtEmperor' timestamp='1313338778' post='4849016']
I assume your direction is normalized and you have math operators on your vectors that allow you to perform vecA + vecB and such.
Each frame:
vSpritePos += vSpriteDir * fSpeed * fTime;
fTime is the time since the last update.
L. Spiro
. If anyone wants to know how a vector2 is a vector when it actually only has 1 point. Think of it as 0, 0 -> xValue, yValue...
if (bob == 15) // Update every 15 updates which is 1/4 of a second
{
bob = 0;
conPos = new Vector2(10, 30);
GamePadState gamePadState;
gamePadState = GamePad.GetState(PlayerIndex.One);
spritePos += conPos;
}
else
{
bob++;
}
Ah I think I've figured out this vector2 stuff somewhat
So if we have a vector of 10, 10 it's actually an 'line' going from 0,0 to 10,10...
Please correct me if I'm wrong anyone...
So I tried playing around with this:
if (bob == 15) // Update every 15 updates which is 1/4 of a second
{
bob = 0;
conPos = new Vector2(10, 30);
GamePadState gamePadState;
gamePadState = GamePad.GetState(PlayerIndex.One);
spritePos += conPos;
}
else
{
bob++;
}
This works as expected with it moving every 1/4 second....
However if conPos.Normalise(), the sprite moves very smoothly (updating every frame I'm guessing)... Why does that happen?
All I can read up on is that you Normalise() for the 'velocity' to stay the same while going diagonally...
By having the direction as a unit vector you can use this in collision detection as it tells you which direction the object is moving in but not the speed of it which you don't need in the intersection test of your collsions. Then with the speed variable you can determine the time when this collision is happening.
spritePos = new Vector2(100,200);
spritePos.Normalise();
