Week Summary: Nov 12-16 and IAAPA!

This week most of the team (except for Anuja) went to IAAPA, the International Association of Amusement Parks and Attractions.


So what did we learn at IAAPA?

We learned that we really don't have that much left to do. Jack's own words were "We understand building things, you guys leave that to us. We need 'new ideas', that's what you guys do, and that Pillow Tree is a good, new idea".

We were hoping that this was what they would say; as it was very nice to hear them say this in person, seeing as we only have 2 work weeks left. We are right on target to get everything we
have to do done.

What else does Bob's need?

What Bob's wants from us is all the documentation we can throw at them. They want structural CAD for the tree, but they will "figure out the aesthetic part" on their own. They also want us to test, for placement of all the input devices on the tree.


There are 4 main things we have to do by the end of the semester for Bob's:
1- get all the animations done
2- get the tree in a working state to test
3- test the locations/placements of all sections
4- document like mad


So how are we going to do this? (with Thanksgiving, finals, and the BVW show...)

The following are hard deadlines; as we have to stick to this schedule to get it all done. For each week, we've listed what has to be completed, and then each person has their tasks broken down. We have tried to account for thanksgiving and BVW:

***November Nov 19 - 23***
Things that have to be done this week:
- Order all components for mock up
- Get software architecture robust

Evan: BVW stuff; order stuff; documentation
Rich: Fully determine what we need to buy to make the tree mockup, and order it (so we have it by next week)
Brendan: Animations
Rob: Work on show software remotely
Karin: Animations
Anuja: Clean up all audio, documentation; work with Staque; Record French Audio

Events this week - Thanksgiving


***November 26 - 30***
Things that have to be done this week:
- English Animations
- Spanish Animations
- French Animations
- Music
- SFX
- Soft Opening
- Tree Mockup Built

Evan: BVW stuff; documentation; final budget; prepare for soft opening
Rich: Build Tree
Brendan: CAD; Build Tree
Rob: Integration, Tech Documentation; Help build Tree
Karin: Animations; prepare for soft opening
Anuja: Audio, Animations, Documentation; SFX

- All Animations Done (all languages)

Events this week - Nov 30 - Soft Opening

***December 3 - 6***

Things that have to be done this week:
- BVW
- TESTING

Evan: BVW / Final Presentation / Documentation
Rich: BVW
Brendan: TESTING / CAD
Rob: BVW / TESTING / Teach everyone how to run all the software
Karin: TESTING
Anuja: TESTING

- make final presentation
- work on documentation
- make BVW happen
- Finish all CAD
- Test Tree Mockup

Events this week - Dec 5 - BVW Show

*** December 10 - 14 ***

Things that have to be done this week:
- Pack it up
- present

Evan: Document / Presentation
Rich: TEST
Brendan: Technical Documentation
Rob: Stress Testing / Tech Documentation
Karin: Tighten up the graphics
Anuja: Documentation

- ship it
- ship documentation for review

Events this week - Dec 12 or Dec 14
- Final Presentation

Week Summary: Nov 5-9

This week we:

- Finished the detail model of the tree in maya
- Got a first-pass of the music
- Recorded the Spanish Voice Over
- Determined animation timings and pace
- Finished the detailed OWL charechtor
- Started Animation
- finished the art for the owl's house
- got 7.1 sound working
- got video to play reasonably
- figured out a good codec
- made a sweet DMX application
- made a video of the 'Legend of the Pillow Tree"
- kept the blog up to date
- were awesome TAs

------------------------------

-------------------------

Brendan will:
- Finish up all the lighting passes, and document a lighting scheme
- determine if it makes any sense to get the maya model into solidworks

Anuja will:
- Work with staque to make music
- Get the sound effects all sorted out
- Record the English V/O
- Organize GKTW letters sent to the ETC
- work on animation (cleanup)

Karin will:
- work on animation (key)

Rob will:
- work on animation
- integrate animations into show
- integrate audio into show
- document codebase, so it can be modified later (adding com, adding
language changes, etc)
- automate program start and computer boot

Rich will:
- make functional demo input devices
- mockup functional tree
- work on animation

Evan will:
- figure out the plan for the last few weeks, accounting for a
possible big BVW show commitment
- work on total project documentation (inclusive of what we can't do
this semester)
- encode animations as they are done

-------------------------------------------------------

Also... Here's the IAAPA Plan

Wed - Team drives to airport.
- Fly to orlando
- get in cab, go to hotel, check in
- go to conference
- TEA Party

Thurs - Go to conference
- go to disney world

Friday - go to conference
- go to GKTW

Saturday - go home to PGH

-------------------------------------------------------

Also... Here's the plan for Thanksgiving week (Nov 19 - 23)

Rob will be gone all week
Karin will be gone all week
Evan will leave monday night

By the end of the week:
- we need to have all the animations done and encoded
- we need all the audio to be done, with the music muxed in
- The system needs to be ready for play testing
- we need to have a plan to build the tree mockup at the ETC

