Within this project, I set myself a few milestones at the beginning in preperation for this point in the course. The main thing I wanted to do was to further my knowledge of programming and try to focus on that aspect of the project's development. I was also very interested in the mechanical side of our design proposition, with moving the Kinect around a room in relation to a persons position.
At this point in time, I'm in charge of the group, although it wasn't always that way. To begin with, Laura was our leader, but because she wasn't confident in her ability to be in charge of the group she asked me to take over. I have mixed feelings about this for a number of reasons. Firstly, it was probably a good idea because I feel like I would be a better group leader than her, especially if she went into it with the idea that she wouldn't be. In contrast to this, I have a feeling that it would have been better for the group as a whole if she had stayed on as our group leader. At the moment our team is struggling with interaction, mainly due to the language barrier we face with having members who don't have English as their first language. Having Laura as our leader may have negated some of this as she would be able to take charge in their native language where I struggle to communicate with our group members sometimes.
I feel that this barrier we face as a group has somewhat hindered our ability to work thoroughly on our project. In conjunction with this language barrier, I feel that some of the members of the group have a large disinterest in the project, so much that they work a little on their part of it then put it out of mind. This makes managing a large project quite difficult, as it means work is either not delivered or it's delivered at a subpar standard. The only course of action we've been able to take in relation to this is to press on with our work as best we can and not overly rely on imput from all members of the group. The way we structured our project initially means that there are two main focuses for our group, and at present we are able to press on with at least one of these working properly. While this means we may not end up presenting everything we set out to present as a final project, it does mean that we will be able to have a large section of it finalised, be it proof of concept or finished completely.
As group leader, seeing early that these issues were arising, I had to add my milestone the notion of keeping the group running as smoothly as possible. I feel that to a certain degree I've been successful with this so far. A lot of my time in this project has gone towards trying to ensure that everyone knows what they're doing and when they need their work to be completed. Though no matter how much I stress these issues I still find that it is out of my control if the work actually ends up being done or not, which can be frustrating, especially when that work then falls onto others to complete.
Mechanical Design:
From the outset of our project, we split the group into two parts, the design of the mechanical and programming side of things, and the Crysis side. Myself and Matt took the physical aspects of our project and have been working on these since the beginning. Together we discussed idea for how our system would work. Matt designed the initial Kinect Rig, drawing up the plans which we eventually had laser cut into a prototype. Through this stage, I helped a little in talking through the design choices, although most of the work on this front was Matts.
My work on the mechanical side of things has been through the conceptualisation of our system for moving the Kinect across the room. Our initial brainstorming came up with the idea of using a Spider-Cam like system to move the rig across the roof of the room.
This type of system runs wires from each corner of the room to the decide. Motors at the corners extend or contract the wires in unison, allowing the system to move freely. I've investigated into these types of devices to see how they run, as well as how to integrate it into our proposed system for the Kinect. At the moment we are still trying to narrow down how this would work if we were to add it into our prototype, so at the moment it's use is purely theoretical.
Programming:
My main aim for this project was to immerse myself into the programming side of it, as so far I have very little to no experience with that sort of thing and would like to know more about it. The project focuses on programming on two fronts, the Kinect's integration with Crysis, as well as Arduino to run the motor systems for the Kinect.
For the Kinect, we're managed to get the integration with CryEngine 3 working properly with Stephen Davey's help. At the moment what we can do with it is fairly basic, and will probably need us to get into the code of the Kinect and Crysis SDK to achieve what we want it to do. The next step for me will to be looking into these codes and seeing if we can get positional data for each limb on the person being tracked. This will allow us to be more interactive with the bathroom appliances with gestures and body positioning. It will also enable us to do things like changing the height of a toilet seat or shower head depending on the size of the person in the room, two of the major interactive parts we were hoping to achieve.
The other part of the programming that I've been looking at has been the Arduino. Coming from having basically no programming knowledge, fiddling with the Arduino kit has been difficult. I've gone through a learning booklet that Russell provided when he gave out the kits, which has taught me a few things, but at the moment I can't just sit down and make it do something, I need instructions to achieve this. My accomplishment so far is that I actually now understand what all the code is saying, and can figure out some problems when I come to them. I'm very happy with this progress so far, as I was completely stumped by it all initially. So far I've been able to do everything we will need for our rig to work. I've been able to get a stepper motor to move depending on a varying input amount, which would be what drives our spider cam style rig, as well as rotating the Kinect around on it's rig.
So far in this group project, I feel as if I've made progress towards what I set myself out to do at the beginning. I've been able to further my knowledge of programming, as well as how to practically apply that knowledge to our project. I've also been able to help design the mechanical systems that will eventually run it all.
As the team leader, I feel like our team is slowly moving forward, although a lack of interaction has dramatically limited our progress. I feel that if we keep moving at this rate, we will be able to accomplish something substantial, although not at all what we initially set out to do.
Sunday, 5 May 2013
Thursday, 2 May 2013
Week 8
We collected our laser cut prototype friday of last week and have now assembled it.
We were very happy with the way it turned out, although I feel I should stress this is only a prototype. There are a few issues with this current version that need to be fixed. The main one being that we measured the Kinect wrong, so the brackets that hold it in place are too large and it slips out. This would easily be fixed by measuring it correctly and laser cutting only those pieces again. The rotation mechanism works surprisingly smoothly. The whole unit ended up costing roughly $80, which at the moment is far too much, and could be cut down if we were to do it again.
We looked at alternative mechanisms last week and settled on one specific one that Russell ordered for us from the UK. it can be found here:
http://littlebirdelectronics.com/products/df15mg-tilt-pan-kit-15kg
It's a pan and tilt mechanism that offers two axis of movement. So far it is the only commercially available unit that we've found that looks suitable, so I'm looking forward to actually getting it and seeing what we can do with it.
This week we also gave our groups presentation on Intellectual Property. I feel like it went well. Our main strength was that our group talked about the topic in the context of our project, which the other group that went this week failed to do. The text for our entire presentation can be found on our wiki HERE
We were very happy with the way it turned out, although I feel I should stress this is only a prototype. There are a few issues with this current version that need to be fixed. The main one being that we measured the Kinect wrong, so the brackets that hold it in place are too large and it slips out. This would easily be fixed by measuring it correctly and laser cutting only those pieces again. The rotation mechanism works surprisingly smoothly. The whole unit ended up costing roughly $80, which at the moment is far too much, and could be cut down if we were to do it again.
We looked at alternative mechanisms last week and settled on one specific one that Russell ordered for us from the UK. it can be found here:
http://littlebirdelectronics.com/products/df15mg-tilt-pan-kit-15kg
It's a pan and tilt mechanism that offers two axis of movement. So far it is the only commercially available unit that we've found that looks suitable, so I'm looking forward to actually getting it and seeing what we can do with it.
This week we also gave our groups presentation on Intellectual Property. I feel like it went well. Our main strength was that our group talked about the topic in the context of our project, which the other group that went this week failed to do. The text for our entire presentation can be found on our wiki HERE
Saturday, 27 April 2013
Communication Presentation Review - Shades of Black
Overall this group's presentation was good, although there were a couple of areas where it fell down. It was obvious that the group was very well organised and knew what each of their roles within the presentation was. The slides that accompanied the speaking were also well put together. They did not have too much text, or especially the whole talk, but just enough that the audience knew what they were talking about. I did feel as if the pictures that accompanied the talk were too generic, and didn't have anything to do with the group's project, and although they had some link to the topic, they were too generic to really lend anything to the presentation. What everyone said seemed well thought out, although there were a few times were it seemed like the text was a little too verbose. This didn't help the presentation at all, but rather made it seem like they were spilling out large words just for the sake of doing so rather than to explain the topic of communication.
One main concern of mine was that the group tried to tackle the entire idea of communication rather than to pick a small section of it and do it thoroughly. While they did split up the topic into sub topics, these were all summarised quickly by an individual. I think it would have been more substantial to pick one or two of these sub topics and focus the entire presentation on those.
The video at the end of the presentation was interesting, although it did seem to just reiterate the presentation. I did like the interview style the group used, although it seemed too disjointed by each person being in a large variety of seated positions.
One main concern of mine was that the group tried to tackle the entire idea of communication rather than to pick a small section of it and do it thoroughly. While they did split up the topic into sub topics, these were all summarised quickly by an individual. I think it would have been more substantial to pick one or two of these sub topics and focus the entire presentation on those.
The video at the end of the presentation was interesting, although it did seem to just reiterate the presentation. I did like the interview style the group used, although it seemed too disjointed by each person being in a large variety of seated positions.
Wednesday, 24 April 2013
Week 7
Main update this week is that we sent our prototype Kinect rig to the laser cutters here at UNSW.
The prototype will be mainly cut out of MDF, but with one acrylic part for the movement. We still need to buy some nuts and bolts to put it all together with, but that will be easy.
This week we also began testing the Kinect integration on my laptop. It all ran smoothly after spending a while setting it all up. It is a little limited with what we can make the game character do from the real world sensor, so we might have to rethink both our level of interaction as well as our method of demonstration.
Next week we are giving a presentation on Intellectual Property as a group, so we spent some time this week preparing as a group. Our tasks for the talk are split into the following categories:
Using IP:
Creating IP:
![]() |
| Design sent to the laser cutter |
![]() |
| Sketchup model of the prototype |
This week we also began testing the Kinect integration on my laptop. It all ran smoothly after spending a while setting it all up. It is a little limited with what we can make the game character do from the real world sensor, so we might have to rethink both our level of interaction as well as our method of demonstration.
Next week we are giving a presentation on Intellectual Property as a group, so we spent some time this week preparing as a group. Our tasks for the talk are split into the following categories:
Using IP:
- How to use other peoples IP.
- IP our group is using and how we should use it.
Creating IP:
- Automatic IP Rights.
- Formally Registered IP Rights.
- IP we've created and how we'd protect it.
Tuesday, 16 April 2013
Week 6
I was unfortunately sick this week and didn't make class, but I talked to the group about where we're all at and what needs to be done. Matt talked with Stephen Davey about the Kinect integration with CryEngine. Unfortunately Matt's laptop runs Windows 8, which CryEngine 3 is incompatible with, so he'll either have to use my laptop or a uni one to do any work on the Crysis side of things. On a positive side, Stephen already has some code that works with the Kinect in Crysis, that allows for character movement by moving your legs, leaning, as well as recognising hand gestures.
The level design side of the group has also presented some of their work today. They have a first draft of the level, with three different sized houses and the detailed bathrooms. The models all look quite nice, although they could do with some more advanced texturing.
The level design side of the group has also presented some of their work today. They have a first draft of the level, with three different sized houses and the detailed bathrooms. The models all look quite nice, although they could do with some more advanced texturing.
Thursday, 11 April 2013
Week 5
This week wasnon teaching week for UNSW so we didn't have class. Matt and I talked about or ideas for moving the Kinect and are pretty certain we're going to go for the spider-cam system, but we'll get some feedback from Russell and Stephen next week and go from there.
Matt also worked on developing a design for a prototype Kinect rig. Info for that can be found on our wiki Here.
The other three members of our team have worked on the bathroom designs for the Crysis level, and should have them implimented into the environment by class next week.
Matt also worked on developing a design for a prototype Kinect rig. Info for that can be found on our wiki Here.
The other three members of our team have worked on the bathroom designs for the Crysis level, and should have them implimented into the environment by class next week.
Tuesday, 26 March 2013
Week 4
In this weeks studio class, we allocated who will be doing what group presentation later in the semester. I chose the topic of Intellectual Property for our group. This decision came about because it seemed like the most relevant topic to our project. We are using a number of different companies property to create our own system, so I thought it would be nice to investigate exactly how we are and aren't allowed to use this property. Our presentation most likely also cover how we are creating our own IP and how we as a group can protect it. This topic is also very relevant to us as students and as future designers, so I think it will be very useful to look into.
As a group, we talked with Stephen and Russell about our project. We looked at what we were planning on achieving as a group and how we should go about achieving it. Me and Matt both feel that our main problem is going to be the Kinect and how we will get it to function within a system running a number of different things at once. Stephen has some code that works with the CryEngine already, but that doesn't necessarily mean that it will do what we want it to do.
Me and Matt talked about how we think we can move the Kinect around the room to track a person as well. This is because of the limited view range of the Kinect, and the possibility that the user will step out of this space.We had a number of ideas, the most likely being a hinge system. This would be the Kinect sitting on a two axis hinge that would sit in a corner of the room, allowing it to rotate sideways and up and down to track someone. The other idea we came up with was for a bigger room, and is a Spider-cam like system that uses four wires attached to the Kinect and then to winches on each corner of the room. These would allow the Kinect to glide across the roof of the room as the winches push or pull the wires in unison.We will continue to look into these systems and try to figure out which one will be the most useful and easiest to construct.
As a group, we talked with Stephen and Russell about our project. We looked at what we were planning on achieving as a group and how we should go about achieving it. Me and Matt both feel that our main problem is going to be the Kinect and how we will get it to function within a system running a number of different things at once. Stephen has some code that works with the CryEngine already, but that doesn't necessarily mean that it will do what we want it to do.
Me and Matt talked about how we think we can move the Kinect around the room to track a person as well. This is because of the limited view range of the Kinect, and the possibility that the user will step out of this space.We had a number of ideas, the most likely being a hinge system. This would be the Kinect sitting on a two axis hinge that would sit in a corner of the room, allowing it to rotate sideways and up and down to track someone. The other idea we came up with was for a bigger room, and is a Spider-cam like system that uses four wires attached to the Kinect and then to winches on each corner of the room. These would allow the Kinect to glide across the roof of the room as the winches push or pull the wires in unison.We will continue to look into these systems and try to figure out which one will be the most useful and easiest to construct.
Subscribe to:
Posts (Atom)





