Friday, 7 April 2017

Final Post - Nicole

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.

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.

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.

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.

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.