Class hours: 9:40 – 2:05
Mr. Bohmann
wbohmann@ewsd.org
Week Thirty Six (36)
Today’s Notes
- Today is an EHS B Day
- PE meets at the Tennis Courts
- Res Building Trades – Home Build Tour 1:30 today
- 2 Photographer Volunteers?
- Game Testing Today – let me review
- Google Form
- Publishing
- Talking Points
- For those that had their game tested, review your feedback and incorporate changes to your game. Then, feel free to test again.
- Monday, June 5th – we (CAWD2) will all test each others games for another round of feedback, the we will do a final sprint to incorporate changes and prepare for publishing for Wednesday.
- Wednesday, June 7th will be our Game Jam. We’ll invite others to play our games, talk about our games and show off your work.
- Thursday, June 8th all of the deliverables will be due from the game project for grading. Each of you will do a short presentation about your game, what you learned, what was challenging, what you were most proud of.
- Friday, June 9th – if you threw in the towel, then we’ll be looking to you to share your work / learning with us.
9:40 Attendance
9:45 Web Professionals Practice Session
Visit gosocrative.com and enter room name CAWD2
10:00 OBS Core Game Mechanic
OBS Walkthrough
The Task: Use OBS to demonstrate the core mechanic for your game. Use Premiere to create titles or use voice over to describe what the mechanic is. I want to see it in action, and I want to hear or read about it when I view your clip. While you play your game, explain what you are doing, and how it is the core mechanic of your game. For full credit we need to see the completed mechanic.
It is ok that you are in prototype mode. Doing a core mechanic overview give us the pitch/purpose of your game. I am going to catalog these videos to share with future classes.
Remember The core mechanic in a game will usually be the purposeful interaction that occurs the most frequently. Jumping, collecting, sliding, farming, etc…..
When complete create a file animation called “CoreGameMechanic_LastName.mp4”
This assignment is due Today – end of day.
When you finish showing your core mechanic – continue working with your game.
Throw in the Towel (I’m done until game testing feedback)
If you have completed the alpha of your game and do not plan to continue developing, revising and generally working on your Cawd final game project until after game testing, you will need to continue working on a project independently. This may be:
Your How To for English
A CAWD Knowledge Exchange – where you take your favorite topic, build a lesson and plan to teach us how to do it. You become the teacher and we build, learn, practice with you. We can schedule a day to present next week.
CAWD Project Revision – you take a project from the year that you’d like to improve, add on, revise or just overall go “further”. You’ll share your “mod” with us next week
SkillsUSA (if this applies to you)
10:35 Break
10:45 CAWD Game Studio or I’ve Thrown in the Towel
Game Publishing for Testing…
Before you prepare your Alpha for publishing…
- Create a folder in your Unity Directory – Name it Builds
- Choose that folder when exporting for a Build
- Test to see that the screen resolution and size is ok
- if you need to adjust, do this in project settings under player
- Choose Resolution, then choose Windowed, then set screen dimensions
- Drop your build folder with your .exe file in the Cawd Game Studio Folder in Public Folders
- Name your Folder BohmannBrickBreaker_Alpha (for example)
11:40am Game Testing – Visitors from CAWD
Friday
Game Testing
Nexus Trace
Catana
Breakout
Aperture
The Bush
Shadow Strider
Monday
Game Testing
Violet Vengeance
Slime Scape
We have visitors today from CAWD1. The students will be the incoming class for CAWD2. Your task is simple. Show them your game / what you have been working on for your game (if your a team).
These students have never seen Unity nor do they know anything about C# programming. Give them a 3 minute overview of your project. Don’t sweat it, you are in dev mode. They are interested to learn what you have been making/coding. We’ll rotate every 3 minutes.
During your 5 minutes, have them test your game and have your Google Form up and ready to go for feedback.
Talking Points (if you need them)
- My game is….
- The core game mechanic is…..
- The goal is to …..
- This bit of code is cool because it does…..
- I made this asset / texture / material / lighting / environment / sprite ……
- I am proud of ….
- I’d like this game to ……
12:15 Lunch
12:45 Independent Reading
1:10 Break
1:20 Independent Project Work Time of Individual Support
- Incomplete Work
- Game Dev time / Passion Projects
- OBS Core Mechanic Walkthrough