Hermes the Owl

Here is our owl, Hermes! He will be the caretaker of the Pillow Tree. Karin created this final version of the owl that will greet the children.

Week Summary: Oct 29 - Nov 2

This week we:

- Finished the Tree Model, sent off photos
- worked on Spanish version of the Script
- Play tested the Owl
- Worked on the Maya Model
- started lighting planning
- fought with Panda (sound and video)...
- acquired Staque's services for music
- started the final owl art
- started the final on screen scene
- planned the IAAPA trip
- Determined that Linux and WinXP are bad
- Storyboarded and determined scenes
- kept the blog up to date

Next Week:

Brendan will:
- Finish detail model of tree in MAYA- Monday
- Determine "Best Case" Lighting for Tree (as we designed it) - Friday
- Spec lighting hardware - Friday

Anuja Will:
- Organize GKTW letters sent to the ETC - Friday
- Work with Staque to make music - Friday
- Find sound effects - Friday
- Work with Language Departments to get script translated/approve
Oscar's translation - By Wednesday
- Further Testing?
- Get audio ready to animate against (placeholder)

Karin Will:
- Finish Owl Char - By Monday
- Start animation - Friday

Rob Will:
- Get Videos playing in Windows - by Friday
- Get 7 channel sound in Windows - by Friday
- Get DMX working in Windows - by Friday

Rich Will:
- Finish Room Art - By Monday
- Animate Owl and room details (lighting) - By Friday
- Do V/O for "Ms. Merry story" - By Wed

Evan Will:
- Make animation templates
- English V/O
- Spanish V/O
- Find Language Voice actors - ASAP
- make "Mrs. Merry" Story Video
- Integration
- Video Compression

The Tree Model Is Done

The physical tree model is done. It took us a couple of weeks to get everything done. Big thanks go out to Karin & Rich for spending so much time and effort into molding the tree. A special thanks go out to Anuja, Brendan, Evan, & Rob for helping out with the leaves too. Here are some photos of the tree:

Here is the entire physical tree model.


















Here are the buttons that a child will press to indicate if they're a knight, princess, or jester.











Here is the heart button kids will need to press to fill their pillows with all their wishes and dreams.











Here is a close-up of one of the branches.












Here's a close-up of the intricate vines.












Here's a close-up of the button path.












Here's a view of the tree once it's covered with the fabric leaves.


















Here's a close-up shot of the fabric leaves.


















Here's while the tree will look like as a child enters the canopy.


















Here's a view of the tree from underneath the canopy.


















Here's the tree enclosed in the entire canopy.

Owl Testing

This week was the first time we got to test some of our ideas with kids. Thanks to another ETC project teams (shoutout to the Carnegie Libaries project!), we got two classrooms of second and third graders.

On Tuesday morning, the biggest thing we wanted to test was our owl character. We had 13 different owls and we had to narrow it down to one. We asked the kids to choose owls they thought were the wisest, oldest, and friendliest. Although we weren't sure what to expect, the kids' answers were a surprise! On a good note, now we have a clear direction on what features we should give our owl.

Here is a summary of our results:

1. Kids thought the two oldest owls were #5 (13 kids) and #12 (13 kids).

2. Kids thought the two wisest owls were #6 (12 kids) and #10 (8 kids).

3. Kids thought the two friendliest owls were #2 (8 kids) and #11 (9 kids), but overall, there was no overwhelming favorites for this category. Votes were disbursed fairly equally for each owl.

4. There were no large gender differences. Girls and boys pretty much had same choices for oldest and wisest.

5. Overlapping categories included #6, #10, and #4 for wisest and friendliest. Oldest did not seem to overlap.

Conclusion:
A combination of OWL #2 and OWL #6 with a little bit of OWL #12 is my vote for the owl, because they received high scores overall with an average score over all categories.

Windows vs. Linux - The Ultimate Showdown

For our computer we were debating whether to use Windows or Linux as our operating system for the pillow tree. We were going to use Linux but we ran into a few problems. They are as follows:

1. We're using Panda3D, a free 3D game engine made by Carnegie Mellon. Our input devices, called phidgets, are compatible with this engine. However, the Linux version of Panda3D does not contain the code required. The Windows version ran on DLL files, and recreating the code to work for Linux would have taken some time.

2. We also have code to interface with DMX, which would control all the lighting effects. However, our code currently involves Windows API. Redoing it in Linux would have also required a lot of work.

3. Video playback just didn't work at all in Linux. The framerate was terrible and it just didn't seem that Linux could perform as necessary.

We then decided to go with Windows. We tried to use Windows XP at first, but we had driver issues. We couldn't find the right drivers for the network adapter or the sound card, and our hardware description didn't solve the problem.

We finally settled on Windows Vista. All of the code works in Vista, so our main goal now is to try to maximize the performance, as the operating system eats up quite a bit of memory.