Skip to content

Sprint 1 Game Audio User Testing

37JackHirst edited this page Oct 13, 2021 · 2 revisions

Usability testing is a great way to uncover problems, discover oppurtuinties to improve and learn about the targeted user. Due to time constraints, user testing was completed by various team members seperately, however, the team created a user testing plan together in order to ensure consistency. For these user tests, we decided to go with explorative tests that allowed the participant to have a more open-ended conversation. We asked the participants to brainstorm, give opinions and express impressions about our feature. In order to have precise data, we firstly introduced our feature and what our aims/goals were and then followed with some leading questions.

Example Leading Questions

  • Do you think our backtrack sounds connect with the games theme?
  • Do you think our sound effects connect with the games theme?
  • Do you think our sounds produce the right mood for the game?
  • Are our sounds consistent with the games theme as well as with each other?
  • Do you have any other recommendations for sounds that would enhance our overall game experience?

Participant 1

This participant liked how there were two different sounds between the start menu and the actual game. The participant continued to say that the use of actual Windows OS sounds for the sound effects was a "great idea" that "goes along with your guys theme really well". However, she did state that the main menu backtrack sound seemed "less techy" compared to the other sounds. In terms of the mood of the game, the user aid that the void becoming louder due to the distance "creates alot of tension and is a great addition".

Participant 2

For this user test, we followed the same explorative method except didn't introduce what our feature was before the user played with the game. The team did this in mind to see if the user had any noticable negative or positive first impressions to the sound. The user didn't have any impressions on the sound at the start and, after explaining our feature, had no further recommendations. The team then introduced the sound effects and the user liked these sounds as well. He said that he liked how the sounds could be "slightly changed and built upon" when new features are created in the game. He continued to state that with the addition of more intense levels that the sounds "have the potential to create alot of tension which is super cool". In terms of the void, the participant said that this was a "super good little add on that really contributes to the excitement in the game".

Participant 3

This partipant explained that he felt the backtrack sounds seemed "not in unison" and "sounds like three different games". He stated that he could understand how the backtrack sounds integrated with the games theme but felt as though they didn't integrate with each other. In terms of sound effects, the user stated that the Windows OS theme integrates well with the game and also is easily distinguishable for most players which brings a "fun" addition to the game.

The Results

From these explorative user tests, the team decided to create 3 backtrack sounds that aligned more with the Windows OS theme. The team then continued to create sound effects from the Windows OS sounds that had the ability to be "built-upon" in order to create more tension with more levels. We also decided to focus more attention in the code that changed the void sound the closer it is to the player. The team felt this was an extremely important feature that has the ability to create more tension in the game and therefore a better experience.

Table of Contents

Home


Game Design

Game Design Document

Void/Antivirus

Loading Screen

Game Sound

Menu Assets

Player Design

     Original Design

     Final Design


Gameplay

Movement

Jumping & Sliding

Jump Pads

Portals & Bridges

Buttons

Pick-Ups

Physics

    Momentum & Physics

    Gravity

    Collision


Level Design

Level 1

     Background

     Textures

     Map Design

Level 2

     Background

     Textures

     Map Design

Level 3

     Background

     Textures

     Map Design

Level 4

     Background

     Textures

     Map Design


Sprint Round-Up

Sprint 1 Summary

Sprint 2 Summary

Sprint 3 Summary

Sprint 4 Summary


User Testing

Testing Plans

Sprint 1

     Team 1
     Team 2
     Team 3
     Team 4
     Team 5

Sprint 2

     Team 1
     Team 2
     Team 3
     Team 4
     Team 5

Sprint 3

     Team 1
     Team 2
     Team 3
     Team 4
     Team 5

Sprint 4

     Team 1
     Team 2
     Team 3
     Team 4
     Team 5

User Testing

Sprint 1

     Sprint 1 - Game Audio
     Sprint 1 - Character Design
     Sprint 1 - Menu Assets
     Sprint 1 - Map Design
     Sprint 1 - Void

Sprint 2

     Sprint 2 - Game Audio
     Sprint 2 - Character Design
     Sprint 2 - Menu Assets
     Sprint 2 - Interactable Design Animation
     Sprint 2 - Levels 1 & 4, and Level Editor
     Sprint 2 - Proposed Level 2 & 3 Designs
     Sprint 2 - Current Game State

Sprint 3

     Sprint 3 - Menu Assets
     Sprint 3 - Map Design
     Sprint 3 - Score Display
     Sprint 3 - Player Death and Spawn Animations
     Sprint 3 - Pick Ups and Pause Screen

Sprint 4

     Sprint 4 - Gameplay
     Sprint 4 - Game UI and Animation
     Sprint 4 - Level Background and Music
     Sprint 4 - Game User Testing
     Sprint 4 - Final Game State Testing


Game Engine

Entities and Components

     Status Components
     Event System
     Player Animations Implementation

Level Editor

Level Saving and Loading

Status Effect


Defunct

Development Resources

    Getting Started

Entities and Components

    Level Editor (Saving and Loading
         Multiple Levels)

    Service Locator

    Loading Resources

    Logging

    Unit Testing

    Debug Terminal

Input Handling

    UI

    Level Saving/Loading

    Status Effects

    Animations

    Audio

    AI

    Physics

Game Screens and Areas

    Terrain

    Concurrency & Threading

    Settings


Troubleshooting

MacOS Setup Guide

Clone this wiki locally