This past week I spent my time getting the last of OSC implemented into our project. To start, I cleaned up the code required to control one of our game players in Unity using our infra red tracking code. My next task was to find a way to get two player control into the game.
Since the PS3EYE has a limited width and height, it was decided this would best be done using a second camera, meaning the application would need to be run twice on two separate computers. This also means each character in the Unity project needs to listen to a separate port for it's controls. I was able to set up the control for both characters using different ports, and even tested controlling the code from a second computer.
The last thing things required for me will be to test are IR lights and how well they work in the area of our installations final set up location, adjusting all the move sets to match with the code once created, and lastly, adjusting the dead zones on the cameras to allow for more player freedom based on some user testing.
Friday, 7 April 2017
Milestone 10 - Erin
Overview - What features and tasks did you work on this past week?
This week I worked on creating different animation states for our characters. I did this using Adobe Illustrator.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
For whatever reason, once in a while when I tried to copy a character in order to deform it for an animation, a couple pieces of it wouldn't go with it, and I didn't notice until I'd already submitted it to my group members. Plus, I tried to bring a cc file into cs6, which resulted in me doing the entire piece of work I'd done over again. Next time I would just double check that I'd selected all the correct pieces I need, and I wouldn't work on Adobe cc.
Successes - What did go well? What approach(es) did you take?
The animation states ended up looking very nice. I did this by spacing out their movements a small amount at a time.
This week I worked on creating different animation states for our characters. I did this using Adobe Illustrator.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
For whatever reason, once in a while when I tried to copy a character in order to deform it for an animation, a couple pieces of it wouldn't go with it, and I didn't notice until I'd already submitted it to my group members. Plus, I tried to bring a cc file into cs6, which resulted in me doing the entire piece of work I'd done over again. Next time I would just double check that I'd selected all the correct pieces I need, and I wouldn't work on Adobe cc.
Successes - What did go well? What approach(es) did you take?
The animation states ended up looking very nice. I did this by spacing out their movements a small amount at a time.
Thursday, 6 April 2017
Ayan-Sprint 10
Ayan Abdalla
Sprint 10
![]() |
| Flashlight and Unity Game |
This week has been extremely productive for your team. We were finally able to get the OSC working.We got a lot of things done in the unity side. We successfully added two players have their movements , collision and health bar. There is still lot of polishing and finishing touches that we have to do this weekend.We need to test out the game with some users. We still need to polish the health bar.We need to come up with some type of reaction( flash of color on the screen, or a different hit noise) so the user understands that they're hitting the other player rather than the falling enemies. I worked on the collision and health bar.
I realize the importance of communication and teamwork through this project .I think if we had better communication with each other. We could gone through a smoother progress of getting our final product. It could have been way more easier. I do believe we organize ourselves well with project management tools like Slack, Trello, and Google Drive. We should have been updating each other on our progress. We definitely improve our communication throughout the project. I think everyone in our group work hard on achieving the end product. Also I believe that we could not have completed our project without all of our unity efforts.
Thursday, 30 March 2017
Erin - Milestone 9
Overview - What features and tasks did you work on this past week?
This past week I worked on implementing OSC into Unity. Nicole managed to get the sender side of the project working, sending different types of cases depending on what area of the screen the ir tacker was in, while I tried to implement it into the Unity side.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
There were a lot of failures this week. The main issue being the conversion between the js files we found to use for the OSC implementation, and the C# files of our own. I spent a lot of time trying to figure out the best way to implement the changes in cases in osc. I started by attempting to simulate keystates within Unity, as they were already implemented with our characters. After finding that this would be a lot of unnecessary work, I implemented a bool statement to set the states of each movement and tried to call them in the cases. But going between js and c#, we found that it interrupted the bool states and changed them so they wouldn't work. So finding that this was failing, I implement a state change by setting an int state, then setting state to equal different values for different cases. But this again came up with an error that I couldn't debug, so I decided to go back to the bool states and see if I could make that work.
With assistance from a peer, we decided to try to change the js code to c# so we'd be able to easily go between the two scripts. We used this and worked on it for a while, implementing the ir tracking into the unity project. We worked on this until Nicole managed to make progress with the original js code, from which I worked on in order to progress towards our final goal.
I learned that transferring data from one scripting language to another is very difficult, and that I still do not understand it. I plan to continue working on this as this will continue to be a problem with our current project, and plan to approach it by asking for more help and doing more research.
Successes - What did go well? What approach(es) did you take?
Not a lot went well this week. We ended up with an almost working code which is great, and we got there by working together to implement research and tutorials into the code we'd created. There are bad weeks and good weeks for progress. This week was good for progress towards our goal. Not as much progress as we want, but progress is still progress. Unfortunately I don't have a lot to show for it since our progress involved a lot of backtracking, but I'm glad we managed to make some improvements.
This past week I worked on implementing OSC into Unity. Nicole managed to get the sender side of the project working, sending different types of cases depending on what area of the screen the ir tacker was in, while I tried to implement it into the Unity side.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
There were a lot of failures this week. The main issue being the conversion between the js files we found to use for the OSC implementation, and the C# files of our own. I spent a lot of time trying to figure out the best way to implement the changes in cases in osc. I started by attempting to simulate keystates within Unity, as they were already implemented with our characters. After finding that this would be a lot of unnecessary work, I implemented a bool statement to set the states of each movement and tried to call them in the cases. But going between js and c#, we found that it interrupted the bool states and changed them so they wouldn't work. So finding that this was failing, I implement a state change by setting an int state, then setting state to equal different values for different cases. But this again came up with an error that I couldn't debug, so I decided to go back to the bool states and see if I could make that work.
With assistance from a peer, we decided to try to change the js code to c# so we'd be able to easily go between the two scripts. We used this and worked on it for a while, implementing the ir tracking into the unity project. We worked on this until Nicole managed to make progress with the original js code, from which I worked on in order to progress towards our final goal.
I learned that transferring data from one scripting language to another is very difficult, and that I still do not understand it. I plan to continue working on this as this will continue to be a problem with our current project, and plan to approach it by asking for more help and doing more research.
Successes - What did go well? What approach(es) did you take?
Not a lot went well this week. We ended up with an almost working code which is great, and we got there by working together to implement research and tutorials into the code we'd created. There are bad weeks and good weeks for progress. This week was good for progress towards our goal. Not as much progress as we want, but progress is still progress. Unfortunately I don't have a lot to show for it since our progress involved a lot of backtracking, but I'm glad we managed to make some improvements.
Ayan-Post 9
Sprint 9- Ayan
Starface Studios as a collective, we have all contributed time in trying to get OSC connection. We spent a lot of the trying different possible.We have come to a major block. We have receiver that has both C and JavaScript scripts. It will not receive data from the different languages.
Marie and I focus on the connection in the sprint. So unfortunately, very little was done of the Unity side. We have discussed as a group how we will proceed. We must get the connection working by the end of the weekend. I have add background music and in currently lower the opacity of the player once it get to small to show the ghost state. I learned a lot of about importance of Game Object. The biggest issue I had implementing music was due to fact that I didn't connect to a Game Object. I was such a silly mistake but reinforce the importance on the connect of the assets to the game. The background music was Dollhouse by Melanie Martinez. We like how it was upbeat but slightly creep beat.
I honestly I feel like we should give up with camera and switch to a Kinect. We have a Kinect and we aren't using it. I feel like we have waste such valuable time doing the most difficult method to achieve our goal for no reason.
Milestone 9 - Nicole
Overview:
This week I got OSC implemented in our OpenFrameworks project, and managed to get it sending proper protocol information to a Unity test project.
What went well:
Once I figured out what I had done wrong with my OpenFrameworks add ons, I was able to add in proper variables to be sent via OFC. I was able to read the information being sent out via OSCulator as well as OSC Data Monitor, two programs used to monitor the information being sent via OFC. I then was able to read the data in Unity via the Console log and use it to apply a rotation effect to my test cube:
We were also able to, after this, incorporate the OSC controls into our main Unity file, and print information to the console.
What didn't go as well:
We have yet to be able to get the variables sent into the Unity code to affect the animations in the other scripts. This will be our main challenge this week before we can tweak the remaining code.
This week I got OSC implemented in our OpenFrameworks project, and managed to get it sending proper protocol information to a Unity test project.
What went well:
Once I figured out what I had done wrong with my OpenFrameworks add ons, I was able to add in proper variables to be sent via OFC. I was able to read the information being sent out via OSCulator as well as OSC Data Monitor, two programs used to monitor the information being sent via OFC. I then was able to read the data in Unity via the Console log and use it to apply a rotation effect to my test cube:
We were also able to, after this, incorporate the OSC controls into our main Unity file, and print information to the console.
What didn't go as well:
We have yet to be able to get the variables sent into the Unity code to affect the animations in the other scripts. This will be our main challenge this week before we can tweak the remaining code.
Friday, 24 March 2017
Nicole - Milestone 8
Overview:
This week I worked with Erin in order to implement OSC between our two project files. This required a lot of research into an add on for Unity that would allow for OSC to be used to control it's contents. In the end, we decided on the following tutorial and accompanying video:
https://github.com/heaversm/unity-osc-receiver
https://vimeo.com/95584442
What went well:
The implementation on the Unity side is, in theory, very good, as the OSC code should be able to send an updated signal whenever the tracked variable for movement changes states (for example, if we set the action variable to 1 when the player lifts the pillow up and 2 when the pillow is down, OSC should be able to track it.)
What didn't go as well:
In the end, I have been struggling to get the Xcode project file to be found by OSC, either from some base misunderstanding of OSC itself, the code I require, the ports or simply the program I am using. As such, we have been unable to test our results this week and can only rely on our theoretical knowledge in this case. Since the deadline for the final project is approaching, we have begun to plan for a scenario in which we are unable to get OSC working as well, and can move our code implementation to a different camera such as a Kinect we have acquired. This would be a last resort in the case that the OSC code is simply not functional in the slightest.
This week I worked with Erin in order to implement OSC between our two project files. This required a lot of research into an add on for Unity that would allow for OSC to be used to control it's contents. In the end, we decided on the following tutorial and accompanying video:
https://github.com/heaversm/unity-osc-receiver
https://vimeo.com/95584442
What went well:
The implementation on the Unity side is, in theory, very good, as the OSC code should be able to send an updated signal whenever the tracked variable for movement changes states (for example, if we set the action variable to 1 when the player lifts the pillow up and 2 when the pillow is down, OSC should be able to track it.)
What didn't go as well:
In the end, I have been struggling to get the Xcode project file to be found by OSC, either from some base misunderstanding of OSC itself, the code I require, the ports or simply the program I am using. As such, we have been unable to test our results this week and can only rely on our theoretical knowledge in this case. Since the deadline for the final project is approaching, we have begun to plan for a scenario in which we are unable to get OSC working as well, and can move our code implementation to a different camera such as a Kinect we have acquired. This would be a last resort in the case that the OSC code is simply not functional in the slightest.
Thursday, 23 March 2017
Ayan - Sprint 8
Ayan Abdalla
Sprint 8
This is sprint, I was able to finished:
- Get the score to print
- Get the player to increase when it has successful hit an enemy
- Get the player to decrease when the enemy leave the screen without being hit
** I will be changing so that it only decrease when the player hit another player. I just wanted to make sure I would be able to implement easier for the next sprint. Because I found that it currently disorienting because the enemy is decreasing once it leave the screen.
Marie and I had implement a fluff animation to appear when the player hit an enemy. This is sprint was pretty successful on the Unity side. Next, we will have to add a secondary player, more enemy, and a health bar.
Erin Vincent - Milestone 8
Overview - What features and tasks did you work on this past week?
This week I worked with Nicole on implementing OSC into our current version of Pillow Fright. This involved a lot of research, learning, and trial and error. Using an opensource code from GitHub (https://github.com/heaversm/unity-osc-receiver) and watching the connected tutorial (https://vimeo.com/95584442), I started to understand how to implement OSC into Unity. So using this code and what I had learned from the tutorial and other online resources, I began to connect the OSC receiver to Unity. Currently, in theory, when sent the case message the Receiver should send "keyPressed" prompts to the Unity file (http://answers.unity3d.com/questions/28473/simulating-key-presses.html), which will make our character interact with its enemies.
In the future I plan to work on testing the code and working with Nicole on setting up the Sender side of the OSC aspect of the project. This way we will be able to tell if the code actually works.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
What did not work out as planned was attempting to use a non-local remote IP with the OSC application. In order to test the code, it requires a sender. And because the sender code is not yet completely ready I had hoped to try to use it with a remote Sender application on my cellphone. But the applications require the OSC to access a remote IP, which I was unable to set up on the computer at Carleton University (because of the installation restrictions). This code would in theory work locally, but again with the installation restrictions I was unable to test it.
Next time I will be working with Nicole directly, so she will be able to test the code locally anyways. If this is not an option for whatever unknown circumstance, I will have to install the correct software on a personal computer or an Algonquin College computer.
Successes - What did go well? What approach(es) did you take?
What went well was following along with the tutorial and making notes along the way in order to generate a better understanding and a future reference of how to use the GitHub code and how to use it with our project. These notes include:
OSC
Port(outgoing) = 8000 - touchOSC sends messages out on port 8000
Port(Incoming) = 9000 = recieves them on port 9000
Unity will be listening on port 8000 for incoming instructions
For MAC, can use OSCulator to route and convert into the programs you need. can use to see the messages
--Have it listen to channel 8000
Remote IP - address for local host, messages transfered over local ip address
Script object - attached all scripts
private var yRot - changed/incremented whenever the button is pushed
-this is probably what we need to change in order to casue the animations
Update - runs every few frames within unity
-var go - goes and finds the game object (in example, the cube. )
-transfor, rotate around the y axis a certain number of degrees
- every time the button is hit, it increments a certain number of degrees
All message handler - takes any osc message in and decides what to do with it
-var msgstring - takes the entire message and keeps track of it
-message address - breaks that message down just into the variable being sent (in his example, its
-message value - whatever your osc sender is set up to send
-in code, its an on and off switch, off=0, on=1. 1 is the degree we're going to use to "rotate the cube"
-debug prints out the message string
-his message import = /1/push7 1
-assume "7" is the button number, "1" is the on state
switch (msgAddress): for any message that comes in, do these things by default. In the case of the tutorial, default is to Rotate(msgValue)
switch (msgAddress):{
case '/1/push7": //1 being the button on state, and 7 being the button pushed
var rotateVal = msgValue*10 //makes spin 10 times as fast
Rotate(rotateVal);
break;
use cases to seperate movements for different "buttons"
Can call separate functions to perform the functions instead. Eg/ public function NAME(msgValue):void{rotate=msgValue}
What else went well was referencing the Unity forums in order to get a general idea of how to implement the GitHub code into our code.
This week I worked with Nicole on implementing OSC into our current version of Pillow Fright. This involved a lot of research, learning, and trial and error. Using an opensource code from GitHub (https://github.com/heaversm/unity-osc-receiver) and watching the connected tutorial (https://vimeo.com/95584442), I started to understand how to implement OSC into Unity. So using this code and what I had learned from the tutorial and other online resources, I began to connect the OSC receiver to Unity. Currently, in theory, when sent the case message the Receiver should send "keyPressed" prompts to the Unity file (http://answers.unity3d.com/questions/28473/simulating-key-presses.html), which will make our character interact with its enemies.
In the future I plan to work on testing the code and working with Nicole on setting up the Sender side of the OSC aspect of the project. This way we will be able to tell if the code actually works.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
What did not work out as planned was attempting to use a non-local remote IP with the OSC application. In order to test the code, it requires a sender. And because the sender code is not yet completely ready I had hoped to try to use it with a remote Sender application on my cellphone. But the applications require the OSC to access a remote IP, which I was unable to set up on the computer at Carleton University (because of the installation restrictions). This code would in theory work locally, but again with the installation restrictions I was unable to test it.
Next time I will be working with Nicole directly, so she will be able to test the code locally anyways. If this is not an option for whatever unknown circumstance, I will have to install the correct software on a personal computer or an Algonquin College computer.
Successes - What did go well? What approach(es) did you take?
What went well was following along with the tutorial and making notes along the way in order to generate a better understanding and a future reference of how to use the GitHub code and how to use it with our project. These notes include:
Port(outgoing) = 8000 - touchOSC sends messages out on port 8000
Port(Incoming) = 9000 = recieves them on port 9000
Unity will be listening on port 8000 for incoming instructions
For MAC, can use OSCulator to route and convert into the programs you need. can use to see the messages
--Have it listen to channel 8000
Remote IP - address for local host, messages transfered over local ip address
Script object - attached all scripts
private var yRot - changed/incremented whenever the button is pushed
-this is probably what we need to change in order to casue the animations
Update - runs every few frames within unity
-var go - goes and finds the game object (in example, the cube. )
-transfor, rotate around the y axis a certain number of degrees
- every time the button is hit, it increments a certain number of degrees
All message handler - takes any osc message in and decides what to do with it
-var msgstring - takes the entire message and keeps track of it
-message address - breaks that message down just into the variable being sent (in his example, its
-message value - whatever your osc sender is set up to send
-in code, its an on and off switch, off=0, on=1. 1 is the degree we're going to use to "rotate the cube"
-debug prints out the message string
-his message import = /1/push7 1
-assume "7" is the button number, "1" is the on state
switch (msgAddress): for any message that comes in, do these things by default. In the case of the tutorial, default is to Rotate(msgValue)
switch (msgAddress):{
case '/1/push7": //1 being the button on state, and 7 being the button pushed
var rotateVal = msgValue*10 //makes spin 10 times as fast
Rotate(rotateVal);
break;
use cases to seperate movements for different "buttons"
Can call separate functions to perform the functions instead. Eg/ public function NAME(msgValue):void{rotate=msgValue}
What else went well was referencing the Unity forums in order to get a general idea of how to implement the GitHub code into our code.
Thursday, 9 March 2017
Ayan- Milestone 6


The IR light finally come in! It arrived on Monday. I purchased from PCBoard. The website is selling educational electronics, LEDs, DIY electronics. The flood IR light had need to be hooked to an Arduino board to operate. Luckily, Marie has an aurdino. We have all of the material to complete your game.
This week I worked with Marie in completing the movement the character. I coded the movement with the keyboard with animation that Marie had created. Unity has a lot of the tutorial and forums. I didn't have difficult with figuring on how to create movement through keyboard inputs.
This week we discussed our progression and the final product. We have not been as productive as we should be. There has been many reasons like other classes/assignments or the lack of the necessary material. With the beta presentation approaching, we have discussed the tasks that need to be completed in order to be successful.
Milestone 6 - Erin
Overview - What features and tasks did you work on this past week?
This week I worked on looking at the animation process using Unity, and creating collision scripts. I also worked on the movement of the enemy, getting it to move fluidly on and off the screen.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
I found that often approaching using Unity and scripting in unity was difficult, as I often try to use Unity the same way as I would use C++. Confusing these often ends up in the script not working, and having to do more research. Next time I will look up more information about collision creation before I continue working on the collisions.
Successes - What did go well? What approach(es) did you take?
This week I worked on looking at the animation process using Unity, and creating collision scripts. I also worked on the movement of the enemy, getting it to move fluidly on and off the screen.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
I found that often approaching using Unity and scripting in unity was difficult, as I often try to use Unity the same way as I would use C++. Confusing these often ends up in the script not working, and having to do more research. Next time I will look up more information about collision creation before I continue working on the collisions.
Successes - What did go well? What approach(es) did you take?
I managed to get the enemy to move on and off the screen successfully, and I am making progress implementing collisions. I find that by approaching my peers who have a wider knowledge of Unity than I helps, along with consulting online resources.
Thursday, 2 March 2017
Milestone 5 - Erin
Overview - What features and tasks did you work on this past week?
This week I continued working on trying to edit the Unity environment to incorporate enemies and their movement. The enemy is currently moving between two places very quickly and rotating,. It is intended to eventually bounce off the walls of the application.
I also started working on incorporating animation states into Unity. Marie created some basic animations and I have been working on learning how to animate using Unity and incorporating said animations into the game. While the tracking of the movements is still in progress, I will be testing using key press states.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
I found that trying to incorporate previously separated sprites into Unity for the animation states took a lot more time than using the incorporated tool intended to separate the images on a sprite sheet. I would've known this if I finished my research before I started trying to start the animation process.
I am having a lot of issues trying to get the enemies to bounce off the walls. I hope to achieve doing this by asking my peers for help and referencing more online resources.
I also started incorporating Box Colliders, which may help with the finishing of the movement of the enemies.
Successes - What did go well? What approach(es) did you take?
This week I continued working on trying to edit the Unity environment to incorporate enemies and their movement. The enemy is currently moving between two places very quickly and rotating,. It is intended to eventually bounce off the walls of the application.
I also started working on incorporating animation states into Unity. Marie created some basic animations and I have been working on learning how to animate using Unity and incorporating said animations into the game. While the tracking of the movements is still in progress, I will be testing using key press states.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
I found that trying to incorporate previously separated sprites into Unity for the animation states took a lot more time than using the incorporated tool intended to separate the images on a sprite sheet. I would've known this if I finished my research before I started trying to start the animation process.
I am having a lot of issues trying to get the enemies to bounce off the walls. I hope to achieve doing this by asking my peers for help and referencing more online resources.
I also started incorporating Box Colliders, which may help with the finishing of the movement of the enemies.
Successes - What did go well? What approach(es) did you take?
I found that by doing research online and looking to tutorials for assistance I was able to make progress with the animation of the character and the movement of the enemies.
For example, I referenced this tutorial to assist with the start of the animation of the character: https://www.youtube.com/watch?v=O_0gZuqW6y8.
Ayan -Sprint 5
This week I finally resolved the issue that I had with finding a light source. After a lot of searching and guidance from James and Anthony purchased an infrared flood light from PC light on Wednesday. I made sure that the express shipping it should be coming in 2 -3 business day. I started to plan out the background music with one of my friend Justin. He said that he could make some basic beat that are childish but creepy to fit your theme. The week I was able to discussed my idea about UI design with the group and come up with a solution :
- We decided that the intuitive design so we don' t provide the instruction.
- We will have message " Lift the pillow to start" in background if there is no player playing.
- If a player already playing then the message appear in the background stated " Lift the pillow to add a new player" .
- In term of the condo hits, we will be sound and effect to display it. We want to take impression from SSX Tricky and fight games.
- If a player already playing then the message appear in the background stated " Lift the pillow to add a new player" .
- In term of the condo hits, we will be sound and effect to display it. We want to take impression from SSX Tricky and fight games.
Milestone 5 - Nicole
This week I focused on refining the PS3EYE IR readings. It was however, very difficult without the use of a proper reflective material or light source. After working to find a good way to bridge the colour blob detection in with the IR reflection, we have debated switching cameras to the Knex camera instead, in order to handle both color and IR on the same device.
Friday, 17 February 2017
Milestone 4 - Erin
Overview - What features and tasks did you work on this past week?
Throughout this past week, I worked with my group members on researching hitboxes, and UI planning.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
Due to the heavy workload of the week, I did not plan my time out as well as I should. I worked with my group members, but not as much as I could have if I'd planned my time accordingly. Being able to discuss ideas with the group would have been very helpful to the tasks.
Successes - What did go well? What approach(es) did you take?
I found that doing online research helped to proceed with the tasks.
Throughout this past week, I worked with my group members on researching hitboxes, and UI planning.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
Due to the heavy workload of the week, I did not plan my time out as well as I should. I worked with my group members, but not as much as I could have if I'd planned my time accordingly. Being able to discuss ideas with the group would have been very helpful to the tasks.
Successes - What did go well? What approach(es) did you take?
I found that doing online research helped to proceed with the tasks.
Thursday, 16 February 2017
Ayan
Milestone #4

I got the reflective material this week.I had ordered the IR light on Amazon on Feb 2. I got confirmation email where it said it would within 1-2 weeks. Last week I emailed Amazon because when I looked at my order information it said it would come March 2- March 23. I realize that Amazon response went to my junk mail. They essentially said that they contacted the seller and that the information was wrong that they had initially sent me and apologize . They just said that once I get the package I can get a full return if I just send it back. So the seller didn't provide tracking so they said that they don't know necessarily where the light is. They just know that the product was shipped. I have big dilemma. I need to find a light source ASAP. I've looked online and a lot of the people who provide these kind of lights are in China or like Texas area.The ones I see on Amazon don't have fast shipping option. Marie suggested that we check with Vistek on bank st because they might have rent out IR lights. I need to call them tomorrow. Also, I did some break down of the logic for collision detection. I also started to do the first iteration of UI design for the game. I made design how we could display information: like health box, instruction, and combo hits. I think personally I want to have less amount of instruction. We want to make intuitive and immersive game. This week has been tough week for the group. We didn't get the chance to discuss as group. Next week, I want to share my idea with my group about UI. Also I must find a light source during reading week.
Milestone #4

I got the reflective material this week.I had ordered the IR light on Amazon on Feb 2. I got confirmation email where it said it would within 1-2 weeks. Last week I emailed Amazon because when I looked at my order information it said it would come March 2- March 23. I realize that Amazon response went to my junk mail. They essentially said that they contacted the seller and that the information was wrong that they had initially sent me and apologize . They just said that once I get the package I can get a full return if I just send it back. So the seller didn't provide tracking so they said that they don't know necessarily where the light is. They just know that the product was shipped. I have big dilemma. I need to find a light source ASAP. I've looked online and a lot of the people who provide these kind of lights are in China or like Texas area.The ones I see on Amazon don't have fast shipping option. Marie suggested that we check with Vistek on bank st because they might have rent out IR lights. I need to call them tomorrow. Also, I did some break down of the logic for collision detection. I also started to do the first iteration of UI design for the game. I made design how we could display information: like health box, instruction, and combo hits. I think personally I want to have less amount of instruction. We want to make intuitive and immersive game. This week has been tough week for the group. We didn't get the chance to discuss as group. Next week, I want to share my idea with my group about UI. Also I must find a light source during reading week.
Milestone 4 - Nicole
This week I was unable to work much further on the PS3EYE and my IR tracking code due to waiting on our materials. Due to some mix up on the part of the provider, we are looking for an alternative source of lighting for our project. As such, I tested more with lights i had lying around with few results.
Overall I feel there was not much progress made this week.
Thursday, 9 February 2017
Ayan-Milestone 3
This is week was a little bit slow. I started the process of the rigging the character. I made broke down file of the character's parts. My biggest issue was that last sprint I purchased the light and infrared tape. Amazon had initially said that the tape was coming within a week and half. I checked the tracking of the product. The product is now coming in March 2. So, I had the email Amazon about the issue. I have yet to get a response on back. Nicole said that we should be able to use reflective material like aluminum for the time being.
Milestone 3 - Erin
Overview - What features and tasks did you work on this past week?
This week I continued to learn about Unity and about using C# to move the enemies around the screen.
.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
When trying to use Unity, I found that moving from Unity at Carleton to Unity at Algonquin would often mess up the files I was working on, just because of the different versions available. The older version of Unity was unable to support the newer version.
I would approach it differently by installing Unity on my laptop, rather then relying on the available school computers.
Successes - What did go well? What approach(es) did you take?
I found that by consulting online resources when coding the enemy movement was very useful, and helped me to understand more about C# with Unity.
This week I continued to learn about Unity and about using C# to move the enemies around the screen.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
When trying to use Unity, I found that moving from Unity at Carleton to Unity at Algonquin would often mess up the files I was working on, just because of the different versions available. The older version of Unity was unable to support the newer version.
I would approach it differently by installing Unity on my laptop, rather then relying on the available school computers.
Successes - What did go well? What approach(es) did you take?
I found that by consulting online resources when coding the enemy movement was very useful, and helped me to understand more about C# with Unity.
Milestone 3 - Nicole
This week I worked on getting the PS3Eye camera projects working, and getting some basic IR tracking working. Facing a few more technical difficulties with OpenFrameworks add ons with the driver set me back, however I managed to put together some makeshift colour recognition:
I tested a few different materials (mirrors, a running jacket, different tapes) and light sources(flashlights, desk lamp, kitchen lighting), however tinfoil seemed to reflect the best for testing, alongside my phone flashlight. I will be able to refine this further and get tracking set up nicely once the reflective material we ordered arrives, as well as our IR light source.
I tested a few different materials (mirrors, a running jacket, different tapes) and light sources(flashlights, desk lamp, kitchen lighting), however tinfoil seemed to reflect the best for testing, alongside my phone flashlight. I will be able to refine this further and get tracking set up nicely once the reflective material we ordered arrives, as well as our IR light source.
Thursday, 2 February 2017
Milestone 2 - Marie
For the second week of the project Pillow Fright's development I was tasked with refining the art assets for the player characters and their weapons, as well as aiding in getting the tape, testing IR reflective materials and if necessary help with the setup of the basic tracking with the camera code as well as set it up with a base file. This last task is because I have a Mac and the plugin driver we found that works with the PS EYE works best on Mac and not windows.
System Setup: As we hadn't gotten the tape yet, the testing of IR reflective materials can't exactly be done. I did a basic test with the camera and the IR lens to see how much infrared light is reflected in a normal environment (a classroom), and realized we would need an IR emitting light to get more accurate tracking on the tape.
Character Design: I changed the colour palette of the characters and created 2 new characters with their corresponding weapons (pillows). I exported them as individual EPS files for use in the Unity scenes for testing.
• Failures
System Setup: As we hadn't gotten the tape yet, the testing of IR reflective materials can't exactly be done. I did a basic test with the camera and the IR lens to see how much infrared light is reflected in a normal environment (a classroom), and realized we would need an IR emitting light to get more accurate tracking on the tape.
• Successes
Character Design: I changed the colour palette of the characters and created 2 new characters with their corresponding weapons (pillows). I exported them as individual EPS files for use in the Unity scenes for testing.
Milestone 2 - Nicole
This week I focused my time into getting the PS3EYE camera drivers set up in order to start working on some test projects and tracking, as well as learning how to use Unity. I ran in to quite a few hurdles along my way, that ended up slowing the development I expected to have done, however I am in a good starting place for Milestone 3.
Unity
At the beginning of the milestone, I ran through Unity's tutorials on setting up a game environment, creating objects, and adding scripts. The tutorial I started with was Roll-a-ball, a simple unity game where you add physics scripts to a ball to allow it to roll around a plane. It gave me a brief introduction into the type of code I would be using when adding in the game code to our project, such as collisions. It also gave me a good run down of the program's layout.
I watched a few tutorials on Youtube about creating a fighting game. Though our movements would not be controlled by button presses, there were some similar themes as to what we would be making.
PS3EYE
The PS3EYE drivers were more problematic than I expected. We had required the assistance of Anthony Scavarelli while attempting to set the camera up with the school's computers, only to find out the camera drivers were very difficult to work with unless on a Mac. After receiving a test project from Anthony, I went about installing the PS3EYEGrabber and adding it to the correct folders. This turned into quite the nightmare as I ended up running into constant errors all the way until I re-downloaded Xcode itself, OpenFrameworks, the grabber, and finally the test project.
Milestone 2
AYAN
OverviewThis week completed creating of my enemies. I worked on learning more about Unity. I worked on figuring how to rigged 2-D character for the future sprint. I purchased the IR Material and IR light.


Failures
- We didn't complete as much as we plan to do. Because we needed to acquire the material before proceeding with other tasks.
-It took me a long time to find a Unity tutorial that was the same version I had that was discussing the rigging.
Successes
- I was able to complete the art asset for enemies. I was able to order in the tape and light which was an extremely important step for the proceeding with the next tasks.
Milestone 2 - Erin
Overview - What features and tasks did you work on this past week?
This past week I worked on learning more about Unity, and I worked on setting up the environment we will use throughout the creation of our game installation
.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
When trying to set up the environment, I tried to follow a set of tutorials. When working with different tutorials, I found that they often used different versions of unity or special packages that I could not access. I would approach it differently in the future by looking further into the details before going into the tutorials to check and see if I'm able to use them properly or not.
Successes - What did go well? What approach(es) did you take?
I found that a combination of consulting my peers who had previously used this version of Unity and watching a relevant tutorial, I was successfully able to understand more of the Unity setup process, and set up the environment.
This past week I worked on learning more about Unity, and I worked on setting up the environment we will use throughout the creation of our game installation
.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
When trying to set up the environment, I tried to follow a set of tutorials. When working with different tutorials, I found that they often used different versions of unity or special packages that I could not access. I would approach it differently in the future by looking further into the details before going into the tutorials to check and see if I'm able to use them properly or not.
Successes - What did go well? What approach(es) did you take?
I found that a combination of consulting my peers who had previously used this version of Unity and watching a relevant tutorial, I was successfully able to understand more of the Unity setup process, and set up the environment.
Friday, 27 January 2017
Milestone 1 - Nicole
Milestone 1
Nicole
Overview
For the start of the first milestone, I tasked myself with starting the base code for our project, namely pseudocode to plan out the individual moves. I have also done some ground work towards creating a particle system for successful hits from these moves, which I will be starting for the second milestone.Successes
- The pseudocode took much less time than expected, however is not very specific as I am not very familiar with C# or JS.
- As we covered particle systems in class, I was able to do some basic testing on how particle systems work.
Failures
- Our priority for the week shifted to getting the camera driver set up and ready, which we struggled with getting to work with some previous code. Currently we are receiving some assistance in order to get the driver working so that we may continue progress.
- I realized after a discussion with Anthony Scavarelli, that my intended plan to prototype and design in Processing and then move the work over to Unity would not work as intended. As such, my intentions of furthering progress on the moves by actually coding them was not possible. I instead took my time to begin doing Unity tutorials on 2D fighting games in order to better understand what will be necessary.
- In the end, while there was time consumed, not much was done on my end for the project.
Thursday, 26 January 2017
Milestone 1 - Erin
Overview - What features and tasks did you work on this past week?
For the first sprint of our project, I was in charge of creating the initial background and researching the creation of Unity environments. As a group we worked on deciding on a theme/art style to use throughout the game.
When creating the background I started by sketching out initial ideas, which helped me to decide what type of environment we should have our game take place in. After this I made our first design, and tweaked it until it fit with the rest of our assets.
As I am personally unfamiliar with Unity, I started by asking my peers about the usage of the program. Then I moved onto online research and YouTube videos.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
When Ayan, Marie, and I were creating our art assets, we didn't do it all at te same time or on the same computers, making the colors difficult to select. So when I first showed them my background, we were all pleased. But as soon as I put their characters on top of my background, we found that the background was too bright and drowned out the characters. From this point I fiddled with the background until I had a finished product that we were all satisfied with.

Successes - What did go well? What approach(es) did you take?
I found that looking through different Unity setup tutorials was very helpful with figuring out how to create a Unity environment. They lead you through step by step and educate you on how to do things while you're able to follow along.
I also found that when editing my background to make the characters stand out, having the characters present on screen really helped to tell what looked good and what didn't.
For the first sprint of our project, I was in charge of creating the initial background and researching the creation of Unity environments. As a group we worked on deciding on a theme/art style to use throughout the game.
When creating the background I started by sketching out initial ideas, which helped me to decide what type of environment we should have our game take place in. After this I made our first design, and tweaked it until it fit with the rest of our assets.
As I am personally unfamiliar with Unity, I started by asking my peers about the usage of the program. Then I moved onto online research and YouTube videos.
Failures - What did not work out as planned? Why not? What did you learn and how would you approach it differently next time?
When Ayan, Marie, and I were creating our art assets, we didn't do it all at te same time or on the same computers, making the colors difficult to select. So when I first showed them my background, we were all pleased. But as soon as I put their characters on top of my background, we found that the background was too bright and drowned out the characters. From this point I fiddled with the background until I had a finished product that we were all satisfied with.

Successes - What did go well? What approach(es) did you take?
I found that looking through different Unity setup tutorials was very helpful with figuring out how to create a Unity environment. They lead you through step by step and educate you on how to do things while you're able to follow along.
I also found that when editing my background to make the characters stand out, having the characters present on screen really helped to tell what looked good and what didn't.
Milestone 1- Ayan
Milestone 1
Ayan
Overview
The first milestone consisted of deciding on an art style , making rough sketches of the enemies characters ,and researching on IR camera. Our group made the decision on the art style of our game. This was an very important step because we have three different artists working on the art assets. We must have consistency in your style. We decided on having 2-D colorful design with shadows. I'm taking the responsible of the creating the enemies for Pillow Fright. I made my first iteration of enemies. Also I made some simple outlines of the enemies to be used for testing. I also did some researching on IR camera.
Successes:
- I completed my first iteration of enemies. I thought it would be difficult in keeping a consistent art style with Erin and Marie but it hasn't been the case.
- James and Anthony have provide us with a lot of resources and suggestions on IR camera. They have allowed us to borrow a PS3 camera with IR lenses.
Failure:
- Although we have been successful in researching on IR camera . We need to make decision quickly as a group if we should purchased the reflective tape, the patches of reflective fabric, or the IR reflective paint. Because it might take awhile for it to ship to us.
Milestone 1 - Marie
For the first week into the Pillow Fright project I made character concept artwork, sketches and created simple figures for later testing with the code. Ayan and I also looked into what type of camera we would need for infrared(IR) tracking as well as how to mesh it with our choice of programming software. Finally, we also looked into what was the best option for tracking IR, either through tape, reflective paint, or other materials.
We decided to go with an altered Sony PlayStation EYE digital camera device with an IR lens. I also researched the necessary drivers on how to mesh the PlayStation EYE with OpenFrameworks and all the necessary plugins.
System Setup: I ran into some trouble when trying to install and test Github developer-made drivers for the PlayStation EYE, it required external downloads of other libraries, and wrappers which, even through the instructions were thorough, it did not work well. The camera on its own would work on some computers but not on others as well. We are currently getting assistance in resolving this issue. Additionally, along the way we realized we would need an IR illumination source in order to track IR reflective tape.
Character Design: The colour palette would need to change so as to differ between characters and become more vibrant. This would help make the characters pop from the environment background.
System Setup: We were able to acquire the PlayStation EYE camera with some help and were able to test it quickly. We also decided that reflective IR tape would be the best approach to infrared tracking. And are planning our next steps into acquiring the tape.
Character Design: The sketches went well, the art style worked out immediately with a flat/gradient design.
We decided to go with an altered Sony PlayStation EYE digital camera device with an IR lens. I also researched the necessary drivers on how to mesh the PlayStation EYE with OpenFrameworks and all the necessary plugins.
• Failures
System Setup: I ran into some trouble when trying to install and test Github developer-made drivers for the PlayStation EYE, it required external downloads of other libraries, and wrappers which, even through the instructions were thorough, it did not work well. The camera on its own would work on some computers but not on others as well. We are currently getting assistance in resolving this issue. Additionally, along the way we realized we would need an IR illumination source in order to track IR reflective tape.
Character Design: The colour palette would need to change so as to differ between characters and become more vibrant. This would help make the characters pop from the environment background.
• Successes
System Setup: We were able to acquire the PlayStation EYE camera with some help and were able to test it quickly. We also decided that reflective IR tape would be the best approach to infrared tracking. And are planning our next steps into acquiring the tape.
Character Design: The sketches went well, the art style worked out immediately with a flat/gradient design.
Subscribe to:
Posts (Atom)















