Nick Karasch

Member

37

171 Neutral

• Rank
Member
1. Euler angle rotations

I used ZYZ, doesn't that match up to what that says? Thanks for your input
2. Euler angle rotations

http://wolfr.am/1cjQWiv   Does that look right? I would just go ahead and try it but I have no idea how my end result is supposed to look. All I can do is make sure I'm right on a theory level.
3. Euler angle rotations

"You will eventually regret any use of Euler angles." -John Carmack   Part of my assignment:   So I need to produce a transformation matrix for these rotations     These kinds of rotation matrices can't give me rotations around the "new" y' and z'' can they? aren't they only relative to the x, y and z of my coordinate system?
4. Euler angle rotations

How would you accomplish this? I know how to do rotations around the X, Y, Z axis, but those are not applicable in this case other than the inital rotation right? It's the rotations around the "new" axis that are throwing me off.
5. Power Up Table Tennis Contest

I would like to participate as well
6. All matrix operations in shader?

Thanks, I don't know about instanced rendering yet but now I have something new to read about   I think it's all opinion but I disagree about me reusing my work being unfair to other students. If I have spent 12 hours a day working on this stuff since school resumed, I don't think it's unfair for me to get to reuse code. It's also NOT unfair to me that I have to start over, I wasn't trying to say that either.
7. All matrix operations in shader?

Thanks for the friendly reply. Yeah it is very frustrating, I have my 4000+ line "3D engine" I have been working on that would make this assignment take 10 minutes. I expected I could just strip it down to the essentials and reuse my code for these assignments. Now I'm having to start over, sweating over finding a new way to do the basics in the way he wants.
8. All matrix operations in shader?

I ask my Graphics Programming professor if I could use something I am familiar with like GLM and he said no, we are supposed to do everything in the vertex shader. From my experience/understanding, it makes more sense to calculate the model-view-projection matrix once per model for this simple program and pass it in through a uniform.   I think he wants us to create all of the matrices in the shader code, can that ever make sense? I don't understand why you would EVER create your main view and projection matrices within a shader. Thanks
9. Android GLES1 2d collisions detection

Now that I'm working out how to keep track of the locations of my objects outside of OGL, another question has popped into my head. Would reloading a fresh set of  pre-transformed vertices into OpenGL every frame be significantly slower than using glTranslate, glScale etc?   I'm dealing with 2D here, usually arrays of 12 values. something like: draw(){ vertices = somewhereElse.getVertices(); vertexBuffer.put(vertices); //blah blah blah gl.glVertexPointer(3, GL10.GL_FLOAT, 0, vertexBuffer); //draw stuff //blah blah blah }   Also, thanks for the SAT advice. I might use something like it.
10. Android GLES1 2d collisions detection

So far I can draw textured quads (triangle strips), move them and it all works independently of screen resolution and aspect ratio. I'm hitting a huge snag when it comes to collision detection. My only prior experiences were with fixed resolutions with no rotation.   How do you guys handle it? Is there any easy way to get my objects vertices after a translation and rotation? I know how to peek at the model view matrix and it isn't of much help as far as I can tell. I feel like all of my problems would be solved if I could just get the post-transform coordinates of my vertex array.