By Anthony Stonehouse
User interface design in games differs from other UI design because it involves an additional element — fiction. The fiction involves an avatar of the actual user, or in this case, player. The player becomes an invisible, but key element to the story, much like a narrator in a novel or film.
This fiction can either be linked directly to the UI, partly, or not at all. There seems to be a growing debate with which is more immersive for the player. One side of the debate is that UI elements that sit within the game world, and therefore ‘viewable’ by both the player and avatar, are the more immersive and provide a more seem-less experience. However these elements are often clunky and inherit many restrictions. They need to strictly adhere to to the fictional narrative and adopt the visual design of the game’s art direction. They also sit within the geometry of the game’s perspective, often rendered on a 3D plane that can reduce their legibility.
Erik Fagerholt and Magnus Lorentzon explore these theories in their thesis for Chalmers University of Technology titled: Beyond the HUD — User Interfaces for Increased Player Immersion in FPS Games. They introduce the term diegetic interfaces for UI elements that exist within the game world that the player and avatar can interact with through visual, audible or haptic means.
I believe well executed diegetic UI elements do benefit the player by enhancing their experience of the narrative. However, they are more difficult to implement because the inherit restrictions.
Metro 2033 uses a complete diegetic UI with no HUD elements to help to support the game’s narrative. It does seem to run the risk of frustrating the player though slow response times but perhaps this forms part of the game mechanic, I have yet to play the game.
These elements can either exist within the geometry of the word, or on the camera/screen for the player. Fagerholt and Lorentzon use the term Spatial to define elements of the UI that sit in the geometry and Meta to define elements that exist on the camera.
Fable 2’s dotted line that guides you to locations marked on your map is an example of a Spatial element, it exists in the game world but the avatar doesn’t interact with it. It ensures a more seamless experience, avoiding jumping out to a map screen as often.
Lastly there are the traditional non-diegetic UI elements. They have the freedom to be removed completely from the game’s fiction and geometry and can adopt their own visual treatment, though often influenced by the game’s art direction.
I think these elements are best used when the diegetic, meta and spatial forms provide restrictions that break the seamlessness, consistency or legibly of the UI element. World of Warcraft has a pure non-diegetic UI, that adds nothing to the fiction. It does allow the user to completely customise though, hopefully ensuring a familiar experience.
Here are some visual representations of these concepts that have been adapted from Fagerholt and Lorentzon’s thesis.
For further reading; Marcus Andrews from DICE examines recent games using these theories from Fagerholt and Lorentzon in this article posted on Gamasutra. Michael Grattan, a senior at the University of Souther California writes a response to the article on his blog. Dave Russell has also written an article on his blog.
New physical interaction methods make their way to the PS3 and 360 this year, called Move and Natal respectively. These technologies promise to challenge current best practice in game UI design and generate even more innovation in the area. As a designer currently working in web design I’m almost jealous of the levels of interaction plus the addition of audio and haptic elements available in game UI — while I’m still refined to users with an outdated keyboard and mouse. Web does offer other challenges and more variety in content delivery though.
In the virtual world of internet and information technology nothing can be said to be impossible. Things that were thought to be impossible some years back have now become a reality.
ReplyDeleteUser Interface Design