CMPS 160 -- Fall 2017

CMPS 160 -- Prog 4

Early if time stamp is before midnight Nov 27, 2017.
On time if time stamp is before midnight Nov 28, 2017.
Late submissions will not be accepted/graded.

Objectives:

Texture mapping

Description:

A texture image is read in and applied to the GC. Fix up any remaining issues with your earlier assignments.

Details:

Texture mappping. The requirement here is pretty straightforward. You must let the user texture map a GC with an image. There are several images available in the ../resources folder from the Matsuda/Lea book, but they are pretty low resolution. You can include one or two other images together with your submit folder for use as texture maps. Make sure that your images have power-of-two pixels in each dimension.
The easiest way to apply the texture images onto the GC is to align the vertical edge of an image with the spine curve of the GC. Different columns of the texture image are then mapped to different rotation angles of the GC.

Bonus. The new requirement of this assignment is pretty straight forward. However, you do need to fix any unresolved issues from your earlier assignments.

You have a lot of opportunity (and a bit of extra time) to implement bonus features. Here are a few that comes to mind:

    add shadows
    add reflections
    add bump mapping
    add environment mapping
    add procedural textures
    add 3D textures
    add better GC models:
	use spline representation for the spine,
	a function that describes how the radius varies along the spine,
	and non-circular cross-sections.
    add out-of-plane GC (covers full 3D space)
    others -- contact me first

Resource:

Read the examples in chapter 5 of the Matsuda-Lea book.

CONTEST!

We will run a peer-judged contest based on the extras from this program. Each of the graders will nominate their top 2-3 picks from the programs that they need to grade. These 6-9 nominees will then get a chance to give a 2-3 minute presentation of their program in the last week of class. Students get to vote for the best and next best programs. Winners will get bragging rights, recognized on the class web page for future classes, and win some token prizes. However, this has no bearing on grades.

Grading:

Rubric:

You start off with 100 points.  You earn additional credit by turning in your assignment
early and/or implementing additional features.  You lose credit for missing functionality,
incorrect results, poorly documented or formatted code, or not following instructions.

Below is a partial list:

- up to 10 points off for poor features.html file
- up to 10 points off for inadequate comments or hard-to-read code
- up to 10 points off for not following instructions
- up to 10 points off for special handling to grade your homework (usually
  because you did not check that it runs on the computers in the lab first).
- functionality points depending on importance

Make sure you:
a.  submit the right files you want us to grade,
b.  have tested your code on the browsers in the lab.
c.  follow the general instructions described in overview.html

Who graded your assignment based on your login name:
```
hugh:	a - k
cole:	l - z
```

Submission:

See course overview for instructions on what to submit and what not to submit.

Put materials in a folder named prog4 and zip it up. Submission must be done using the "submit" command from unix.ucsc.edu

submit cmps160-ap.f17 prog4 prog4.zip