Description
4-5 Milestone: Interactivity in a 3D Scene
This week you will be continuing to work on the 3D scene you already began to build, based on a 2D image you selected. Now it is time to incorporate input devices and camera movement so you will be able to traverse your scene more easily.
Prompt
You will complete your work in Visual Studio, being sure to work from the project file you already created in a previous milestone. This file already has the libraries set up correctly and contains the 3D object you built, which will be necessary for you to add to this week.
Specifically, you must address the following rubric criteria:
Create a 3D plane to situate a 3D scene. This will serve as the base for the rest of the objects in your world. Depending on your 2D image this plane may be used to represent a desk, the ground, a table, or something else entirely. It will be important to work on this first so you will understand the scope of the world your camera will be traversing. A plane is also a relatively simple shape so it will be a good place to start when managing the placement of different objects in your scene. Remember, you will need to take into account where the plane is located in relation to the 3D object you developed during a previous milestone (which used multiple 3D shapes).
Apply horizontal, vertical, and depth camera navigation around a 3D scene. It is recommended that you use the following keyboard controls to manipulate the basic camera movement:WASD keys: These keys should be used to control the forward, backward, left, and right motion.
QE keys: These keys should be used to control the upward and downward movement.
Apply nuanced camera controls to a 3D scene. It is recommended that you use the following mouse controls to allow a user more specific input options for how they view the 3D scene:Mouse cursor: This should be used to change the orientation of the camera so it can look up and down or right and left.
Mouse scroll: This should be used to adjust the speed of the movement, or the speed the camera travels around the scene.
Create perspective and orthographic displays of a 3D scene. Use the tap of a keyboard key to allow a user to change the view of the scene between orthographic (2D) and perspective (3D) views at will. (Hint: check the glViewport and the glOrtho functions.) For consistency, please use the letter “P” keyboard key. To accomplish this work, you will be switching the function call to retrieve either the perspective or orthographic projection matrix. Note that you will be keeping the camera in the same orientation that you already developed.
Create code that follows a logical flow without syntax errors. The code you create has to be executable and all the code that is included needs to be reached by the execution. Note that not everything should be written in a single function and your work should be well-modularized.
Apply coding best practices in your creations. Pay particular attention to the way you format and comment your code. Program code should be easy to read and follow industry standard code formatting practices, such as indentation and spacing. Commenting best practices should be in place to ensure the source code is briefly and clearly explained using descriptive comments.
Guidelines for Submission
Submit a completed ZIP folder with all of your code, which may include one or multiple CPP files along with Visual Studio project files. Also make sure the ZIP folder includes an EXE file, because without this your code will not be able to run. Checking for the EXE can be used as a quick reference on the functionality of your code before you submit.
Module Four Milestone Rubric
CriteriaExemplary (100%)Proficient (85%)Needs Improvement (55%)Not Evident (0%)Value3D PlaneExceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner; areas demonstrating exemplary work may include creating a plane with a particularly successful interaction with the 3D scene, as applicable to the 2D reference image
Creates a 3D plane to situate a 3D scene
Shows progress toward proficiency, but with errors or omissions; areas for improvement may include creating a plane that is relevant for the 2D image or that successfully encompasses the scene
Does not attempt criterion
20
Camera Navigation: KeyboardExceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner; areas demonstrating exemplary work may include creating navigation that is particularly clear or intuitive for the user
Applies horizontal, vertical, and depth camera navigation around a 3D scene
Shows progress toward proficiency, but with errors or omissions; areas for improvement may include applying camera movement in all identified directions
Does not attempt criterion
20
Camera Navigation: MouseExceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner; areas demonstrating exemplary work may include creating a speed of translation that is appropriate or adjustable at runtime
Applies nuanced camera controls to a 3D scene
Shows progress toward proficiency, but with errors or omissions; areas for improvement may include appropriately controlling the speed of the navigation
Does not attempt criterion
20
Perspective and Orthographic DisplaysExceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner; areas demonstrating exemplary work may include the ability to dynamically change between the two types of projection while the simulation is running
Creates perspective and orthographic displays of a 3D scene
Shows progress toward proficiency, but with errors or omissions; areas for improvement may include creating both perspective and orthographic displays that can be easily switched between
Does not attempt criterion
20
LogicExceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner; areas demonstrating exemplary work may include creating code that is particularly well-modularized and logical
Creates code that follows a logical flow without syntax errors
Shows progress toward proficiency, but with errors or omissions; areas for improvement may include ensuring there are no errors once code is compiled, ensuring the code is executable, or ensuring the flow of the execution reaches all of the code
Does not attempt criterion
10
Best PracticesExceeds proficiency in an exceptionally clear, insightful, sophisticated, or creative manner; areas demonstrating exemplary work may include creating code that shows a strong attention to best practices in both formatting and comments
Applies coding best practices in creations
Shows progress toward proficiency, but with errors or omissions; areas for improvement may include creating code that is easy to follow and is commented appropriately
Does not attempt criterion
10
Total:
100%
