Plan for this afternoon Team Assignments Team Assignments - - PDF document

1

Team Assignments

Plan for this afternoon

 Team Assignments  Expectations for Checkpoint 1

Spring Job Fair

 Fair:

 Wednesday, March 28, 11a.m. – 4 p.m. in

the Gordon Field House.

 Inteviews

 Thursday, March 29

 More info to come…

Logistics

 CVS Repository

 vtheatre group account  To be set up on UNIX machines  More details to come but…  Need CS account names for group account.

Are We Ready

 Teams:

 moCap  Puppet  Staging  Audience  Audio  Networking

About the teams

 Some teams

 Responsible for set of theatre participants

 GUI  Interaction  Models  Perspective

 Some team’s

 Responsibilities spans all teams

2

Team moCap

 Members:

 Tayeb Karim (leader)  Adam Linderman  Stephen Bialobok  Brandon Chez

Team moCap

 Responsibilities

 “Actor participants” that use moCap equipment

 ShapeWrap II (full body)  5DT Data Glove (hand only)

 Tasks

 Logistics / setup of hardware  Import of Maya models (also puppet)  Integration of all appropriate software.  GUI: keyboard  Viewing: HMD (team audience)

Team moCap

tge.exe (C++) Virtual Theatre (TorqueScript) Shape Recorder (measurand) Ray’s API 3D Virtual stage

Team Puppet

 Members:

 Nick Kochakian (leader)  Kevin Pazirandeh  Hao Yan

Team Puppet

 Responsibilities

 “Actor participants” that control models with

predefined animations.

 Tasks

 Import of Maya models and animation (also

moCap)

 Identify animations from file and store internally

for later playback

 Control of each animation separately  Blended animations.

 GUI: List of animations and triggers to play.  View: 1st person perspective (team audience)

Team Staging

 Members:

 John Santino (leader)  Jonathan Bryan  Josef Schelch (GUI expert)  Steven Schutzman  Team Audio

3

Team Staging

 Responsibilities:

 “Stage Manager”  Components:

 Lights  Cues  Virtual light / sound board  Sound (sort of)

Team Staging

 Tasks:

 Define lighting subsystem  Define software objects for cues/actions  Define infrastucture for setting, loading,

saving cues.

 Define GUI for triggering of cues

Team Staging Team Audience

 Members:

 Darren Stanley (leader)  Jacques Bosman  Dominick D Aniello

Team Audience

 Responsibility:

 “Object” for generic viewer (1st person)  GUI for audience members (keyboard)  Link to HMD / moCap system.

Team Audio

 Members:

 Nicholas Blake  Matthew Penepent  Joe Geigel (leader)  John Santino (co-leader)

4

Team Audio

 Responsibilities

 Audio subsystems

 Music  Sound effects (staging)

 GUI

 simple viewer  MIDI instrument

Team Networking

 Members:

 Darren Stanley (leader)  Team of one

 Responsibilities:

 Making sense of TGE networking  “Assembling” the server

 What goes where?  What client / server communication needs to take place

 Co-ordination with all groups.

Questions so far? Checkpoint 1

 Goal:

 Implementation plan

 What needs to be done  Who’s going to do it.

 Basic tasks to get things rolling.  Lots of research on how Torque does things

 Date for deliverables:

 Tuesday, March 27 (next week!)  Team conferences

Checkpoint 1

 Team moCap

 Get profiled, suited up, and capture motion with

shapeRecorder

 Explain how Torque does articulated figure motion

from a rigged model.

 Plan for importing of Maya models into Torque

(link on mycourses)

 Implementation plan for integration of Ray’s API

into TGE

 Dig deep into C++ code  Docs on tge internals on garage games Web site.

Checkpoint 1

 Team Puppets

 Explain how Torque does general articulated

figure motion from a rigged model.

 Import of models and animations from Maya (link

• n mycourses)

 How does Torque store/manage predefined

animation sequences.

 Design of interface for “animation blending”

5

Checkpoint 1

 Team Staging

 Investigate lighting capabilities in Torque

 Set up a lighting grid

 Implementation plan for cuing system  GUI Design for stage manager interface

Checkpoint 1

 Team Audience

 Learn how first person viewing / control

works in Torque

 Design of “viewer” object that can be

controlled in a variety of ways

 HMD / keyboard / etc.

 Set up of HMD hardware.

Checkpoint 1

 Team Networking

 How does the client server communication

work in Torque.

 Some idea of where things fit in the

“theatre game”.

Checkpoint 1

 Team Audio

 How does audio work in Torque

 Sound effects  Music

 Design of audio subsystem.

For the rest of today

 Logistics

 Breakout Room 2 access

 Team moCap and Audience  Others? Please let me know

 Team gatherings

 Get to know each other and strengths

Next time

 Team working time…  Questions?