There’s a project I’ve been following for a while, simply called v r 3.
It’s the most recent work by Pippin Barr, one of my favorite game people. If you don’t know who he is or what he does, well, Google can help you understand his approach to games better than my words would ever do. You’ll find some (very) amazing stuff on his blog, I promise. </fanboying>
So, v r 3. With this project, Pippin wants to create a digital exhibit of all the water particles available for Unity, including third-party assets. Which is interesting on many levels, especially if you read the flow (hey, a pun!) of thoughts he explained in his blog posts. He’s also following the design process by regularly posting on Facebook and Twitter about his progresses, development issues, and such. So when he recently announced that v r 3 is close to be completed I was sad, because this means no more tweets or posts about v r 3. No more water misbehaving in .gifs. No more funny nor clever comments by other game designers/followers about it. No more reflections (another pun!) regarding this digital museum. As soon as v r 3 will be finished, it will leave a hole in my everyday habits, which included looking at Pippin’s progresses with this project. There will be more contents from him about future works, I believe. But v r 3 will be done and gone.
It’s a very egoistic way to look at things, I realize. For my personal amusement, I desire that someone who has spent a lot of effort in working on a thing just doesn’t finish the said thing. “The show must go on”, to some extent a legacy of our times: when you have something going on you are tied to your audience. If they say “Continue!” you have to. Many thoughts about spectacularization come to mind: talent shows, YouTube, Twitch, early access, game walkthroughs, livetweeting, etc. There’s a whole thesaurus for that. The argument could indeed extend in many directions, as it’s really broad and complex. Yet, my aim now is to ponder a small area of that topic because I see an artistic performance going on here, and feel like a spectator.
Something (Barr, 2017)
Curious about game making that becomes a performance, I looked up online for performative game development, and found an intriguing GDC talk dated 2014 by Vlaambeer developers Rami Ismail and Jan Willem Nijman. I understood that they analyzed the process of developing a game (Nuclear Throne) in front of an audience, livestreaming their work sessions and receiving constant feedback from the community. Something really close to what Pippin is doing, yet not exactly the same. v r 3 is most likely not going to be sold, so there is no monetization involved. Its audience is mostly composed by fellow game devs/critics, not players-customers (an oversimplified definition for the sake of understanding). Lastly, the performative act differs: instead of a livestreaming we have here a trail of bits in the form of Tweets/Facebook posts. So there’s a a posteriori kind of performance, where the artist shows only some selected part of his act to the audience. Hence the meaning, and the possible interpretations of the whole performance are different. Mh.
This is a reasoning that applies with other events too, I guess. Football games, extraordinary events, TV shows…whenever someone posts on social media maybe? And when does it become a performative act? Should there be awareness by the actor?
I don’t know. Not even trying to make a point, to be honest. This is just me giving perhaps too much thought to an event.
Still, I’m pretty sure Pippin is already aware of this, and it has been intentional: he once admitted that his very presence on social networks is an act of performance to some extent (and isn’t it true for all of us, after all?).
But damn! I’ll miss that water nevertheless.
V r 3 is out, downloadable from Pippin’s blog. You can check it out here.