It's likely that you are only testing ballvec.X/Y in your collision routine rather than the whole Rectangle, show us how you are determining the collision and 'bounce' and we can help you further
- Viewing Profile: Posts: WarAmp
Awesome job so far everyone! Please give us your feedback on how our article efforts are going. We still need more finished articles for our May contest theme: Remake the Classics
Community Stats
- Group Members
- Active Posts 308
- Profile Views 769
- Member Title Member
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Not Telling
450
Good
User Tools
Contacts
WarAmp hasn't added any contacts yet.
Posts I've Made
In Topic: Rectangle
30 August 2012 - 01:00 PM
You will need to give us more than just your drawing code if you want us to help with a collision issue 
It's likely that you are only testing ballvec.X/Y in your collision routine rather than the whole Rectangle, show us how you are determining the collision and 'bounce' and we can help you further
It's likely that you are only testing ballvec.X/Y in your collision routine rather than the whole Rectangle, show us how you are determining the collision and 'bounce' and we can help you further
In Topic: What do I do with this?
20 August 2012 - 10:41 AM
struct MyVertex
{
float x, y, z; // Vertex
float nx, ny, nz; // Normal
float u, v; // Texcoords
float a, r, g, b; // Color
float padding[4];
};
My openGL is a bit rusty, but I believe you want the value passed into the gl*Pointer() functions to actually point to the part of the struct that is relevant.
ie:
glNormalPointer( GL_FLOAT, sizeof(MyVertex), &(*RenderListIT)->RenderMesh->VertexData.nx ); glTexCoordPointer( 2, GL_FLOAT, sizeof(MyVertex), &(*RenderListIT)->RenderMesh->VertexData.u ); glColorPointer( 3, GL_FLOAT, sizeof(MyVertex), &(*RenderListIT)->RenderMesh->VertexData.a ); //etc....
In Topic: Calculate Slope with only three points?
14 June 2012 - 03:42 PM
If all you have is A(x, y) and B(x, ?) you simply don't have enough data. There are an infinite number of lines that pass through A(x,y) and the boundary B(x, ?).
You can set ? to any value and create a line, but there is no single specific line.
If you have an angle already, then JTippets post explains how to solve for ?.
You can set ? to any value and create a line, but there is no single specific line.
If you have an angle already, then JTippets post explains how to solve for ?.
In Topic: heading to position transform angle in C++
22 May 2012 - 06:03 PM
Ok Mike4, one more time:
What are you trying to do? There seems to be a language barrier issue here, perhaps describe your problem in your native language, and another poster can help you that way?
What do you mean by this? Are you saying that you have the location and heading angle of both the Source AND the Listener? If that's the case, you would use alListener3f with AL_POSITION to set the x,y,z and then use a separate call to alListener3f with AL_ORIENTATION to set the orientation. A quick google search will tell you how to use the given heading with alListener to create the 'at' and 'up' vectors you need.
If you only have partial information about the listener/source then please tell us explicitly the information you have.
What are you trying to do? There seems to be a language barrier issue here, perhaps describe your problem in your native language, and another poster can help you that way?
I can only use x,y,z and heading for source and listener.
What do you mean by this? Are you saying that you have the location and heading angle of both the Source AND the Listener? If that's the case, you would use alListener3f with AL_POSITION to set the x,y,z and then use a separate call to alListener3f with AL_ORIENTATION to set the orientation. A quick google search will tell you how to use the given heading with alListener to create the 'at' and 'up' vectors you need.
If you only have partial information about the listener/source then please tell us explicitly the information you have.
In Topic: heading to position transform angle in C++
16 May 2012 - 12:40 PM
If you are just trying to transform [0, 360] to [180, -180] then just:
newAngle = 180 - angle;
But what would really help us help you is some context. We can sort of see that you are having a problem with OpenAL, but other than just saying 'Not hearable at certain angles' we have no idea what you are doing vs. what the result is you are trying to achieve. Maybe even draw us some pictures to illustrate the problem?
Spend some time explaining the situation and we can spend more time trying to help. The more information you give us, the more we have to work with.
newAngle = 180 - angle;
But what would really help us help you is some context. We can sort of see that you are having a problem with OpenAL, but other than just saying 'Not hearable at certain angles' we have no idea what you are doing vs. what the result is you are trying to achieve. Maybe even draw us some pictures to illustrate the problem?
Spend some time explaining the situation and we can spend more time trying to help. The more information you give us, the more we have to work with.
- Home
- » Viewing Profile: Posts: WarAmp

Find content