Last week’s discussions in our video game community revolved around practical challenges and innovations in game development. There was a strong focus on optimizing game performance, particularly in maintaining smooth interfaces on consoles. Members also explored the implications of new technologies like eye tracking, which led to unexpected gameplay experiences. Accessibility and design were other key themes, with developers sharing strategies for creating readable HUDs from a distance.
This Week’s Hot Topics
Keeping UI snappy at 60 fps on console
Developers are diving deep into techniques for optimizing user interfaces to run smoothly on consoles at 60 frames per second. This topic is crucial for enhancing player experience and maintaining immersion. Read more here
Eye tracking betrayed my stealth run
Gamers and developers are sharing stories about how eye-tracking technology can affect gameplay, especially in stealth games. This discussion highlights the unexpected ways new tech can influence game design. Read more here
Readable HUDs at 10-foot distance
Creating HUDs that are clear and readable from afar is a key design challenge. This thread discusses best practices and innovative approaches to ensure accessibility and player comfort. Read more here
Thanks for keeping up with the latest discussions. Looking forward to seeing more valuable conversations in the coming week.
In a stealth prototype, eye tracking kept “betraying stealth” by tagging enemies when players just peeked; switching to a 250 ms dwell-to-confirm and a about 5° gaze deadzone around the reticle stopped most false positives. It does add a tiny bit of latency, so we only enable it in stealth states and expose a toggle for accessibility. If you’re tuning filters, Tobii’s notes helped us: https://developer.tobii.com/ (turns out eyes love to snitch).
Had the same “betraying stealth” issue; on console we stopped using gaze to tag and only used it to bias selection by about 20%, with a button tap to commit — false positives vanished and the UI stayed 60 fps. Also filter out saccades by ignoring gaze velocity spikes (>300°/s) so peeks don’t register, @dlawrence91. If you need accessibility, add a slow focus ring instead of instant tagging to signal intent without giving you away.