You must write and include at least one script when implementing your scene (and you may choose to include many more). All scripts must be written in the C# language.

While the scene must be implemented in Unity, you are allowed to include assets that you have created in other software packages (e.g. 3D models that you have  created in Maya).

GUIDANCE: THE REPORT

Your report must include the following sections:

Background: Give the background to situate the rationale in creating your environment and experience. For example, your report might describe:

•    Why did you choose to create this particular environment and user experience?

•    What other environments provided inspiration for your project?

•    What is the purpose of this experience?

•    Who might it be used by?

•    In what situation is it meant to be experienced? (e.g. an art exhibition)

Description of Experience: Provide a description of a typical user’s experience of interacting with your environment (e.g. a walkthrough).

Description of Technical Implementation: This should be the largest section of the report. You must give a detailed and precise description of your technical approach for implementing your environment (e.g. lighting, sound, physics, AI).

Reflection: Discuss the success of your experience from both a user-experience and technical perspective. For example, you might reflect upon:

•    What were the challenges of creating your experience?

•    Which parts do you feel work well and which didn’t? Why did they work or not?

•    How could you develop your environment further?

You are allowed a 10% leeway either way (i.e. 250 words over or under is acceptable). This length limit excludes all appendices. Write the total word count clearly at the end of the report. Note that over- or under-writing beyond the limits of the leeway may incur mark deductions.

Use either Times New Roman in font size 12 or Arial in font size 11.

You must include a cover sheet with your report.

SUBMISSION REQUIREMENTS

Your submission must include the following components:

Note that you MUST submit a standalone build of your environment in addition to the complete Unity project. A standalone build is a file that allows your scene to be run outside of Unity. This will enable the marker to experience your environment exactly as you intended it to be. When creating your standalone build, please configure it using the “PC, Mac & Linux Standalone” option with the “Target

Platform” set to “macOS” and then “Windows” For more information on how to create a standalone build of your project, please see this pagein the Unity manual.

Please read the Very Important Points to Note for the Submission of AllAssessments (which includes important information on the appropriate time to start submission; how to check your files; what to do if there are problems with submission etc.). Please access the file with your University of York login.

USE OF EXTERNAL SOURCES AND ACADEMIC MISCONDUCT

All work submitted for assessment must be the student's own and all sources must be acknowledged and referenced, as set out in your Course Handbook and/or assessment brief, to avoid academic misconduct. Students may not submit the same work or part of the same work for assessment twice.

All sources in your report should be cited using the Harvard referencing system format. You may refer to this referencing guidefrom the University of York. For finding out the correct format for citing non-standard sources (e.g. computer games)this Harvard referencing guidefrom Anglia Ruskin University Library may also be helpful.

The scene must be your own work. If elements of the design or implementation of your scene (e.g., the concept, the layout, the gameplay mechanic, a solution to a challenging technical problem) are based upon the work of others, you should indicate this in an appropriate section of your report with references.

If you include code written by other people in the scripts submitted as part of your Unity project, you must reference this in the source by including a block comment at the top of the file describing where the code came from , e.g.:

/**

* This script is based upon a code example from the Unity Script Reference *

* Author: Unity Technologies (author name unknown)

* Accessed: 20/10/2021

* Location: https://docs.unity3d.com/ScriptReference/AudioSource.html */

Additionally, if a script includes some code that is written by you and some code that is written by others, you should include inline comments that clearly indicate which parts are your own work and which aren’t.

// I added the following three lines to set the volume based on a slider

AudioSource a = GetComponent();

Slider s = GetComponent();

a.volume = s.GetValue();

// My modification ends

COPYRIGHT and USE OF ASSETS

You may include assets (e.g. text, images, media) from existing sources in your environment as long as they are properly acknowledged in a Copyright Appendix to your report. Appendices do not count towards the word limit of the report.

In this assessment, you may use assets under the copyright ‘Illustration for

Instruction’ principle. This means that you can use any asset within this assessment as long as it is fully credited because it is only going to be viewed by a limited audience (i.e. only you and the examiners will view the application).

However, if you wish to host these applications online or use them in any

other way after the assessment (e.g. in your portfolio), then you will have to ensure you have the appropriate copyright permissions for all assets and content.

Your Copyright Appendix must adopt the format shown below:

ASSESSMENT AND FEEDBACK CRITERIA

TOTAL: