Project Milestones

Creation of non-linear narrative
We had quite a few false starts during the initial brainstorming phase, creating storyboards and then scrapping them (Conceptualising Narrative Blog Entry). Our problem mainly stemmed from trying to create an interactive storyboard without first creating a model of non-linear narrative that accurately reflected the legend of the spectre. Therefore I think our the group first project milestone was creating our circular model of narrative.



Creation of interactive storyboard
Our next project milestone was developing our "murder mystery" interactive game idea and developing our interactive storyboard around this. Unfortunately I don't believe that our interactive storyboard worked as intended as we deviated from the circularity that we originally were focusing on in order to create a game that would work in a real world situation (the circular part f the game would men the player dies every time he/she plays). Nevertheless in terms of milestones in the development of this product this was very important.





(Conceptualising Narrative Blog Entry Part 2)


Paper Prototyping
(Paper Prototyping Blog Entry)
Paper Prototyping was the next major project milestone. This assured us that players understood our game, the majority understood the story and feedback in general seemed pretty good. It also pointed out some usability issue that were easy to implement in the final product.

Product Development
Our next milestone was establishing how would we develop the product, capture the action on digital video and work out who would do what. Using puppets and composting the background was a compromise on not being able to use stop motion animation because of the trouble sourcing props. This was a group decision but I was a little disappointed as I was very keen on trying out stop motion animation and spent a lot of time researching methods and downloading framegrabbers.
Developing the actual product with flash was a no brainer really, the other alternative was using html and javascript and this would have caused far more work and the end result would be no different at best.
Roles in the group established... but these were not strictly stuck too, with being such a small group we pretty much had to help each other out with everything. This did give a wide exposure to a lot of different areas of production though ad despite this mixing of roles it was useful to have leads on all major areas of production.

Film & Sound Editing
(Filming & Editing Strategy Blog Entry)
Filming the puppets in front of the green screen (green card) was relative straight fwd, not a huge amount of puppetering skill was needed, the only thing that caused a slight problem was keeping the puppets in the middle of the screen and making sure no hands were seen. Recording sound was very straightforward, we just used a dictophone accessory for an ipod. In hindsight though it would have been beneficial to use a better quality recording device as our sound quality in our final product was poor.
In terms of composting the background of the video's I was not sure how well the imovie plugin would work, but it was effective enough for our prototype, with just a small amount of distortion when the puppets move very quickly. We used audacity to balance out the sound levels of the dialogue and then inserted this into the main timeline in imovie.
We now had a set of video's all that was needed was the flash development.

Compression
Compression was completed in imovie. This was very successful in terms of size visual quality but we had some issues surrounding sound quality. Results can be seen here: Video Compression Blog Entry


Prototyped Developed - time to test
After flash development (Scripting Efficiency Blog Entry)we tested our prototype. This test highlighted some big flaws in our design and was generally not very well received (Technical Testing Blog Entry)

Reflection
For me one of the most the most important project milestones was reflecting back on the project and the product we made after the testing was done and I was writing up my reports. I think by deviating from our original intention of basing our product around our non-linear model of circularity, our product was ultimately a failure in the sense that it did not fit what the brief asked and also it did not do what we intended which was help the player learn about the the legend of the spectre.

Group Production Techniques

Although being a small group had its disadvantages in terms of work load, I think it also had its advantages when it came to organising the group. From the start of the brainstorming stage we worked together as a group and from this it was really a case of assigning roles, establishing tasks that needed to be completed at each stage and dividing the tasks accordingly. During the actual production phase these roles became slightly blurred but it essentially meant that each team member was responsible for a specific area of production whether they were working alone or with other members of the group.

We used our team blog to keep everyone up to date on what had been completed and what needed to be done. Our project manager used this to inform the team of times and locations to meet.

As we were all working with multiple video, sound and flash files so it was important that our naming convention for files was the same for the whole group. We incorporated a system where we saved each file in iterations; _1, _2 etc and put our initial at the end. This meant that we knew which was the latest version and who was responsible for it.
Asset Management Blog Entry

Software Inter-Relationships

Technically it has not been a particularly ambitious project partly as a result I think of the lack of technical know how on the team. Despite this the softwares used have done the job required and I found no major issues working between different softwares for this project. The major software packages used were imovie for video editing and compression, audacity for sound editing and photoshop and flash for creating the final product. We captured video on a panasonic mini DV and sound on a dictophone ipod accessory.
Particularly useful was imovie HD6 which although being a very lightweight video editing software, allowed us to do all the editing we required and its ability to accept plug-ins such as the composting one we used was very useful.

Flash's video import feature is very straight fwd and adjustable so importing video was hassle free. Lastly with flash and photoshop being part of the same CS3 package, integration between the two is pretty seamless. So all in all, pretty straight forward.

Debugging & Modification

As a result of the simple construction of our flash game (see earlier in blog for explanation), debugging has not been much of a problem. We did have one actionscript issue during our testing where the popup for the instructions wouldn't appear when called upon. I created this pop-up as a class in a separate as file and the code worked fine until i changed the popup movieclip with an updated one and it seemed to not recognise the new mc. Time was getting on and a simple fix for the prototype was to simply create the instructions as a separate swf that could be called upon with a button.

Product Testing

Our product test of our prototype product was reasonably successful. It highlighted some points where the narrative of our product could do with being improved upon. I felt that an issue of our testing was how the testers seemed to only want to point out technical issues. One tester in particular (a sound art student) was determined to point out that the sound quality needed to be improved. While being true, our compression had resulted in a poor quality sound and it was useful to find out that this did impact upon the usability for certain players, it was more useful for us to find out deficiencies in the interactivity and narrative of the game. This was not the testers fault, as they were not to know this but it may have been beneficial if we'd oulined this at the beginning of the test.

Scripting Efficiency & Product Optimisation

Although in terms of efficiency in both the running of the final product and the size of the final product, it would be far better to write it all in actionscript 3.0, due to time constraints and only being a small team I don't have time to play around with the new techniques that I would have to learn to complete this in the required time. Therefore I am creating quite a simple timeline based fla file in actionscript 2.0, and embedding the video in the slides that I have created in photoshop - see below for examples:




I have also created some movieclip animations to enhance the experience.
Despite this drawback in the efficiency of the product, the use of streaming video and the simple design is allowing for quite a lightweight yet smooth product.

Video Compression

Video Compression has been quite successful. I was not involved in the process my self but we have managed to get each of our 13 video clips down to between 1-5 megs each. An example of one of our clips is below: