|
What's the best way of representing surfaces in a 2d top down racing game? I'd like paved and dirt surfaces in my game to have different friction properties. Would you break up the map into a grid and simply check where in the grid the car is to determine the friction? Or is there a better way of managing it? The roads and dirt are not self contained all or nothing tiles either, so I'd have to handle a grid section that contained some road and some dirt. |
|||||||||
|
|
It sounds like the root of what you're asking for is a way of determining the friction of the ground at a given point in your map. A simple way of doing this could be to create a one-channel (grayscale) texture that represents the friction of the ground. Sample this texture at the point of the car (or each of the four wheels if you're feeling fancy) to get friction at runtime. These textures should make it relatively easy to author content for. You could probably whip up a debug mode that overlays the friction map on top of the visual texture to double check that things line up right. It allows you a lot of freedom in the friction gradient at the fringe of the road. You could probably come up with a data structure that uses less memory, but with a top down sprite based game I'm guessing that's not going to be much of an issue. |
|||||
|
|
I think what you're asking is 2D polygon collision detection: detect that the car shape is over a certain road shape, and then apply some physics effect like slowing down to the car. This site has pretty pictures and has code that does what you're asking for, although you could probably pull it off just with bounding box collision detection. It really depends on what your game will really look like; "The roads and dirt are not self contained all or nothing tiles either" is somewhat vague. |
|||
|
|
