• 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
Heelp

I Can't Properly Rotate The Enemy To Look At Me All The Time.

15 posts in this topic

Guys, I spawned an enemy that moves towards me all the time no matter where I move.

 

Now I need to somehow rotate properly the enemyRun animation so the enemy faces ME all the time, no matter where I move.

 

Sounds easy, but that glm::rotate function is unbelievably messed up ( at least for me ).

 

What my logic is:

 

1.Find the vector pointing from 'enemyPosition' to 'playerPosition' and normalize it. Lets call that vector 'movementDirection'.

 

2.Now find the vector that shows the current direction that the enemy faces. When my enemy is spawned, I made it to face the +X axis by default.

 

3. Then find the angle between the current direction the enemy faces( along +X ) and the direction the enemy needs to face ( towards me ) and somehow regulate it to rotate somehow. ( this is the part where I don't know what I'm doing )

 

Update 1: The glm::rotate function accepts radians not degrees, this means that rotation.w should be in radians, so glm::radians( angle ).

Update 2: Dot product doesn't work for 360 degrees, just for 180, I need more vectors to cleary distinguish the position in a 360-degree environment.

Update 3. In order to get the 360 degrees I need a third vector, lets say I can get the third vector using a cross product, but then how to use the third one properly?

 

The movement is ok, but the rotation is messed up. Here is the code:

 

Note: rotation.w is the rotationAngle, rotation.y = 1.0f means: rotate along the Y axis.

void Enemy::moveTowardsPlayer( glm::vec3 playerPos )
{
    movementDirection = normalize( playerPos - position );
    rotation.w = dot( movementDirection, faceDirection )*someNumberIdontKnow; //This is the rotation angle
    rotation.y = 1.0f;
    position += movementDirection/50.0f;
}
Edited by Heelp
0

Share this post


Link to post
Share on other sites

Use the formula arcos(dot(v, w) / (mag(v) * mag(w)) where v and w are the players position and the enemies position.

 

This will give you the angle between the two. Use that angle to rotate your enemy to your player.

 

Edit: That will give you the value in degrees. Multiply the resulting angle by PI/180 to convert it to radians.

Edited by ExErvus
0

Share this post


Link to post
Share on other sites

Yes, this is the dot product, but it works only for [ 0; 180 ], not for [ 0; 360 ], so I need something else.

Edited by Heelp
1

Share this post


Link to post
Share on other sites

This is not the dot product. The dot product is a part of the formula. This formula tells you exactly how many degrees you need to rotate.

0

Share this post


Link to post
Share on other sites

Nanoha and Tangletail, thanks. I will gather some info about quaternions, I have one 3d math book focused on games, will have to read one chapter on quaternions today, apparently.

 

ExErvus, two things:

 

First, the dot product maps:

180 degrees to -1

90 degrees to 0

0 degrees to 1

 

That's why your formula doesn't work, man.

 

arccos will turn [ -1; 1 ] into [ 0; 180 ] range, not [ 0 ; 360 ]. Dot product between 2 vectors doesn't distinguish between left and right. Quaternions are the answer.

 

Second, see this website: http://www.cplusplus.com/reference/cmath/acos/

This says that acos ( which is the c++ 11 <cmath> variant of arccos ) returns the principal value of the arc cosine of x, expressed in radians, not in degrees, as you said.

Edited by Heelp
1

Share this post


Link to post
Share on other sites

Guys, I fixed the problem by using neither quaternions, nor atan2().

 

I figured that if one dot product helps me to determine an angle in the range[0; 180], then two dot products can do it for [0; 360]

so I used 3 vectors to determine the rotation , not 2.

 

First, I find the cross product of the upVector( +y ) and the faceDirection( +x ), which happens to be +z ( or -z, depends on the order of the arguments ).

Then I say:

void Enemy::moveTowardsPlayer( glm::vec3 playerPos )
{
    crossVec = glm::cross( faceDirection, upDirection ); // Find the vector pointing at +z
    movementDirection = normalize( playerPos - position ); // find the vector between playerPos and enemyPos
    float dotProduct = dot( movementDirection, faceDirection );
    float crossVecDotProduct = dot( movementDirection, crossVec );
 
    if( crossVecDotProduct < 0 ) // If I turned left
    {
        rotation.w = std::acos( dotProduct ); calculate degrees from 0 to 180
    }
    else //else I turned right
    {
        rotation.w = std::acos( -dotProduct ) + M_PI;  calculate degrees from 180 to 360( thats why I increment by Pi )
    }
 
    rotation.y = 1.0f;
    position += movementDirection/30.0f;
    position.y = -0.5f;
}
Edited by Heelp
1

Share this post


Link to post
Share on other sites
So you shouldnt use angles for that i wont explain whys that. Just vreate a rotation matrix since you will know 2 vectors you are all good firt vector is front enemy-player, second one is the up vector with these two normalized you make cross product and end wirh side vector if front and up aint parallel (i might use wrong word) then you need to normalize that cross product .build a mat out of these 3 vectors and aply it to enemy object simple as hell
-1

Share this post


Link to post
Share on other sites

I've used many tutorials from that same website and it seems that I've totally missed out that one. Will check it definitely! 

Thanks!

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