Force Sensitive Resistor

Discovering a new biometric technique with Pete Collier

Feature by GamesIndustry International Contributor

Published on June 15, 2011

What this new data output had provided was a means for me to sell the concept to my colleagues at Bizarre. If I had this Newton force data outputting in real-time from the FSR surely this could be visualised with a line graph? If recorded alongside someone playing our current games (at the time - Blur and James Bond: Bloodstone) we could determine the game-play intensity felt by the player when playing our games. This, I felt, would be really useful because at the time we had excellent resources gathering quantitative data and game metrics providing qualitative data but this would provide an extra dimension.

So I jury-rigged the FSR to a 360 controller and the Arduino to my netbook with it running the Newton Force script in the SDK. I have to say, it all looked pretty awesome in its nerdiness!

It drew a small crowd when I showed the FSR in action. I don't think many game developers can resist mad experiments so it was a successful demonstration. Everybody was pretty excited at the potential and interested in exactly how useful the data could be. We discussed other potential ways of visualising the data, Chris Pickford (now super developer at Jagex) and Michael Evans (our Tableau man) were convinced we could run the data through Tableau and get some really interesting overlays on our maps. So the next step was some further pillaging of clever coder brains. Two were to become my absolute heroes - tools programmers Ken Macleod and Jamie Hales - Jamie for joining me on this mini-project and Ken as his manager for giving him time in his schedule to do so!

Jamie was quick to write an application that communicated with the FSR. He connected to the Arduino via a COM serial connection and exposed variables in a debug interface that allowed tweaking of the sensitivity values. This allowed them to be placed in a range that was attuned to a natural gripping of the pad. Jamie's program then communicated this data via a TCP/IP connection to the game, overlaying a graph showing the current sensor input value in a vertical bar, and a graph showing the input history for the last X seconds. The game then used its logging system to log the sensor values in a database as a per-frame and per-second average. This was logged alongside other game data such as health, position etc and allowed visualisations showing the mapping areas where people were gripping the pad the hardest.

Being able to tweak the sensitivity of the data proved to be critical. It was much more manageable in this more reasonable range rather than spiking so drastically second to second. By this time Mike had set up Tableau ready to take the data and visualise it. The harder the player squeezed the pad larger circles would be drawn along with a deeper shade of red. Because we were getting second to second data from the sensor a happy bi-product emerged where we could see the player's path through the level. Of course what we were capturing from the player was very much open to interpretation as to exactly what emotion/s we were capturing by the player squeezing the pad. But intriguingly what we were getting through from the map overlays appeared to match up with where we expected the intense player stress to be; fire-fights, tricky track sections on racing levels. Not only that but we were getting granularity in the data, seeing a build up in stress levels and a come down from events. What we appeared to be getting was an emotional trail through the level. This was incredibly useful to see if you were aligned with your design requirements for the level regarding pacing and beats. Here is an example of one of the images we generated, click the links to see further hi-res examples:

For me this was a fantastic conclusion from where I had been sitting on the couch a few months before. It was a great feeling taking a spark of an idea and running with it to fruition. Not only this but working together with the people that got wrapped up in the journey along the way made it immensely satisfying. Our industry is full of passionate, very clever people who love little experiments like this one. So if you've ever held back on an idea before, I encourage you to run with it next time and see where it takes you!

So you may be wondering what became of the project? Well I'm sure some of you may be aware of this technique popping up in other peoples list of biometrics techniques. Hell there may have been even before I did this experiment back in early 2010. I certainly couldn't find any at the time but on looking recently I've found examples like this presentation from early 2009.

Right there on slide 25 at the bottom of the page I noticed pressure sensor. So I think I was very likely beaten to the punch. Not only that but the technique certainly has its flaws too, people hold pads in different ways, certain groups of people might not even react to pressure by tensing up. As with all data gathering this would need to be combined with other biometric techniques to corroborate perceived trends.

I took my findings to someone who I thought may be interested in the project; Graham McAllister over at Vertical Slice. They are experts in measuring player experience and use biometrics extensively. He was interested to hear about the project and we remain in contact now. This is a good point to end this story on because it demonstrates my final point. I wouldn't say I've got anything materially out of this project; sadly the whole rig now sits in a plastic bag in my wardrobe! But what I did gain from it was huge when it came to relationships with people. This project brought people together and what is greater than that? I established new relationships, cemented current ones and learnt the power of positive energy and perseverance; people naturally gravitate to these things. It's funny how far an idea can take you if you follow it through and I look back on this mini-side-project with great fondness. I hope you enjoyed reading about it.

Read this next