GDC Advice for young first-time attendees, 2017 edition

I remember when I was totally bewildered and disappointed at my first GDC. Since everyone is doing little advice columns / threads on Twitter, I thought I'd chime in with my own shit. This is a bit of advice and info primarily for young people (ages 15-30?) going to GDC for their first time:

• If you are a man, assume every woman you meet is a developer. Never ever ask a woman whether she is "in games" -- don't be so fucking basic, of course she works in games, she's at GDC! Women at GDC are not your mom and they are most definitely not your girlfriend: women are your colleagues. The secret is to understand women as skilled experienced professionals. Instead, you could ask:
• "What are you working on? What's your current project? What was your last project?"
• "What do you think about [area of expertise]? What are your thoughts on [related game]? Did you go to [related GDC session]?"
• "Go to any good talks? See any cool stuff? Go to any cool parties last night?"
• This is a business conference. If you're not here to "do business" or sign some deals or have meetings, then the conference is going to be kind of boring, and it'll be up to you to entertain yourself. On the other hand, if you do have something to show, this is a great time to try to talk to a publisher about a deal / getting a console devkit / getting some VR money.
• When requesting business meetings / making appointments / approaching people, err on the side of doing it. Awkward first meetings are expected at GDC. Assume that you and your project are worth their time. If the meeting isn't a good fit, then let them decide -- they will quickly wrap it up, they're used to it... but also, use your judgment and don't annoy people if they don't look receptive.
• Business cards exist to end conversations politely. If you ever want to leave a conversation, just make an excuse, offer your card, and then leave. Everyone knows this is bullshit, but the effort you put into this bullshit ironically indicates that you do give a shit.
• If you ever have to choose between going to a talk vs. hanging out with people, you should usually choose to hang out with people. All sessions are recorded, you can always just watch it later or read a summary. (Personally, I've never regretted missing a talk.)
• Stay aware of how tired you are, take short naps in the Mild Rumpus area or the park, and remember to eat enough. If you're hungover, you'll probably just have to drink a bunch of immune boosters and coffee, and try to hold it together until Friday.
• If you are manning an IGF or Alt.Ctrl booth, it is totally OK for you to put up a "back in 30 minutes" sign and take a break, or maybe ask a friend to cover for you. Some people even just setup a looping video trailer and leave. The drawback is that you might miss some possible press coverage and interview opportunities.
• Lunch recommendations near Moscone:

On cs_ppc, "school maps", and the politics of remediating / re-mapping real-life places

[ cs_ppc.bsp ]

by: Walnut<+>Warrior

for: Counter-Strike pic.twitter.com/P8XWw0ppuD

— .BSP (@dot_bsp) February 18, 2017

The excellent @dot_bsp Twitter account randomly tweets screenshots from different levels in various Goldsrc (Half-Life 1 engine) games and this February 18th tweet about "cs_ppc" by "Walnut<+>Warrior" really caught my eye and got me thinking.

cs_ppc is really clean and well-built with good height variation and composition. The shapes flow into each other very well, and the scale seems very realistic. On a technical level, there's also clever use of masked transparency textures to complicate silhouettes with fewer wpolys, centering around a pretty huge atrium with a lot of open sight-lines everywhere -- this kind of craft means it was built relatively late in the Goldsrc cycle, when high polycounts and heavy use of custom textures were the norm.

This level has relatively little cover and probably plays strangely for Counter-Strike, but the author clearly prioritized real-life resemblance over gameplay. It made me wonder about the level's relation to the real world. Fortunately, when I loaded cs_ppc.bsp into the engine, I discovered that the author embedded a commemorative plaque at the very front of the level. It is definitely intended as a recreation of Peter-Paul-Cahensly (PPC) vocational school in Limburg, Germany.

So what?...

Apply to STUGAN, a bucolic game design residency in Sweden

Stugan is a residency program for indie game designers to hang out together in a beautiful cabin in the Swedish countryside and work on their stuff.

They call it an "accelerator", but don't that word dissuade you. If you consider yourself more of an artist than a businessperson, it's OK, they have hosted plenty of artsy experimental designer types too.

There's been some understandable criticism of Stugan's arrangements: Like many artist residencies and opportunities, there are certain barriers to access -- you're basically foregoing paid work for a few months as a sort of working holiday, and you'll need existing funds to travel to Sweden somehow.

However, I think it's worth noting that many art residencies often have hefty application fees and/or require attendees to pay for their own room and board. Compared to that inaccessible norm in the (messed-up) art world, Stugan is a somewhat reasonable deal that's firmly in the middle of the pack for art, and extremely rare in video games funding.

Of course that doesn't mean it's "accessible" -- so if you're interested in Stugan but don't necessarily have the resources, you might want to do some research into funding sources for artists, you might be surprised. Also, if you're a student, talk to your school -- many institutions offer travel grants for programs like this.

Or just cross that bridge when you come to it? You can apply to Stugan for free. Good luck.

Thoughts on Steam Direct

There's news today that Valve wants to transition away from Steam Greenlight, which is a crowd-source voting system where you pay $100 *once, forever* to let users vote for your games on Steam, and after a certain vote threshold you can put each game on Steam.

The new system planned for roll-out in Spring 2017 is something they call Steam Direct, where you pay a "recoupable" (whatever that means, here? Valve doesn't say) $100-$5000 fee *per game* (they haven't decided the actual rate yet) instead of going through the vote process. They want their storefront to seem more open, but they are also cautious about public perception of "shitty games diluting" the Steam store.

A lot of my thoughts are basically a repeat of past criticism of the Steam Greenlight fee, years ago, except this could be much more expensive and much worse? Here are my reactions:

"Press Forwards" and the pleasing death of agency

Trackmania games have very robust track editors that let the community build and share custom tracks very easily. This ease of use and immediacy allows new track genres to emerge organically from "grassroots" player communities, a practice that I've characterized before as "local level design" -- it is not just new ways of using the game's building blocks, but it also suggests entirely new ways of thinking about the game itself.

The "press forward" genre (or "PFs") is one of my favorite examples of emergent level genres. Instead of challenging players to hone reflexes and maneuvers on a track, a PF beckons the player to simply hold down "forward" as a mindbogglingly complex track swirls around them. Through no skill of their own, a player ends up executing amazing stunts -- spinning 1080 degrees in the air before barely grazing a ramp in just-the-right-way to land perfectly on the track below. If the player makes any kind of choice, like letting go of the "forward" key, or (god forbid) turning left by 0.1 degrees, the consequences are often fatal.

There's a famous saying that "writing about music is like dancing about architecture." PFs are maybe the closest thing to actually dancing about architecture. Sometimes it feels like the track architect wanted to impress you, sometimes they are making a joke, sometimes they want to scare you. The PF frees us, to be more open and receptive to the ways that architecture speaks to us as we traverse it.

Notably, this is a track type that resists the dominant mode of playing Trackmania. It is a video game world that basically punishes you for even trying to wield any agency or control. When virtuosity is guaranteed, how many humans can resist the urge to fuck it up?

Teaching, Spring 2017

This semester, I'm teaching three game development classes. Here's a bit about each one:

• "Intermediate Game Development" at NYU Game Center. This is maybe the 10th time I'm teaching the class; it's a mix of Unity, source control, and 3D art. It's intended for 2nd / 3rd year undergrads in the undergraduate game design program, to give them enough awareness of different tools so they can start to focus their practice in future classes. Teaching it is always challenging... some students double-major in computer science and think the coding lessons are too easy, but for many other students, this is only the second code class they've ever taken. That said, the main point of this class is that code is certainly important, but making a video game involves much more than just code.
• "Virtual Reality Studio" at NYU Game Center. This is the second time we're running the VR class, and it's kind of exciting because the department is starting to equip some state-of-the-art Vive workstations. Last year, the lack of motion controllers and room scale capability really limited a lot of project ideas, so hopefully we'll be able to accommodate the student demand better. What's challenging about teaching this semester is that there's a lot of new material: I have to figure out how to teach a Vive workflow AND I'm also trying to mix-up the theoretical readings more. Last year, we spent a lot of time reading Hamlet on the Holodeck, which was helpful, but also way too concerned with narratology for a class that doesn't focus on storytelling.
• "Recursive Reality" at Parsons School of Design, Design and Technology. This is the fourth time I'm teaching this VR studio class at Parsons, which differs greatly from the focus at NYU -- here, at least half the students are interested in VR for film / installations. The equipment situation here is a bit less ideal, because no desktop VR HMD is compatible with the school's fleet of Mac workstations. So instead, we're focusing more on mobile VR like Cardboard and Gear, which actually works well for a lot of the students' design goals.

Queer Game Studies, "On FeministWhorePurna and the Ludo-material Politics of Gendered Damage Power-ups in Open-World RPG Video Games"

For the upcoming book Queer Game Studies (2017), I contributed a chapter on the "FeministWhore" scandal in the game Dead Island. It is a "ludo-material" political analysis, looking at gameplay as expressed by source code, intended for general audiences. Here, I'll talk a bit about the ideas and process behind writing the chapter, and then briefly summarize the main argument.

First, to remind you, here's the reporting on the scandal back in 2011 from Kotaku:

One of the unlockable skills for Dead Island leading lady Purna allows her to deal extra damage against male victims. It's called Gender Wars in the game, but the original skill was named "Feminist Whore."

There's a lot to unpack here, and one goal of my chapter is to expand what we mean by "representation" in games. Currently, whenever we criticize a game character for its politics, such as a racist or sexist stereotype, we tend to focus on the character art, animation, writing, and voice acting. Why not expand representation to encompass the richness of the entire game experience and game engine itself?

My analysis follows Mark Sample's excellent "Criminal Code: Procedural Logic and Rhetorical Excess in Videogames" in focusing on the procedural politics of game mechanics and balance, and comparing that to the systems as intended from the source code. FeministWhorePurna is an ideal case study: it was a contemporary event with modern game engine architecture and a player / modder community that practically did the gameplay and forensic analysis for me already. (I also forced myself to play a bit of Dead Island to verify everything.)

You'll have to checkout the full book from your library, or buy it, or whatever, to see the full essay, but I'll try to briefly summarize the argument here, and in more game developer-y language as appropriate:

RIP, Vine.

The short video service Vine shut down today. I know a lot of game designers and devs who used Vine to document and share their work, and we're all pretty sad to see it go.

Below is my only claim to Vine fame -- nearly 2,500,000 loops before Vine died. This was a vine of the first sex game I ever made, called Hurt Me Plenty.



After I posted it, it quickly jumped to 1,000,000 loops within a few days. I was stunned. I had never really made anything "viral" before, and it only took me like 10 seconds to record that clip! I mean, numbers and view counts mean very little in the end, but when you haven't done much, even "very little" can be a strong boost to your self-confidence.

The breathtakingly thirsty response to this vine convinced me that there was an audience for my work, and that I should see it through, which is exactly what I needed to hear.

So thanks, Vine... rest in power.