OpenGL changing degrees into directions

Recommended Posts

Hi all, Can anyone show me how to change degrees into directions, for example I have 4 objects which move off at 0,90,180,270 degrees, how do I change these into x and y opengl movement. It could be any number of objects it's haow to do it mathmatically rather than the above example. Thanks

Share on other sites
You want to convert polar coordinates to Cartesian? The transformation is straight forward:

x = r • cos(a)
y = r • sin(a)

Where r>0 is the distance from origin to your point and a is the angle (0≤a<2π)

For normalized directions you have r=1, so you get

x = cos(a)
y = sin(a)

Hope this helps

EDIT: And make sure you don't mix up radians and degrees. Most implementations of sin and cos expect input in radians, whilst OpenGL I believe uses degrees.
You can convert degrees to radians by a simple transformation

y = T(x) = x • π / 180;

Where the input x in degrees and the output y will be in radians. And the inverse converts radians to degrees

x = T-1(y) = y • 180 / π

Share on other sites
The right triangle is one such that the hypotenuse (which represents your direction of movement in this case) forms the angle of movement with the adjacent, while the opposite completes the triangle. Assuming sector 1, the adjacent represents movement in x and the opposite represents movement in y.

The following relationships then hold:
1. the sine of the angle is equivalent to the length of the opposite divided by the length of the hypotenuse;

2. the cosine of the angle is equivalent to the length of the adjacent divided by the length of the hypotenuse; and

3. the tangent of the angle is equivalent to the length of the opposite divided by the length of the adjacent

You may remember them from trigonometry classes. Assuming a unit movement in the hypotenuse, then:

x-displacement = cos(angle)
y-displacement = sin(angle)

Scale these displacement by the number of units of real movement you want. Test for values of 90, 180, 270 and 0/360 degrees.

Create an account

Register a new account

• Partner Spotlight

• Forum Statistics

• Total Topics
627663
• Total Posts
2978521
• Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 10
• 10
• 12
• 22
• 13