Mario Kart Dev Diary: Cameras
1 min
Cameras
For the Mario kart game my first task is to understand how the cameras work in direct x. The way the cameras were set up was of a child class of game object, and then they have a child class of that called TPSCamera. This camera is used for third person and was set up by out lecturer for us.
The difference between the two is that the first one, you pass in the camera’s width, height, near view and far view and it would instantiate a camera and render whatever it saw from its position in the world. You could update the position and how far the camera rendered as well. With the TPSCamera, all the previous data was passed in when instantiating one, but also passed in a target and delta position. The target was what the camera to look at and the delta position was the position of the camera in relation to the target.
What I did to save on the number of classes is merge the TPSCamera class in to the camera class so now a camera can be both with having to use different class. In order to stop a camera being third person, a nullptr is passed in instead and it checks if the target pointer in the class is null and if it isn’t then it locks onto the target else it goes back to being a normal camera.
m_cam1 = new Camera(static_cast<float>(1200), static_cast<float>(800), 1.0f, 1000.0f, nullptr, Vector3(0.0f, 3.0f, 10.0f));
Subscribe
Subscribe to this blog via RSS.
Categories
Low level programming dev diary 28
Text based adventure dev diary 6
Level design developer diary 3
Game engine programming dev diary 14
Audio-visual production dev diary 7
Recent Posts
-
Posted on 27 Feb 2020
-
Posted on 27 Feb 2020
-
Audio-Visual Production: Particle System Mesh Spawning Issues
Posted on 20 Feb 2020 -
Posted on 12 Feb 2020
Popular Tags
Low level programming dev diary (28) Text based adventure dev diary (6) Level design developer diary (3) Post mortem (4) Ex-machina dev diary (11) Game engine programming dev diary (14) Network game dev diary (11) Audio-visual production dev diary (7)