Category Archives: Assignments

Assignment 2

I have finally completed marking for Assignment 2 and your marksheet has been emailed to you. Please let me know if you don’t receive it or if you have any queries.

I apologise for the time it has taken but as I am sure you are aware I have been in hospital but I have been trying to keep up with some of the great things you are creating for Assignment 3.

Hope all goes well for the rest of the semester.


Assignment Three: Final Days

Today will be the last opportunity to ask for advice or support with regards to Assignment 3. I will be inworld as usual from 3 to 5 pm to assist where needed.

With regards to completing the assignment, remember that Friday the 16th is the assignment due date. At midnight on Friday Koru will be closed off to entry and will be reopened once marking of your builds is complete. Do check through the criteria in the googledoc for Assignment 3 to ensure you have met all the requirements before the shut off.

For those producing machinima please provide access to the file before the due date/time. This file will be downloaded at midnight on Friday and considered the final product. This also applies to Unity builds. Please ensure full and straightforward access is provided to the build before the due date/time. This will also be downloaded/accessed at midnight on Friday 16th.

Please make sure that all revelent blog posts are up before the due date/time as well. Remember to include a final reflection on the project.

For my part it has been another enjoyable year on Koru. A special thank you to all who put in the effort to approach the subject in a mature and professional manner. It was appreciated.


Assignment 1

I have just finished emailing you your marksheet for assignment 1 using the email you provided on your google doc.  If you haven’t received it or have a problem accessing it, please let me know by email.

My apologies for not writing very extensive notes on your sheets but I spent most of the break still sick 😦 I will go over the assignment in class this afternoon and am happy to answer questions then.

I will also be going over Assignment 3 and what you need to do by next TUESDAY in readiness for it.

See you later

Class notes will be here later.

Evaluating a build

Today we will be looking at how to ‘look at’ and evaluate a ‘build’ and I want to spend  some time talking through some of the things that you should be looking at.   I will probably use the SLENZ Hyperdome build to illustrate what I mean.  My suggestion is that we then spend the rest of the class exploring either that build or  others of your choice and writing it up as a blog post which could either be a trial one for you or could be one of the ones that you submit for your assignment.  If you have already done your posts on ‘builds’, you might like to reassess them in the light of what we discuss and make any additions if you feel it is needed.  If you are happy they are complete then you can either work on other aspects of your assignment or take the time to practise your building skills!

What follows are some guidelines that I put together for a previous course and it would be a good idea to have a read through to remind yourself of what I am after before you start your blog post.


A critical  evaluation of something is a purposeful, reflective summary of what the thing is,  how and why it was created, who it is for, how is it used and what appear to be its strengths and weaknesses.  Of course it isn’t possible for you to know everything about a ‘build’ just by looking at it – you need to explore it, test out the functionality of it, investigate the various elements of it, such as the textures, the use of different kinds of prims, the scripting, investigate who uses it and why and provide your observations on the aesthetics and design of the build.  If it is a large build it may not be possible to look at the entire ‘build’ it may make more sense to make some overall comments and then look in detail at just a couple of aspects of it.

For your assignment  I will be expecting to see at least two such critical evaluations.

You are free to do your evaluation in whatever manner seems best to you but if you would like guidelines then I suggest that you follow the process below.

1. Write a description of the build including first impressions of it, the approach to it, the overall design and ‘look and feel’ of the place.  Don’t forget to provide information on where in SL the build is and provide a SLurl.  I would also expect to see at least two photos of it.  This description should also include details of the different parts of the build.

2. Write a description of the community that uses the build.  For example if you are looking at one of the SLENZ builds you may need to search on the internet for information about this – the SLENZ blog is a good place to start.  Imagine what it would be like to be a student in a class that used this build – how do you think it would feel?  This video may help in your understanding.

3. Write a short description of each of the following aspects of the build:

  • the shape and type of prims used (look at the complexity of shape, the size, total number of prims, use of transparent prims etc.)
  • the textures
  • interaction and scripting

4. Write up your observations of the build – how does it feel to be walking around it? do you find it aesthetically pleasing?  What aspects of the design work for you and which don’t?  Does it feel like a ‘real’ place or is it total fantasy? (Is it important to have private changing rooms for example? why do you think they were built?) Is it somewhere you would wish to spend time in or is it just for a purely functional purpose (like The Particle Lab for example?).