Skip to content

Sprint 2 Character Design User Testing

37JackHirst edited this page Oct 13, 2021 · 1 revision

User testing was conducted with 15 participants to gather feedback regarding the new character design via a questionnaire. Responses to the current design as of Sprint 2 were essentially positive, with most respondents agreeing that the design style fit the sci-fi aesthetic we intended, with a large proportion of users also agreeing that it is fairly representative of a computer virus. Users also provided feedback for future improvements and iterations to the design. Not all participant responses have been displayed below, but those shown are quite representative of the types of responses gathered across the user testing group. The testing plan for this user test can be found here.

Focus aspects of testing:

  • First impressions
  • Suitability of the design for the theme and game narrative
  • Design recommendations

Questionnaire Items:

  • Q: What are your first impressions of the character?

User 1: He looks like a sort of robotic humanoid insect or bug. I like the animations and movement of the limbs.

User 3: Intimidating

User 10: That the main character is something that will attack other players/characters within the game. I personally really like the design and think it looks as though it has potential to demonstrate some interesting movements based on its length and joints.

User 11: Looks pretty cool, like an enemy almost because of its red eye. Kind of looks like those insect-aliens off of rick and morty

User 12: robotic eyeball head is cool! but might be a bit confronting if your target audience is young kids though.

The general consenus around users' first impressions was that the character design was scary and intimidating, which is partly what we desired to achieve with the character. Though this character is the player and takes a more protagonist role as you run from an enemy antivirus void, inherently the character is actually the bad or evil one in the broader context, being the computer virus. Thus, based on users' first impressions we were able to achieve a design style which somewhat fit the character's broader identity as a computer virus.

  • Q: The general theme of the game is sci-fi inspired. How well does the character's design fit the broader theme? (1: Not at all, 5: Very well)

In regards to broader theme and aesthetic of the game, most users agreed that the character design fit the sci-fi aesthetic we were trying to achieve. All responses rated a 4 or higher in regards to the character design's fit or suitability into a sci-fi themed game. This feedback is helpful as it informs us designers that the player is a good indicator of the desired design style of the game.

  • The character is supposed to be representative of a computer virus. As the main player, you are running from an antivirus void that seeks to destroy you. With this in mind, how suitable do you believe the design of the character is? (1: Not suitable, 5: Highly suitable)

In regards to how well the character design represents a computer virus specifically, as opposed to just being appropriate for a sci-fi game, over half of the participants, i.e. 8 of 15, agreed that the character design suits a computer virus. This indicates that stylistically, the choices made towards the character's design are fairly applicable and understandable to demonstrate that the character is a compuetr virus. Other remaining participants were not as fully convinced that the design is suitable, however, none rated the design below a 3, which indicates that to some extent, the design style is still quite representative and draws connections to a computer virus, and is not entirely inapplicable.

  • Q: Please explain why (in regards to the previous question).

The following are some justifying responses from users who rated 5 on the scale:

User 9: _The design of the character is suitable to represent a computer virus because it's "limbs" almost mimic the structure of a virus itself. The colours red and black give negative connotations. _

User 10: I picture a virus spreading and having "tentacle" like characteristics. This character is as I would imagine an evil sci-fi virus to appear.

User 7: The design seems to bring out a sort of malicious look (mainly because of the colour scheme and unhuman like qualities). It is definitely obvious that it has relevance to science fiction, and with context it can be seen that it could be interpreted as a virus too.

The following are some justifying responses from users who rated 4 on the scale:

User 2: It looks like the combination of the terminator with a praying mantis this vibe is pretty on point and most people my age will easily make the connection.

User 3: A computer virus to me is something I should be afraid of. This intimidating first impression is pretty good to be a representative of a computer virus.

User 8: The red colours spells Virus

The following are some justifying responses from users who rated 3 on the scale:

User 4: _The villain looks more like a robot/cyborg than what I would imagine a computer virus to look like. _

User 11: It's definitely sci fi, I think it depends on the design of the "antivirus void" and other designs but it feels like it could be a bit more sci-fi than anti virus

  • Q: What recommendations do you have that could improve the design of the character?

User 2: Maybe add some binary or circuit tattoos on the characters to show it is more computer-y

User 3: Maybe show more exposed wires to make it more robotic and sci-fi

User 4: I would probably imagine something more like a real-life virus

User 5: Make it a bit more erratic, less symmetrical if you’re going for a virus

User 10: Colour changes on the "eye/face" to show what "mode" it is in.

Users have described some useful design recommendations which could be taken into account for future character iterations. Much of the responses seem to indicate that more computer virus specific indicators should be included in the design, such as adding binaries, wires or real-life virus-esque components to the character, as opposed to suggesting a full redesign for instance. These evaluations and suggestions can be helpful for the design team as iterations and improvements towards the character continue to be made.

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