Schematic and Schedule
Posted: November 8, 2018 Filed under: Uncategorized Leave a comment »11/1 | Laboratory for Cycle 2
Set up other computer. Intro to WiMote. Try regular (not short throw) projector. Weekend: Make patching with WiMote. Buy and prepare materials for hanging the window.
|
11/6 | Presentation of ideation and current state of Prototypes
Try patches with window, Hang window bars, Map projections
|
11/8 | Laboratory for Cycle 2
Figure out dimensions in final cut for projections to land on window locations. Continue figuring out WiMote/mapping projections as necessary Weekend: Edit video (maybe shoot more?) and set them up in patches.
|
11/13 | Last second problem solving
Continue figuring out WiMote/mapping projection as necessary |
11/15 | Cycle 2 Performance |
11/20 | Critique
|
11/22 | TURKEY TIME |
11/27 | Laboratory for Final Cycle
Figure out how the computers communicate (if necessary for Makey Makey signals to reach patches) |
11/29 | Rehearsal of public performance
Set up Makey Makey with wires for window hangers. Program Triggers with Makey Makey |
12/4 | Last second problem solving
|
12/6th or 7th | Student Choice:
Public Performance at Class Time or Final Time |
12/? |
Official final time: Friday Dec 7 4:00pm-5:45pm
|
Pressure Project 2
Posted: November 8, 2018 Filed under: Uncategorized Leave a comment »PP2 was to create an interactive fortune teller in 9 hours. Similar to last time I challenged myself to completely begin and end the the process within that nine hour limit (this includes the brainstorming phase). Unlike the first pressure project, I went a route I assumed would be a(n attainable) challenge but instead realized the error of this assumption.
My original idea was to use a program called Max- a visual programming language for music and multimedia developed and maintained by San Francisco-based software company Cycling ’74. The program is similar to Isadora, but I was more familiar with how to use it and various sensors. I wanted to try to create a “fortune teller” that could use some sort of sensor to tell your fortune.
When I had spent too much time trying to figure out Max, I decided to turn to the Arduino, which I was familiar with and thought could work to create a physical fortune teller machine, similar to the 20 questions little game I had as a child. I also knew that Arduino’s have tons of tutorials and help guides that might be able to assist in case I got stuck. It also helped that I had all the equipment from a previous class to get started (working by the light of a laptop):
My plan seemed straightforward: use an lcd screen to display questions to a user. Two small buttons would correspond to Yes and No answers to these questions. The order in which a user answers would after a few questions generate a custom fortune. I began by wiring my arduino and led screen, using using a helpful code and preset sketch. This part was a success!
Next, I attempted to modify a few codes online, one being a simple fortune teller and the other being a code that have various forms of “if this order of yes and no answers (ex: yes no no no yes) then do this (in my case read fortune).
This is where I ran into issues. When I put in a code, Text no longer showed up on the screen and my led stopped turning on. Then, my led light stopped completely. Then when I tried to get the box made so it would be held in something nice, I dropped the Arduino and messed up where the wired had been.
Then I ran out of time.
PP3 – Puzzle Game
Posted: November 8, 2018 Filed under: Pressure Project 3 Leave a comment »For Pressure Project 3, I decided to create a game reminiscent of games like The Talos Principle and The Stanley Parable. These games are unique in that they explore themes of determinism and freewill, and the ending you receive is based on how you perform in light of the choices you make in the game. Certain choices made following the instruction of the narrator/narration will lead you to a somewhat lesser ending than one of disobedience and self-determination. The links below highlight the endings of the games where these themes are evident.
Talos Principle: https://www.youtube.com/watch?v=g5FloMq9Lck
https://www.youtube.com/watch?v=-mNa2csiD8E
Stanley Parable: https://www.youtube.com/watch?v=w3UxRa_-9UU
Given the time constraint, I decided to make a game with the puzzle goal of unlocking when the user successfully correlates actions, but only executes their own commands.
User Inputs would include a gamepad controller and a Kinect interface, and users would input a corresponding button on the controller or move in a corresponding way in space.
🡸 🡺 🡹 🡻 A (Jump) B (Crouch)
Participants would move in a grid space made up in Isadora with data from the Kinect to complete the physical inputs. In the first phase, only the game pad would be used. In the second, only physical movement. In the final phase, both would be used. Thematically, there would be psychology/philosophy quotes about choice between phases, some which would suggest a means of escape/winning. In the final phase, you would unlock the real ending if you made valid unprompted choices.
The game wasn’t completed because I lost the save at one point when I was trying to get the Kinect stream working. SAVE EARLY, SAVE OFTEN. At time of performance, game included the first phase only. It also broke.
Here’s a user actor example on how to make a non-repeating random number string generator. Change length or modulo number for different results. This was used to generate the pattern of inputs that the user had to input.
PP2 – Fortune Teller
Posted: November 8, 2018 Filed under: Pressure Project 2 Leave a comment »
My project was to make a fortune telling interface, styled as the Greek/Roman Oracle of Delphi. In its operation it was to detect the input of the user through text or audio, determine what what said, and meaningfully respond to the contextual and emotional charge of the user dialog. I was very much unable to finish, and I think this is as a result of trying too many foreign concepts in this project combined with a 9 hour time limit.
Did start a good discussion in class regarding AI/machine generated response. Due to the nature of the application, it leads to an ethical discussion on how or in what ways we should be (or not at all be) manipulating the experience/emotional states of the participant.
Although, I am familiar with all of the technology and techniques in my plan for the project, I have never directly implemented a few like: language processing, Audio binary, TCP/IP requests (I recommend NEVER doing this by hand, use a wrapper class), Google Cloud, etc. Led me to think about the ways in which I consider what skills I do and do not have a mastery of, and how to construct this knowledge of each into a full project. For instance, I would definitely consider some of the aspects of this project to be outside my comfort zone now. Ideally for a new project, I should be using skills I already have, save for 1 or 2 new concepts only.
Google CPS: https://cloud.google.com/docs/overview/cloud-platform-services
Chatbot Applications: https://www.wordstream.com/blog/ws/2017/10/04/chatbots
Historical Inspiration for Styling: https://www.coastal.edu/intranet/ashes2art/delphi2/misc-essays/oracle_of_delphi.html
Final Schematic
Posted: November 6, 2018 Filed under: Final Project Leave a comment »My schematic for the final project is in the link.
Final Proposed Planning
Posted: November 6, 2018 Filed under: Final Project Leave a comment »Proposed Planning
11/8 – Work in Drake
11/13 – Work in ACCAD
11/15 – Work in Motion Lab 4-5:20pm
11/20 – Projector Hang/Focus – Critique
11/27 – Determined by outcome of 11/20 – Work in Motion Lab
11/29 – Split Motion Lab time
12/4 – Last Minute Problem Solving
12/6 or 12/7 Perform Final TBD
Pressure Project 3
Posted: November 6, 2018 Filed under: Pressure Project 3 Leave a comment »For Pressure Project 3 I decided to bring in some of my childhood enjoyments to this project. Knowing that I had to have a project that did not involve the keyboard yet had some level of technology involved I had to figure out what to do. I remember enjoying decoding things and figuring out puzzles. The technology that was involved was the Makey Makey and using a website called Scratch. The experience was where someone was to receive a piece of paper. On the paper you had four pictures with a piece of duct tape on top and three dashes below the pictures. There were two tables. One table had a group of red cups that were turned over. The other table had a computer and a Ritz cracker box with silver items protruding up from the inside of the box. When someone received their paper, they were to use the color of the duct tape at the top of the paper to correspond with the color duct tape on the cup that had a letter written on it. Then using those cups, they then had it narrowed down to a smaller number of letter choices. Then looking at the pictures they had to figure out the word and the three dashes let them know that it was a three-letter word. Once they figured out the word they were to figure out that you had to turn the cup right side up to reveal a number inside the cup. Then using the numbers, they were to go to the computer and Ritz box. On the Ritz box there were ten silver protruding sets of foil. There were three rows of three foils and one foil in the center bottom that had the message hold me written around it. The experiencer then was to hold the tenth foil and then touch the other ones in order of the numbers. Once the code was cracked they heard a cheering noise from the computer. There was also a message for the user to click the green flag when they heard their noise.
It seemed that everyone was enjoying the experience. One person said they enjoyed the tactile experience of the this project. It became one big group event and they even asked for more clues when they finished one. They eventually tried to find how to break the experience or to find out if there were any underlying similarities from the clues. They eventually found out that to make the cheering sound you had to hold the one silver prong and enter two numbers followed by the nine. If I was to do this again, I would work more triggers to where there were different sounds for series of numbers and for every last digit that was different, there was a different sound or a random sound.
As I was trying to determine how to put together this pressure project I did some research into other ideas. I ran across a video on how to use the Makey Makey and a book about different projects called 20 Makey Makey Projects for the Evil Genius. There are a lot of projects in the book that I would like to make happen yet I needed to narrow down to this specific project. The project I used was the lock box project. I did some tweaking from what the book has to make it my own. Overall, I feel that this was a successful project.
Pressure Project 3
Posted: November 4, 2018 Filed under: Uncategorized Leave a comment »Our third pressure project included these guidelines:
-Create a 3 minute experience
-user must touch something apart from the keyboard and receive a response
-Must include sound
-User must move in a large environment and a hidden mystery must be revealed
Though I tried to meet all guidelines, I based my experience off of the guidelines “user must touch something apart from the keyboard and receive a response” and “User must move in a large environment”. I wanted to encourage a physicality and adrenaline in the user experience. Inspired by simple video games, I created a game in which the user walked on a path made of aluminum foil and attempted to tag bananas to earn points.
The objectives of the game were as follows: Keep contact with the path, touch all bananas, beat the clock! Level 2 included the user performing these tasks backwards.
I intentionally placed the bananas far from the designated path so the user would have to stretch and reach to earn the points. Additionally, I included an element of time so that the user would have a sense of urgency in his or her movement. I was very curious about the human embodiment of a game that was inspired by a 2-D experience I played as a child.
As a whole, the experience was a fun time for everyone involved. I enjoyed watching the users try and beat the tasks and I think the users had a fun time playing the ridiculous game. My colleagues explained that this experience felt most like a game and that they felt a strong urgency to win.
Though it was a fun time for everyone involved, difficulties definitely arose in the system set-up(see video footage below). The path kept detaching from the floor and caused users to have to start over for no reason. Looking back on it, I should have taped the path to the floor so it wouldn’t move around as much. I practiced the game on carpet and didn’t take in to account the environment in which we would be playing it.
I really enjoyed this project and it definitely inspired certain elements of my final project game I am constructing!
Pressure Project 3
Posted: October 26, 2018 Filed under: Pressure Project 3 Leave a comment »For this project, I really enjoyed the class’ take on a fortune teller in the last pressure project, and a few people’s reminded me of the old chose your own adventure books I used to read when I was younger. One thing I remember is being able to skip ahead a lot and would avoid pages if I saw them while turning through, so I wanted to make something like that but where you couldn’t cheat. I thought that QR codes would be an interesting idea to tell this story, so I wrote out a whole choose your own adventure centered around a murder mystery. From each segment that went on each page, it ended up being a unique QR code that the user can scan to read that section of the story. I pasted the corresponding QR codes to their respective pages on a book that I had. To generate the Qr codes, I just pasted text into (@Laura) this website which generated the corresponding png.
Watching the class interact with my project was so much fun because everyone was very divided on which path to take and it ultimately lead to a democratic vote to which path to take. I think it really helped that the narrator was Alex for this story, his narration really gave life to my adventure. I just wish that my speaker was working; I wanted to have some background music for ambiance.
If you’d like to go through the story in segments, use the attached zip file to read the story using the QR codes. If you’d like to just read it straight up, use the script.md
file attached.