• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
lesshardtofind

Ray to Plane Collision

4 posts in this topic

Hey!

 

   I've been trying, for a couple days, to get my Camera to smoothly "walk" across any loaded heightmap with any size triangles.  It was suggested to me to use a ray to plane collision to get this done, but I'm having some issues figuring out where I slipped up.  Maybe someone here can shed some light on my ignorance.

 

This function should return a Vector3, which is a struct of 3 float, that represents the point at which collision would occur.

 

Here is the code:

 

Vector3 IntersectionPoint(Triangle ColTri, Vector3 CameraPos){
  float a = DotProduct(Normal(ColTri), Vector3(0, -1, 0));  // Vector {0, -1, 0} is the up vector, Normal(ColTri) returns the normal of the triangle passed
  if(a == 0)
    return CameraPos;
  Vector3 Temp;   //this is used to calculate the distance from the plane
  Temp.X = CameraPos.X - ColTri.VertexA.X;       
  Temp.Y = CameraPos.Y - ColTri.VertexA.Y;
  Temp.Z = CameraPos.Z - ColTri.VertexA.Z;
  float X = DotProduct(Normal(ColTri), Temp);
  float Mag = Magnitude(Normal(ColTri));
  float DistanceToPlane = X/Mag;               // end of the distance to plane formula
  Vector3 ToReturn;                                   // the vector to return
  float Multiplier = DistanceToPlane/a;
  ToReturn.X = CameraPos.X;
  ToReturn.Y = CameraPos.Y-((-1)*Multiplier);
  ToReturn.Z = CameraPos.Z;
  return ToReturn;
}

 

 

I know there may be a couple extra data types as I was trying to dumb down the logic for myself to understand it.  I'm very sketchy on calculus still.  Been reading on plane math and planes equations, but still haven't found anything yet.

 

Thanks for your time!

 - John

0

Share this post


Link to post
Share on other sites
I'm sorry I don't have time to dive into your code right now, but I suggest, if you have further trouble making it work,
That you base the y value on the result of a concept called "Barycentric Coordinates". If you're using a grid of quads,
it's easy to compute. (Given that the area of a right-angled triangle is 0.5h*b)

It revolves around weighted coords of the triangle (A, B, C) that currently surround your camera (P).
Basically, the weight of A (wA) is
area(B.xz, P.xz, C.xz) / area(B.xz, A.xz, C.xz)
(the surrounding triangle) / (the opposing triangle to the triangle-point in question (here: A))

So you can add together
A.y*wA + B.y * wB + C.y * wC
to get the resulting P.y. Edited by SuperVGA
2

Share this post


Link to post
Share on other sites

Also, in order to get your camera's "position" and "look at" vector to travel smoothly, research on "linear interpolation" might prove useful (quadratic/cubic bezier curves too but for later) in order to prevent the player, especially the programmer, from getting sick.

0

Share this post


Link to post
Share on other sites

Thank you for the responses.  I adjusted my Vector3 structure to defined operator overloads which made the entire equation alot easier.  It now works to a degree but not how I expected.  It has me floating to the right point rather than just staying on top of the terrain.  It made me realize I'm going to need working structs and formulas in a library before I really delve into this so I'm going to jump into some calculus websites for a few days and program a math library for me to use.

 

I will look into the Linear Interpolation, Barycentric Coordinates, and quadratic/cubic bezier curves.  (thanks for that sometimes I just need to find the right phrase to google)

0

Share this post


Link to post
Share on other sites
If it's a heightmap, you should already know the A,B,C of any given triangle of the terrain (you must know at least two points on the plane to calculate third), and then use SuperVGA's formula to calculate it. Calculating collision in real-time against a terrain is a waste of time (unless it's morphing infinite terrain), and you want that time to be spent on collision detection with other things, i.e. buildings, moving objects, etc.

EDIT: Also, is your Temp vector normalized, when calling DotProduct, or do you normalize inside? Edited by Mercile55
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0