31 replies to this topic

[moomoo112]

o now this is nice, definatly will help

[the sivart]

very good

[PaperCutGames]

11/10. THREE thumbs up. Has a lot of room for potential. Driving sim, roller coaster sim, 3d racing (like that of the gran turismo series, only in first person). It is endless! Kudos to you.

[Tepi]

11/10. THREE thumbs up. Has a lot of room for potential. Driving sim, roller coaster sim, 3d racing (like that of the gran turismo series, only in first person). It is endless! Kudos to you.

...Or then not. Without collision checking there won't be potential, at least not in the racing side.

And this is actually rather trivial to do if you know what you're doing. I know as I did a similar engine a short while ago. That supports also inclination.

And by the way, this topic is almost a year old.

[RamboFox]

Actually Tepi, you can implement collision detection - all we need is the height (z variable) which is taken from a path (we can check against the path's y position) apply gravity, constrict the z var to never be able to go under the z of the path - and simply check how far the car is from the centre of the track to determine when to bounce off the "boundry".

Simple stuff - I did it with a top-down 2D version of this.

And by the way, this topic is almost a year old.

Yeah, well BUMP. >:3

Edited by RamboFox, 29 July 2009 - 01:30 AM.

[Tepi]

Actually Tepi, you can implement collision detection - all we need is the height (z variable) which is taken from a path (we can check against the path's y position) apply gravity, constrict the z var to never be able to go under the z of the path - and simply check how far the car is from the centre of the track to determine when to bounce off the "boundry".

Yes. Too bad though that that can't ever be precisely correct with that method. The path isn't subdivided like the road is, you know.

[RamboFox]

Yes. Too bad though that that can't ever be precisely correct with that method. The path isn't subdivided like the road is, you know.

Actually, I have recently tested out a method where the car can only move forward, and pressing left and right increases/decreases the ofset along the path direction.

Think of it like so:

draw_x=x+lengthdir_x(ofset,path_direction+90)
draw_y=y+lengthdir_y(ofset,path_direction+90)

I don't have GM with me right now, so this code may be slightly wrong (but I think you'll catch my drift).

[PaperCutGames]

What event in what object wold that go under?

[Tepi]

Yes. Too bad though that that can't ever be precisely correct with that method. The path isn't subdivided like the road is, you know.

Actually, I have recently tested out a method where the car can only move forward, and pressing left and right increases/decreases the ofset along the path direction.

Think of it like so:

draw_x=x+lengthdir_x(ofset,path_direction+90)
draw_y=y+lengthdir_y(ofset,path_direction+90)

I don't have GM with me right now, so this code may be slightly wrong (but I think you'll catch my drift).

It might be slightly wrong because no such thing as path_direction exists.

But don't try to come up with anything. If you still didn't get my point, it was that the road consists of triangles, and nothing more but triangles. A path is always too smooth for it to be exactly correct. So as long as your road doesnt work in the precision infinity (always), you will end up under or over the specific z-coordinate you'd normally want to be on.

The technique you'd be searching for indeed relates to finding the normal of the path, but I can tell you the rest of the math is not just elementary math. It relates to the triangles, and there's no way around it.

[RamboFox]

Yep, I meant "direction" - because once you set a path to an instance, it takes the form of the path.

We could come to a close approximate to the actual height, but yes - the way you described it will end up with the car diping below the track at some points.

[ean]

Ooh...nifty. The shadows are a nice touch.

There is no such thing as a path direction function, but you can make your own.

To get the direction of a path on any part of the path, use point_direction(path_get_x(pos1),path_get_y(pos1),path_get_x(pos1),path_get_y(pos1)).

Using really small digits (like .0001) and you can get a really accurate result.

Edited by ean, 24 March 2012 - 07:56 PM.

[THE_GAME_EDITOR]

The texture repeats itself by mirroring it along the path.
If i want the repeat it like normal, what should i do?

Can anyone please tell me?