Thursday, March 14th

Class Hours: 9:40 – 2:05
Mr. Cronin

Notes

Thursday! Happy Birthday Jace!
Game Teams – Beta Testing tomorrow. Beta testing checkoff today.
The following students need to be in the EHS Health Office at 11AM today for 5 minutes- I have let Mrs. McCadden know already.
- Peyton
- Aiden
- Phoenix
- Little
- Braden
- Barber
- Jace
- If you don’t want to be the one waiting in the Nurses’s the longest, get there first.

10:05 Attendance and Article

10:10 Week 26 Skills Production

“Robotic Arm in a Factory or Warehouse”

This week the animation is not about a story. This week the animation is about a demonstration of the Robot Arm.

If your team chooses Factory – the Arm will be assembling something basic. We don’t care what, the project is about the Arm. The focus is the Arm, not what is being built.

If your team chooses Warehouse – the Arm will be taking content from an assembly line and packaging it. Again, we don’t care what, the project is about the Arm. The focus is the Arm, not what is being packaged.

While there is to be no story, you have to think about an attractive and creative way to show off your Arm animation.

A potential animation pacing you could use:

(The Arm is always working in this example – you are just watching it)
Shot 1 – Establishing shot. Fade up from black. Far away. Slowly dollying into the Arm. Just a corner of the warehouse is lit. Don’t model more than you need.
Shot 2 – Medium shot of entire Arm doing its work.
Shot 3 – Top view of entire Arm doing its work.
Shot 4 – Close up of Arm building / placing.
Shot 5 – Reverse of establishing shot. Slowly dollying away from the Arm. Fade to black.

Whatever you and your team choose – make sure the focus is the Arm.

You may or may not need to use an armature for this project. Basic parenting could be used as we don’t care about weight painting or deformations (skin bending).

Save your file as lastNamelastNameArm.mp4.

You have until Friday at 12:25.

Our schedule:

Jan 25, 26 – GDD / STOT / Mood Board
Feb 1,2 – Work and document with Alpha testing as our next deliverable.
Feb 8,9 – Work and document with Alpha testing as our next deliverable.
Feb 15,16 – Alpha Testing and Feedback. This is an early test, conducted after the development phase but before Beta testing. It’s considered a form of internal acceptance testing. Mr. Cronin will play each of your games on Thursday the 15th and Friday the 16th. I must have a playable character to “be”, a world to interact in, and a reason to do what we are doing. This is more than just a level demo – we should start seeing basic gameplay mechanics (collection, opening, exploring, etc.)
Feb 21, 22 – Work and document with Beta Testing as our next deliverable.
March 7,8 – Work and document with Beta Testing as our next deliverable.

March 14,15 (Current) – Beta Testing and Feedback. You must have all that you had in Alpha testing, now with sound, a complete 1st level, UI elements, and an achievable goal. This is your MVP – or Minimum Viable Product to pitch to the judges. If the judges walked in the door we should be able to sell our game to them this week.

Thursday – Demonstrate Beta Milestones

Sound (25% of this weeks grade)
Complete First Level (25% of this weeks grade)
UI Elements (25% of this weeks grade)
An Achievable Goal (25% of this weeks grade)

Schedule:

10:15 Alex and Ben
10:20 Mia and Otto
10:25 Tobi and Peyton
10:30 Jace / Tennyson
10:35 Dylan / Brodey
10:40 Zim / Scotty
12:00 Xavier / Zander
12:05 Phoenix / Little
12:10 Sparky / Philip
12:25 Aiden / Kevin

Friday – Beta testing:

Be ready at 10:05 to host players. These players are not CAWD students. You have to explain what you are to do and let the game testers play your game.
The most important parts of Beta testing is to watch the players use your game. How do they use your game? What do they do which is unintended? Where do they run first? What did they try to do that you hadn’t thought about? Think of these like mini-judges. You never know how users will use your product (game, website, anything) until you watch them use your product. We had an example just Tuesday where Otto expected their player to run into the fence, but when we pulled a CAWD2 player that never had seen their game, they didn’t, and since they didn’t, the game didn’t progress. They player didn’t know what to do. This is why we do Beta testing. How will users use your game? Once your team sees how users play your game, we take that info and improve.

There is no additional deliverable for this week for Game Teams – just the Thurdsay checkoff.

After English on Friday your goal with your partner is improve where you are deficient. Whatever your team is behind on – catch up.

March 19, 20 – Create Game Trailer for judging (OBS + Premiere + Sound Design)
March 28, 29 – Create and practice 10 minute presentation for judging.
Thursday April 4th – Vermont State Design Competitions!

See Mr. Bohmann’s CAWD2 Dayplan.

You have until Friday at 12:25.

10:50 Morning Break (10 minutes)

10 Minute break – you have to exit the room.
When the door near the TV is open, you are welcome to come back in.

11:00 English

11:55 Week 26 Skills Production

12:25 Lunch

No food in the room / eat in the Cafe.
You are welcome to return to the room when you have finished eating and work / hang out.

12:55 Attendance and Article

1:00 Steve Jobs Biography

Read along with Mr. Cronin. Improve literacy, word decoding, enjoy a nice story, and unplug from the world.

1:20 Afternoon Break (10 minutes)

10 Minute break – you have to exit the room.
When the door near the TV is open, you are welcome to come back in.

1:30 Speed Design

Speed Designs are 10 minute sprints in CAWD where we practice. It could be any medium – 3D, 2D, video, programming, etc.

1:45 Afternoon Practice & Production

CAWD Step-by-step Layout
- In folder called centerChannel
DH26: Pots and Spoons
- (lastName)DH26.jpg
Week 26 Agency
- (lastName)Agency_1.jpg
- (lastName)Agency_2.jpg
- (lastName)Agency_3.jpg

Skills work!

2:20 Dailies

2:25 “19 Minutes”

4 of 5 days per week we will end our day in CAWD with the “19 Minutes” of silent reading. Closing down our day with silent reading provides many benefits:

Improve Literacy Skills / Reading Stamina
Create space for a small reading meditation where we can disconnect from the world and get lost in a story
Unplug

At 2:44 each day I will come to 3 students and ask for a 1 sentence explanation of what happened in your story over that day’s reading session. It is neat to hear little pockets of a story, here and there.