CSCI 441 - Computer Graphics

This assignment is due by September 8, 2017 by 11:59pm.

You step back to admire your work. You're not quite sure how you did it, but there it is for all to see. The sign for your soon to be ride is freshly painted and standing. The queue for your line is in place and goes right underneath. After you finish attaching the "You Must Be This Tall To Ride" sign, the man returns.

"Wonderful! Absolutely splendid! Ra is most pleased indeed. We would like to award you with this honor of, 'Employee of the Month!' Stand next to your work and our park photographer will be around to give you further instructions."

And so you wait...

"Very sorry I am late! Much of the park is still being constructed and I am busy cataloging all of our new rides." says Sheila with a smile.

She then continues, "Is that what you are going to wear for the photo? That will not do. Everyone will see your picture as they enter the park. We must get you changed. Luckily, I always come prepared." She heads off and returns a minute later with boxes and clothing racks. "Please look through our costume and props to pick out an outfit. Once you are changed, we'll start the photo shoot!"

You start flipping the costumes down the rack, trying to determine what suits you best. On top of the box of hats, you find a note:

For this assignment, you will write an OpenGL/GLFW progrm that displays a 2D animated and interactive Hero. Make your window a traditional size (say 512x512...the same as A1, hmm). Your Hero must be made up of OpenGL primitives, at least one of which is solid, and drawn in hierarchical fashion. In other words, the eyes and mouth should be drawn with respect to the head and the head with respect to the body, etc. A carefully placed call with glm::translate() could be used to move entire portions of the Hero's body.

Your Hero must have some form of constant animation regardless of user interaction (head bobbing side to side, arms waving up and down, etc.). The user must be able to move the Hero around the screen with the keyboard and the Hero must wrap around the screen. That is, when the Hero gets to the left edge of the screen, the Hero should then reappear on the right edge of the screen. Same scenario for right-to-left, top-to-bottom, and bottom-to-top. When each of these four scenario happens, you must call the following respective functions: moveLeft() , moveRight() , moveUp() , and moveBottom() . This will take care of advancing the map for you. Make sure to keep the function call to drawMap() at the beginning of your renderScene() function, right after we load the identity matrix to the ModelView Matrix.

The Hero must also interact with the mouse (change the Hero's color, expression, fire an arrow, etc.) and the interaction must be based on the position of the mouse (the Hero runs away from the mouse, it fires an arrow at the mouse, the Hero constantly looks at the mouse, etc.). Your program must register a callback for the keyboard and mouse. As discussed in class, it is possible to combine the mouse and keyboard together for Shift + Click or similar operations.

Have fun and be creative! Don't be limited to just the suggestions above. Try out different key combinations (maybe allow the arrow keys to move your hero in addition to ASDW), make full use of the mouse, make your assignment as cool as possible! Your Hero will be added to the Hero page so if you have a particularly cool pose you'd like to use, be sure to capture that as your screenshot.

Use this source code package (NOTE: it depends on SOIL which is included for the lab machines, you'll need to set up on your own machine. If you can't get SOIL set up properly, post to Piazza and I'll tell you how to disable it.) as the starting point since it contains the necessary shell to create the world map. Additionally, download these world map images and put them into the images/ folder to populate the world map.

::click::

Cheese!

Still in your new garb, now that your picture is done, you start to walk through the rest of the park to see what other rides are in development.

Update the webpage that you submitted with A1 to include an entry for this assignment. As usual, include a screenshot (or two) and a brief description of the program, intended to showcase what your program does to people who are not familiar with the assignment.

Briefly answer the questions below. Include your response in the README.txt file.

1. Provide a series of OpenGL/glm calls that accomplish the following transformations. Assume you have a function drawHelmet() which takes care of drawing the Mines helmet to the screen.
   1. As seen in class, it is very simple to rotate an object and have it spin around its own local axis. The Mines helmet is located at (x, y). How can we rotate the helmet around the origin (0, 0) without the object spinning, but staying stationary around its own local axes? An angle of rotation θ_r is provided and updated each frame to simulate the animation. (Think back to the example from the end of class on Monday, August 28).
   2. Instead of rotating around the origin (0, 0), how can we rotate the helmet around an arbitrary point (i, j)?
   3. We have discussed the Shear transformation in class. GLM does not provide a built in glm::shear() as it does for translate, rotate, or scale. Provided an angle of shear θ_s , how can you tell OpenGL the necessary transformation matrix and apply the matrix to the drawing of the helmet? (Hint: Your answer will not require any reference to glm::translate(), glm::rotate(), or glm::scale(). )

With this and all future assignments, you are expeced to appropriately document your code. This includes writing comments in your source code - remember that your comments should explain what a piece of code is supposed to do and why; don't just re-write what the code says in plain English. Comments serve the dual purpose of explaining your code to someone unfamiliar with it and assisting in debugging. If you know what a piece of code is supposed to be doing, you can figure out where it's going awry more easily.

Proper documentation also means including a README.txt file with your submission. In your submission folder, always include a file called README.txt that lists:

• Your Name / HeroName
• Assignment Number / Project Title
• A brief, high level description of what the program is / does
• A usage section, explaining how to run the program, which keys perform which actions, etc.
• Instructions on compiling your code
• Notes about bugs, implementation details, etc. if necessary
• How long did this assignment take you?
• How much did the lab help you for this assignment? 1-10 (1 - did not help at all, 10 - this was exactly the same as the lab)
• How fun was this assignment? 1-10 (1 - discontinue this assignment, 10 - I wish I had more time to make it even better)

Your submission will be graded according to the following rubric.

[1] In other words, a call to drawHero() would be made up of calls to drawHead(), drawBody(), etc.. Within drawHead() are two calls to drawEye() to place each eye on the head. A properly placed call using glm::translate() could move the entire head (and eyes) with respect to the Hero's body. Each component should be drawn with respect to the component it is attached to (i.e. eye locations are set as offset from center of head) rather than being specified with respect to the center of the Hero. Individual components can then be moved hierarchically. If there are any questions, feel free to post a question to Piazza.

Please update your Makefile so it produces an executable with the name a2. When you are completed with the assignment, zip together your source code, Makefile, and README.txt into a folder named src/ plus include your www/ folder. Name the zip file, HeroName_A2.zip . Upload this file to Canvas under A2. The structure of your submission should look as follows:

• HeroName_A2.zip
  • src/
    • images/
      • all_images
    • README.txt
    • Makefile
    • main.cpp
    • all_additional_code
  • www/
    • images/
      • all_images
    • HeroName.html
    • all_additional_files

This assignment is due by September 8, 2017 by 11:59pm.