Printable View
Does anyone have any good links with info on how to achieve realistic car physícs in a 2D world? In school we've currently only gone as far as, v=at and all the other stuff not involving friction(s=½at²). From this I can make it move forward and backwards sort of realistically... But it still doesn't involve friction... I see this as a good opportunity to get ahead in school as well, so please give me all you got =).
Do you actually want realistic car physics, or realistic looking physics.
If it doesn't need to be perfect it'll be a lot easier.
For example for friction (assuming you're using a vector to represent speed/direction) you could just multiply it by a number less than 1 each frame.
I found this:
http://home.planet.nl/~monstrous/tutcar.html
But if you guys have anything else, feel free to post it as well, since this is 'a bit' to precise(airresistance really isn't a neccesity)
Look =)... Well, my problem really is to simulate turning... and sliding, I really don't know where to start on that... When does it start sliding on that kind of ground(say asphalt) at a certain angle and velocity...Quote:
Originally posted by SLH
Do you actually want realistic car physics, or realistic looking physics.
If it doesn't need to be perfect it'll be a lot easier.
For example for friction (assuming you're using a vector to represent speed/direction) you could just multiply it by a number less than 1 each frame.
To get good physics it's not gonna be easy, but what i'd do is have a location and velocity of the back of the car, and one for the front.
Do this for the front and the back.
You have the actual velocity of the front, and the desired velocity (dictated by the speed of the wheels (back), and the direction they're facing(front)). To get the desired velocity for the front simply assume the wheels are moving the same speed as the car is moving i.e. desired velocity for the front and actual velocity for the front have the same magnitude.
Perform ActualVelocity-DesiredVelocity (and store it in a vector called 'Slide'. If the magnitude of this vector is past a particular value then the wheels (front or back) will slide. The amount they slide could be a proportion of the 'slide' vector.
Now you have the desired velocity and the slide velocity for the front and back of the car. Now we need to do friction for each wheel to stop the car going super speed when in a straight line.
The vector for this would simply be a proportion of the difference between the actual velocity and the desired velocity. HOWEVER it's a vector in the oposite direction of the motion of the wheels (it's the magnatude that's proportional).
Doing it this way will take into account breaking, provided you calculate your desired velocity as 0 if breaking.
Now simply add the desired velocity, the slide velocity and the friction velocity for the front and back wheels.
Finally to prevent the car 'stretching' get a vector from the front wheels to the back wheels, then make the back wheels' position = the frontwheels position plus a vector the length of the car, in the direction of the vector you just made.
Note, this doesn't model the physics in any way realistically, it should look nice though. :)
If you want to add realism start doing things like using the friction formula to calculate just how big the 'slide' vector should be etc...
Okay... This may sound silly... But i've always seen a vector as a line in an X,Y system(what's it called in english?) but that doesn't seem to be the right definition of it - could you tell me in short what it actually is?
And thank you many times for the info already given, It's a great help =).
A vector is made up of two or more 1D dimensions.
When working in 2 dimensions (as you are) there are X and Y components.
A vector can be used to represent either a position relative to the origin:
Vector.X = 5
Vector.Y = 9
Vector now represents (5,9)
Or it can be used to represent a direction with magnitude.
Vector.X = 3
Vector.Y = 4
Vector now represents a (particular) direction with magnitude 5.
I think of a vector as an arrow (since it has a direction).
Hmm, so I would create a vector as a type with the fields X and Y ? Making it an arrow pointing to it? And why would the magnitude be 5? Is that a number relevant to the X Y coordinates you gave, or simply something you just said? Sorry for me being so bad at this =/
I've drawn a representation of the vector i described.
http://www.vbforums.com/attachment.p...postid=1786435
It's magnitude is simply it's length. And as the vector form's a right-angled triangle it's magnitude is simply as follows:
squareroot(square(x) + square(y))
Yes, a vector would have fields X and Y.
Not sure what you mean about making it an arror pointing to it.
The arrow is to help with understanding only (as you said you think of it as a line).
hmm, Okay then - I get what a vector is now =) - thanks....
I'm gonna try putting something together from what you said, but I might have some more questions.
Thanks a lot for the great help so far....
How is the direction of a vector defined.
I'll use a 3D vector
Vector.X = 10
Vector.Y = 10
Vector.Z = 10
Now how do I know which direction i am moving...generally I would believe given the angle this would be forward.
Vector.X = -10
Vector.Y = -10
Vector.Z = -10
Now given the angle, this would be backwards?
If so, then a vector only has 2 directions given an angle...forward and backwards.
Em I wrong?
The direction of a vector is totally dependant on your coordinate system.
Not sure what you mean by 'given the angle'? What angle do you mean?? A vector doesn't store an angle (you can work any angle you need out though).
A little example:
Lets say that in my coordinate system x goes left to right, y goes top to bottom, and the origin is top-left. Let's also pretend that my Z axis goes from front to back, i.e. from close to the screen to away from the screen.
the 3D vector
Vector.X = 10
Vector.Y = 10
Vector.Z = 10
would start at the origin (all vectors start at the origin when it's defining a direction), and go 10 units left, to units down, and 10 units away from the screen.
Basically 10 units along each axis.
To get a vector in the opposite direction you are correct, it's simply the negative of that vector.
i.e.
Vector.x = vector.x * -1
Vector.y = vector.y * -1
Vector.z = vector.z * -1
BTW, it's a good idea to make operators for things like addition, subtraction, unary minus, finding the magnitude, multiplying by a number, finding the 'unit vector' (given a vector) etc...
Thanks for the nice explanation.
with dx7 at least...maybe not others, if you type
#define D3D_OVERLOADS
you get a few operators like that.
But yes, it would be a great idea to make operators for it