WEBGL|JAVASCRIPT|FINAL PROJECT 代写

COMP 4302/6909 代写

Final Project/Assignment

–

Putting it all together

COMP 4302/6909 — Assignment 4 Due: April 11, 2020 (Sunday) 11:59 PM

Assignment goals: To demonstrate the skills and knowledge you have obtained through the course by showcasing a WebGL 3D graphics application based on a theme of your choice.

Available Themes:

You can submit one the following project types as your final project for the graphics course:

•   A virtual-museum walk-through type of environment (allows for a virtual tour).
•   A one or two player game or a 3D implementation of a basic 2D arcade game (retro implementation).
•   A 3D simulation of a process that is completed in a factory style, in the type of a cinematic illustration of a process, or sequence of events, as in an animated scene.
•   A 3D system for walking through a virtual building (alternatively, a walkthrough of some part of the MUN campus), plus some interactive elements.
•   A sophisticated 3D interactive tutorial to illustrate concepts from the course (a super cool and informative demo). In case of doubt, it is advisable to check with the professor and discuss the project that you intend to do before the actual implementation to ensure it will meet the requirements and to help you assess the level of complexity of the project so that it is neither too simple nor too complex. All submissions must have the following technical features:

•   Two or more light sources must be activated to illuminate the scene.
  • –  At least one of the lights must be switchable using keyboard input.
  • –  The system must allow changing the light position and color using the keyboard.
  • –  Varying materials, colors and use of textures is expected. For example, in a museum application with several rooms an extensive use of textures is expected.
•   A system for efficient, intuitive navigation must be presented, using the lookAt() function or a matrix equivalent, using both keyboard and mouse functionality.
•   Use of textures on the models.
•   At least one part of the program, where elements are moving in a hierarchical relationship with other elements, in the form of platforms carrying other objects, a solar system, or a pair of objects rotating around each other, illustrating the use of cumulative transformations.

 A “novel component”: A graphics technique that has not been part of the previous assignments. For instance, a method that might have been described as an “advanced topic”, or something that you found interesting, such as particle systems, game AI, new shading effects, something out of the graphics research literature, such as collision detection between multiple objects, interactive model deformation, etc. An important consideration is that it must be appropriate in the sense that it does not look completely different or conceptually detached from the other elements of the assignment, but it has to be suitable to the theme you have chosen.

Evaluation scheme:

Clarity and legibility of the source code, indentation, comments & readability………….5% Complete Documentation and instructions for deployment and testing……………………10% Successful use of textures ………………………………………………………………………………………….20% User control over lighting conditions …………………………………………………………………………10% Effective interface and/or use of keyboard or mouse for navigation …………………………15% Overall degree of sophistication of the “novel component” ………………………………………5% Successful implementation of the “novel component”………………………………………………5% Appropriate integration of the “novel component”……………………………………………………5% Relative Quality and sophistication of the project ……………………………………………………..25%

Further Details:

•   The projects are to be finished individually or in groups of 2 remotely-collaborating participants (maximum).
•   A three to five page documentation of your submission is required. The description must contain:
  • –  A cover page.
  • –  The description of your implementation features and characteristics.
  • –  A user manual, which lists the ways of interaction with the program submitted, including instructions on how to use the application.
  • –  A statement of acknowledgment of sources and references where you clearly specify which parts of your code were done by you, and which parts of the code come from third-party libraries (such as libraries to load models, sounds, open source code, etc.)
  • –  At least three screenshots of your application (showing the highlights of how it should look like when being reviewed) in not more than one page.
  • –  If your project contains special features that need to be checked out by the markers, include a mention to these features along with the instructions on how to test these feature for the markers What and How to Hand in: You are handing in the source of your program, as well as any data files required for running your program. Your source code must contain sufficient internal documentation to facilitate grading. This includes your names, student numbers, a brief description of what the program does, which items you claim to have completed and a listing of known bugs, if any, at the top of the file. Send in your source program(s) through the Direct2Learn Dropbox as a single .zip file. No late submission is allowed. Documenting and referencing your sources:

To avoid potential plagiarism issues, always insert a disclaimer under a section called “Sources & References” explaining whether you adapted source code or used implementation information from any source, including the textbook’s author website. Any source that is external to your own coding must be mentioned. All the source code submitted must be understood by all members of the group and each member must be able to explain in detail his/her own part of the project if this is deemed necessary by the markers or the professor after submission.

Verifying your submission:

Since late submissions are not allowed, you should be careful to make sure each of your submissions has been properly done. Once you have placed your assignment into the Dropbox, click on the link that indicates our submission has been done, download it, open it, revise the contents, test that the program you have submitted actually is the one intended (not the source files, for example), and if it does not correspond to what you want the TA to mark, you must resubmit again, until you are satisfied, the TA will only mark the last submission with the timestamp that is prior to the indicated deadline.