Make sure you upload your Ass 2 to your webpage in today’s lab if you have not done so already.
Task 1: Rewrite the code from last week’s lab to use variable-length arrays (lists) rather than builtin arrays.
Task 2: Allow the user to plant extra flowers by clicking on the screen.
I found a small silver palm-top computer in a black case in the class after today’s lecture. I took it up to Security in the Mathews building.
There are three components you will need to submit:
1) Storyboard of your design (due week 8, your lab session)
2) The JavaScript files for all your scripts (due Sunday 19 September 2010, 23:59)
3) A web version of your game (due week 9, your lab session, i.e. the first lab session after Sunday 19 September 2010)
This week’s lab involves experimenting with arrays.
Start with the following behaviour:
// Flowers.js
var flowerPrefab : GameObject;
var heights : float[];
var flowers : GameObject[];
function Start() {
// make as many instances of the prefab
// as there are entries in the 'heights' array
// scale each one according to the height
// store them in the flowers[] array
}
function Update() {
// Find the smallest flower and make it grow a little
}
Task 1: Complete the Start() method so that it creates multiple instances of the prefab with the specified heights. Make them stand in a line (or, if you’re more adventurous, a circle). Add the script to an empty object (lets call it the flowerbed) in the world and test it out with different values of the heights array.
Store a reference to each flower you make in the flowers array, so we can access them in Update().
Task 2: Complete the Update() method so that on each frame the whichever flower is currently smallest and make it grow a little.
To do this, you will need to use a for loop to look at all the flowers in the flowers array and check its height against the smallest you have found so far.
Test your code with different numbers of flowers. Does it work with 10? 100? 1? 0?
Assignment 1 marking is finished. You can collect your mark using
https://cgi.cse.unsw.edu.au/~give/Student/give.php
You may contact your tutor during your assigned lab session for more information in regards to the marking.
The grouping has been done for Assignment 2 and you can check it at
http://www.cse.unsw.edu.au/~cs1400/10s2/groups.html
Please make sure your grouping is exactly as you had asked.
Report any possible mistake to your tutor before Tuesday 14 September 2010.
We are marking the “assignment 1”.
When it finishes and ready to collect, it will be announced in the blog. Until then, do not try to collect your mark.
I’ve just written the final exam for the subject. It will cover your understanding of javascript and the principles of programming I have been teaching in lectures. The breakdown is as follows:
You are not expected to have perfectly memorised the syntax or the API. Pages of the Unity Script Reference will be provided for classes that are relevant to the questions you have to answer.
The exam isn’t going to be easy, but if you can understand the code from lectures and can do the lab exercises and assignments (with reference to the scripting manual) then you should be fine.
The task in this lab is to automatically generate different levels for the Breakout game written in the lecture. For each of the three layouts below, write a script which creates bricks in this arrangement.
Use two for loops to create the bricks. The outer loop should count the layers. The inner loop should count the number of bricks in each layer. You can base your code on the script I wrote in the lecture.
[Read more →]
Team registration for assignment 2 will start on Wednesday 25 Aug. The maximum number of team members is 2.
You are supposed to inform your tutor who you decided and arranged to work the ‘assignment 2’ with, during your lab session in week 6 (for Monday lab in week 7).
REMEMBER all team members have to inform the tutor at the same lab session.
REMEMBER that on-line team registration (for example by sending email) is NOT acceptable.