Pressure Project 2

When I started out this project, I was really excited to get into the storytelling and create a mystery. I went through a few different ideas including a treasure map, a secret agent entering a vault door, and turning the door into a magic mirror with an evil spirit. These were all really cool, but I was having a hard time fitting them into the required resources, so after a lot of brainstorming and trying to make things fit, I switched approaches. I looked at the resources I had and figured out the best ways to use them and then built a story around that.

The end story I ended up with was a story about an adventurer going on a journey to rescue something and the pressure project being the adventurer finally getting to where they are going and having the final boss fight.

With the makey-makey I decided to make my own controller to cast magic spells. I used the webcam to make the evil spirit more angry (symbols changing on screen more frantically) when there is more movement in front of the camera. I used a stuffed unicorn (his name is Craig) as the final treasure that you find behind the door. Since I have an interest and focus in storytelling and animation, I tried to find ways to incorporate more narrative into the built system. This resulted in three different scenes. The first scene is the ‘villains monologue’ where we are introduced to the task at hand. The second scene is where the battle and interaction mainly takes place. The third scene was the indicator of success and telling people they can now open the door and receive their prize.

I’ve come to the conclusion that I have no idea how long things take to complete. I started out this project with really grand ideas and a big vision of what I wanted and thought “This is completely reasonable and doable in a ten hour time frame!”. I was very wrong. That being said, when I realized just how long certain things were taking me, I was able to scale down my ideas considerably to get to something that was more manageable.

There are two different mindsets that I’ve had professors try to instill in me over the past two years. The first one is to work in slices. The whole thing doesn’t need to be complete, but at the deadline, that section of the thing needs to be a complete and working thing. The second mindset I’ve been referring to is to look at the software and figure out what I can do with what I have, rather than trying to fit what I have into something I want to do – working from inward as opposed to outward in. In terms of scale, I try to remind myself of these things on every project I work on. I’m more successful on some occasions than others.

Obviously, my first attempt at presenting this didn’t go as planned. Apparently, the last time I worked on my project, none of the progress I made saved, causing the initial break in the system. Then when I tried to fix it, my laptop decided it had had enough and gave out on working for the rest of the day. Over the weekend, I was able to figure out the issue with the saving, and make the changes necessary so that it should work fine when I attempt to present next.

Other than that, there was a lot of iterating in the process and trial and error in trying to get things to work. I had a vision of what I wanted to make, but I ended up exploring different nodes and trying to find realistic ways to make things. I started with a small task of making the butterflies move, and figured out how to be creative with the other spells.

I really liked getting to work with physical materials in this project. A lot of the work I do usually exists only on the computer screen, so I liked getting to play around with the makey-makey, and doing arts and crafts to make my controller. I think if I were to go back and do it again, I would focus more on finding better ways to make the experience more immersive and using my environment to my advantage.



Leave a Reply