Channel the within!

Channel the within!

yes!!

I am not yet a master of , and therefore cannot understand the meaning of the messages gives me.

But I will try!

dude, it's simple axis inversion




what the fetch man







i should be making BRO

Hmm... I think the problem goes deeper than that. For one thing, I'm not even sure of where to check for collision. I'll have to check the tutorial.

i do believe syniphas is a designer of sorts

criticism really isn't your thing is it

I edited it once I realized what he was talking about.

Now, I think I've found the bug, but I'm far from fixing it. The problem is not in the formula, it's in how the mesh normals are read. What are mesh normals? They're the "normal" points in a 3D mesh (model). They determine which direction the polygons face. There is one normal for every polygon. If one can get the normal, then one can use that information to find the angle of the polygon.

Now, these "normals" can be read one dimension at a time. X,Y,Z. The number for each dimension returns how far away the normal is from the actual polygon itself, on that axis. I know, it sounds a little backwards, but that's just how it works. By default, if each normal is represented as a line, then that line is exactly 1 unit long. So, if it's sticking straight up in the air, then that normal reads 0,1,0. If it's to the side on the X axis, it reads 1,0,0. If it's at a 45 degree angle, it might read .5,.5,0. Each "normal" dimension has its own command to return the value. The commands are:
getCollisionNormalX()
getCollisionNormalY()
getCollisionNormalZ()

Given that, how might one make a function (subroutine) to get the angle of the polygon on each axis? Well, to start with, all dimensions but the one you need the angle for are used to find the angle on that axis. (You need X and Y to get Z or X and Z to get Y.) Now, since each normal dimension is a distance, then that saves us some work. There is a function in DarkBASIC called atanfull() that gets the degree angle based on two lengths. Hmm... Does that mean that x#=atanfull(getCollisionNormalY(),getCollisionNormalZ())? Well, it should. The only problem is that the rotation seems to be different from what we want by about 90 degrees or so.

dude there is no collision in bigrigs why are you trying to ruin it

dude there is no collision in bigrigs why are you trying to ruin it

Technically, it's not collision. It's raycasting. Without it, you could drive through the hills too, nobody wants that.

UPDATE: Well, I kind of fixed it (kind of). I was able to fix rotation along the X axis, anyways, and just by flipping some values. Now it resembles BROTRR a little more.

Too bad Khalad is still leagues ahead