Are you seriously unable to add semicolons for yourself?

I said this:
m_vLook.x = sin( ? ) * cos( ? )
m_vLook.z = sin( ? ) * sin( ? )
m_vLook.y = cos( ? )
Which becomes this in code:
m_vLook.x = sin( i ) * cos( a );
m_vLook.z = sin( i ) * sin( a );
m_vLook.y = cos( i );
Where i was “inclination” (the radians up or down your player faces) (notice how I said it was “inclination” and then gave the variable “i” as a substitute) and “a” is azimuth (the radians horizontally your player faces) and you weren’t able to figure out how to convert symbols to letters and add semicolons?
It was code from the first time I posted it.
Pick your variable for ? (I chose i but it could be anything), pick your variable for ? (I chose a but it could be anything), and add semicolons. Seriously?
You already know that ? is the vertical angle and ? is the horizontal angle. Moving the mouse up and down changes ? and moving it sideways changes ?. Cap vertical movement? Cap ?.


I am sorry, but how am I supposed to make this any more obvious?
I gave you the code from the start. You took one glance, saw a single symbol that was not C++, and decided it was a useless post. “Please give me code,” you instantly replied, yet the code was already there.
This is exactly what almost every book is going to give you, so if you can only handle to be spoon-fed I am not sure how far you will be able to go as a programmer.


L. Spiro

Time spent doing something isn't necessarily the best metric for skill, especially in an ambiguously multi-disciplinary field like programming. Given some of your recent threads and the kind of feedback you give in discussion, I'm surprised to hear you're a seasoned programmer with 10 years of experience.

Spiro knows their stuff, and explained what you needed the first time around. Computer science and programming is effectively a subset and intersection of branches of mathematics, so if you've been programming for 10 years and that should indicate "how far you've gone" as a programmer, you should be able to make use of a mathematical explanation. Not to mention, 3d programming and graphics is HUGELY math-driven. Your learning process is going to be pretty blind until you grasp the mechanics behind the functions you're calling.

Looking a several of your recent threads, you're missing a lot of the "why" and theory behind what you're trying to accomplish, which is making your task much harder. I'd embrace any assistance that tries to teach you theory and reasoning over directly handing you code.

Tip: "You seriously need to" ditch the ego.

As for your camera issues, I know you've solved the problem but here's another approach that I think is simpler to manage: create a rotation matrix that represents the camera's per-axis rotations (yawpitchroll in some form) which can be calculated off stored rotation values. Here's where the clamp can be applied to your pitch, as well. Then every update call, just apply the newly calculated rotation matrix to a unit forward, up, and right vector (unit x, y, and z respectively) and use those to create your look-at (view) matrix.

...And in retrospect I just described MJP's approach. Hooray redundancy.

I started programming since I was around 10-11 years old

Whee-hee. So did many of the other users here. Heck, I'm pretty sure some of the people who post around here are STILL 10-11 years old. However, as stated before, you are asking for someone to just give you the code you want. All that will do is force you to come back to the forums and beg when you can't do the same thing later on. MJP gave you a REALLY easy way to do it, L. Spiro, although somewhat curtly, gave you the answer you needed as well. Just... Listen.

That's enough. Closing this down.