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.
Thursday, 30 March 2017
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.
Subscribe to:
Posts (Atom)



