Radial Game Menus: Check the Movement Behind the Circle
Radial game menus involve more than a circular layout. A 2009 Wii Remote study separates task speed, selection errors and the extra steps of submenus.

Follow the action after opening the menu
Radial game menus arrange choices around a center. To understand one, follow the whole action: open it, find an option, confirm it and return to play. The circle shows where choices appear. The controls determine how you reach and select them.
Imagine a fictional spaceship-repair game. You select a sealant tool, then point at a crack in the hull. A menu comparison should include that return to the crack. Timing only the moment when the tool lights up would leave part of the action unmeasured.
Keep the older study and its sample visible
Chertoff, Byers and LaViola’s 2009 study compared six Wii Remote menu conditions in counterbalanced order. Eighteen of twenty university participants were analyzed after records involving lost data and difficulty seeing red highlighting were excluded. Each task required five correct tool selections and applications.
A repeated trial can show how the same person handles several versions. It does not turn repeated actions into additional independent players. For our invented repair game, keep each person’s practice history beside their results, especially if they learn where a frequently used tool appears.
Separate task speed from menu selection errors
Without submenus, radial menus produced faster task completion than linear and rotary menus. With submenus, completion-time differences were non-significant. The flat radial-versus-linear error comparison also missed the adjusted significance threshold.
An average completion time and a count of wrong selections describe different parts of an encounter. In our repair example, a quick choice could still equip the wrong tool. A correct choice could be followed by a slow return to the hull. Record both before deciding what to change.
Look at the movement as well as the shape
The study’s radial menu opened near the cursor, the linear menu stayed at the bottom, and the rotary menu used wrist rotation. These implementations changed more than visual arrangement.
Consider two proposed versions of the repair menu that both look circular. One moves a highlight when you press a direction. Another asks you to point directly at an icon. Copying the screenshot would not reproduce their selection rules. A meaningful comparison needs those rules written beside the layout.
Give menu depth its own comparison
For an original prototype exercise, list the route to one tool. One version might expose sealant immediately. Another might require choosing Repairs, then Hull, then Sealant. Count the steps, and note whether backing out returns to the same place. These are invented interface paths, not measured outcomes from the study.
Ask a tester to find a named tool, use it on a named target and then choose a different tool. Log wrong selections and the complete action time separately. Keep icon size, target and starting position steady when investigating one change. A preferred appearance can be recorded with its own question.
Check the task before borrowing a conclusion
The experiment used a fixed-view selection task. Performance during an actual game remained untested.
A moving spaceship encounter would add other demands. The crack might drift across the screen, another warning could appear or the player might need to cancel the repair. Those possibilities call for another comparison. Start by naming the action you want the menu to support, then check whether the evidence covers that action from opening the menu through returning to play.
Keep exploring
Sources & further reading
- Chertoff, Byers and LaViola (2009): full original study ↗
- University of Central Florida: record for the same paper ↗
Have a correction? Tell our editorial team.