Friday, August 25, 2017

Road trip sketches; notes on extracting and visualizing Half-Life 2 levels in Maya


So I'm working on (another) article about level design in Half-Life 2. I chose the d2_coast03 map of the Highway 17 chapter, which is the first real "coastline" road trip section of the game, and is probably the most successful. Look at how big and open it is. Would you believe this is a map in a game celebrated as a meticulous roller-coaster? In my mind, it's contemporary with a lot of vehicle-based first-person open world game design trends that started around the same time in 2004, and they even pulled it off in an engine architecture that's still kinda based on Quake 1.

Friday, August 18, 2017

Teaching, Fall 2017

As mentioned before, I'm going full-time with NYU Game Center starting this September. For this upcoming fall semester, I'm going to be teaching three classes and advising an independent study:
  • Intermediate Game Development (2 sections). This is a required class for the BFA Game Design major where we focus on using Unity in a 3D context, refine C# code fluency, learn about using Maya and Substance Painter, and become less scared of using Git.

    This is my fourth year of teaching it. This year, I've changed the final project to focus on studying and cloning a game. In the past, the final project asked students to collaboratively formulate an original game design concept, but I noticed students would get into endless debates about the game design instead of focusing on project architecture or collaboration workflows. Since we already have dedicated game design classes that offer more support for those debates, I now feel comfortable removing some creative freedom from this class -- so we can focus more on building-up "technical freedom."
  • Intro to VR. This is a new VR-focused class we're running for undergraduates and/or people who aren't so familiar with code and 3D. At Game Center we remain cautious about investing too much in something still fundamentally unproven like VR / AR, but we still want to support students who want to explore it. Unlike our graduate-level VR Studio class which assumes technical proficiency in code and Unity, this class will offer more of a scaffold into working in 3D and VR. We'll also dip our toes into talking about VR culture and critical theory as usual, but probably stop short of discussing Baudrillard and phenomenology.
  • Level Design (independent study). Years ago I used to teach a modding class with a level design focus, but one day I noticed students hated using the Source Engine, and we never identified another decent engine / toolset for level design. We also needed a good base game to design more levels for, which is why we can't switch to Source Engine 2 -- DOTA2 isn't exactly relevant for learning generalized level design practices. At least half of our students also use Macbooks, which basically wither and die under Unreal 4, so that's out of our reach too.

    But then a few months ago, some students approached me to advise an independent study on level design. This format is more like a seminar / reading group instead of a full production-oriented studio class, and we will focus more on theory than construction. Hopefully this will work out better than the Source modding class!

Wednesday, August 16, 2017

StoryCode August 2017 Forum at Film Society, Lincoln Center, NYC


Next week on August 22nd, I'll be giving a presentation for StoryCode, a local community group focused on immersive media and storytelling technology. As one of the few game designers invited to present in their lecture series, I thought I'd try to explain how video games conceptualize narrative, interaction, and expression, to an audience that maybe doesn't play that many video games -- or at least, they don't play what we consider to be the state-of-the-art narrative games.

I'm also being required to talk about my games and present them as case studies, even though my games don't fit neatly into the "narrative game" genre. I think I'll probably just open my actual project scenes in the Unity editor and mess with my scene setup and code, which usually entertains people well-enough? It'll also be a short primer in foundational ideas like immersive fallacy / procedural rhetoric / platform studies, and the idea that production value and paratext amount to their own kind of "story."

The presentation is free and open to the public, but I believe you're encouraged to sign-up and RSVP via this Meetup page or something.

Tuesday, August 22, 2017 @ 7:00 PM
Elinor Bunin Munroe Film Center @ Film Society of Lincoln Center
144 West 65th Street, New York, NY (map)

Saturday, August 12, 2017

Go West young Slime Rancher, and grow up with the country

This post spoils some mechanics and game systems in Slime Rancher.

One in-game day in Slime Rancher, I found a rare "quantum slime", a creature that pooped out "quantum plorts" that I could sell for a lot of in-game money. To make a huge profit, I intended to raise a few on my ranch in captivity, and then collect their precious poop to sell in the market.

To maximize your slime poop plort yields, you're supposed to feed your slimes as often as possible. Every slime has a certain diet (vegetables, fruits, or meat) and a specific favorite item. Quantum slimes eat only fruit, but prefer a special fruit called a "phase lemon". To get phase lemons, you have to bring back a phase lemon from the wild, plant a phase lemon tree, wait for the fruit to mature, and then shoot a different fruit at it (like a cuberry, or a mint mango) to pop the phase lemon into existence. Compared to other crops, it's unusually labor intensive to cultivate and harvest phase lemons.

This is where Slime Rancher's other big system comes in, a cross-breeding mechanic that allows you to merge two slime types together. If you feed a slime with the poop from another slime, it will become a hybrid "largo" slime that inherits both types' diets and other properties, and it will poop out both types of plorts at once when it eats something. Two poops for the price of one! When you do this on purpose in Slime Rancher, you feel like a genius.

Monday, August 7, 2017

Recent developments in queer game studies, Summer 2017

Here's a few recent updates in the """discourse""" within the exciting world of QUEER GAME STUDIES!!!

First, there's a new call for papers in the long-running Game Studies journal -- this time the focus is on "queerness and video games."  The full CFP is here. If you're a student or academic (or anyone with a perverse tolerance for academic citation styles) then you should consider sending-in some original scholarship and/or maybe trim your thesis into a submission; full articles of 6500-8000 words are due by December 31st, 2017. Good luck!

Next, Miguel Sicart wrote a piece about "Queering the [Game] Controller." Sicart, as far as I know, doesn't identify as queer, so some may argue he thus cannot really "queer" anything -- so please allow me, a certified gay person, to try to unpack some of his ideas here:

Thursday, August 3, 2017

Cleaning out some old Black Mesa archives for PC Gamer


Here are two old level design illustrations I did for a PC Gamer feature on level design in Half-Life 1, quite a few years ago. In the overview map, I focused on the construction of the Black Mesa Inbound chapter as a whole; and in the more focused cross-section, I concentrated my analysis on a single setpiece, the "shark cage" sequence in the Apprehension chapter.

(In the PC Gamer print version, the diagrams are annotated and labelled, but the image files I submitted were blank like these. I forget which issue it appears in. If you're interested in this topic, you can watch my Practice 2013 talk on this stuff to get roughly the same material.)

Anyway, here's a bit about my process and intent with these illustrations:

Monday, July 31, 2017

new tool: Yarn Weaver


I'm working on a game that uses the excellent Yarn and YarnSpinner narrative toolkit for Unity. For this project, I'm also collaborating with a narrative designer -- unfortunately, the Yarn editor doesn't actually have a play mode or a testing mode built into it -- which makes it difficult to collaborate, because the designer can't even run through the Yarn scripts without downloading the entire Unity editor and project source! What if she just wants to test a short conversation script or two?

So, I basically duct-taped the YarnSpinner example setup to this excellent UnityStandaloneFileBrowser (for native file open dialogs at runtime) to make a very small simple tool to open and run through Yarn scripts. It can display your text, parse all your variables, and render up to 4 choices.

I call this tool "Yarn Weaver". The project source files are on GitHub under MIT License, or you can download Windows and Mac OSX release builds here. I hope it's useful for people!

Saturday, July 29, 2017

Toward an honesty of pixels: on Final Fantasy 12 HD and Quake 3 Arena

combined screenshots from Final Fantasy 12 (PS2, 2006) and Final Fantasy 12 HD (PS4 Pro, 2017)
You either love or you hate Final Fantasy 12, and you either love or you hate the somewhat recent trend of remastering old games to squeeze a few more drops of profit out of them.

I'm currently playing the remastered PS4 version of Final Fantasy 12 ("The Zodiac Age") and it's still the same old nonsense story about fantasy imperialists and magic crystal macguffins. One thing that surprises me, though, is how this remastered version actually looks worse -- it went from the apex of PS2-era 3D art to looking like a mediocre PS3 game running on a PS4.

When it first came out 17 years ago (!), the Playstation 2 famously had very little texture memory (4 MB!) and no texture compression (!) which meant developers had to get creative. Loyal readers of this blog know of my love of lightmap atlases and UV layouts, and so I'd like to talk about how the textures for the original Final Fantasy 12 on PS2 were utter masterpieces produced under severe constraints -- cramming so much detail into these small texture sheets, down to the pixels...

Saturday, July 22, 2017

announcing: No Quarter 2017 on November 3rd in Brooklyn

poster by Sophia Foster-Dimino
A short while ago we announced the date and lineup for No Quarter 2017: it's on November 3rd at the Starr Space Gallery in Bushwick, Brooklyn, featuring new commissioned work by Auriea Harvey (of Tale of Tales), Droqen, Pietro Righi Riva (of Santa Ragione), and Kitty Horrorshow. We'll be flying out all four artists for the show, so if you attend, you'll be able to meet them and talk with them at the event.

For more info, check out this NYU Game Center page for the event. I'd like to copy and paste my short curator's statement here though --
For 8 years now, the No Quarter Exhibition has been paying game designers to make the games they want to make, and then throwing them a big fun party to celebrate and amplify their unique voices. We claim no ownership over the resulting work — we just want these artists to speak their mind, and so we give them space and support to do that. We think it’s a pretty great deal for them, but we also get a lot out of it: their act of creation, and our shared acts of play, help strengthen our communities.

Now, we do all this at a time when many people think we should isolate ourselves from the rest of the world — but we know that’s a very destructive attitude. It’s so destructive that, for the first time in the history of No Quarter, we are temporarily suppressing our vocal and insufferable belief in our city’s exceptionalism: this year, we are commissioning only artists based outside of New York City. We believe a wider diversity of backgrounds and identities can only enrich our understanding of art and community… oh, and it helps us make better games too.
Also happening right after No Quarter -- game convention GaymerX East in NYC runs Saturday / Sunday. Sounds like a cool fun weekend to me! Not to mention that flights and hotels are cheaper in November too, it's off-peak... just sayin'...

Thursday, July 20, 2017

Paseo, devlog

the original prototype from early 2017, with a weirder style to match the artist's vibe
A few months ago, a big record label asked me if I wanted to make a short gay sex thing set to one of their artist's tracks -- for a few weeks, I thought the collaboration was going well, but then one day they just stopped answering my e-mails. Oh well, that's just how it goes sometimes...

I still kind of like the basic idea, so I'm going to replace the music and expand it to be part of the Radiator cycle. It's tentatively called "Paseo" (but the name will likely change before then) and it's about stripping, which is a popular intersection of sex and money. As a male performer, you will do strip routines and incorporate beautiful dance movements, but you also have to work the crowd and collect your tips.

Tuesday, July 11, 2017

Bevels in video games


Like a lot of digital artists today, I learned Photoshop in the late 90s in order to make awesome-looking fan sites and "professional" forum signature images. One of the Photoshop tricks I learned was the "Bevel" layer style, which embosses a faked thickness and depth onto a layer, as if it's popping outward toward / inward from the viewer.

When I first learned it, I felt powerful, like I could use Photoshop to "paint in 3D" and make my Starcraft fan forum avatar look even more professional. But then I realized that the bevel had a very specific look to it, and I started seeing that look everywhere. My astounding bevels quickly lost their sheen. To this day, the conventional wisdom in 2D game art is that you should just handpaint your own bevels, and it only takes a few minutes when you get good at it anyway.

Today in 2017, the bevel has arguably taken over 3D environment art, and like all the other game art gods, it demands labor from us. But unlike 2D bevels, there's no strong consensus on what the best 3D bevel techniques are, which means we're free to experiment...

Thursday, July 6, 2017

On first person one-roomers and grass games

old WIP production still from an early version of The Tearoom
I want to talk a bit about the formal design constraints in my gay sex games -- I don't usually emphasize this aspect of my work because it's a very game developer-y thing to care about, but sometimes I guess a little bit of shop-talk is called for:

A lot of my games have been what I'd call short form "one room" games, where I constrain the scope of the game to one room or one small area. When I first started doing Radiator 1 ("Polaris") in 2009, that constraint emerged from my frustration with working on a large international group project like Black Mesa Source, where I wasn't sure if we were ever going to finish and release anything. I wondered, could I work alone, and quickly make a short experience in a small room?

Cut to today in 2017. I've just finished and released The Tearoom, a game that takes place in one single public bathroom. Because it was so small and controlled, I could focus on the interactions and production value very tightly, and produce something with relatively high fidelity and density even though I was working mostly alone. (But it still took me like 8-9 months of part-time work to do all that! Maybe the room should've been even smaller?)

But I also don't exist in a vacuum, cut-off from the rest of video game culture. Maybe my attitude is also a reaction against the rise / dominance / golden age of open world games and walking simulator-type hiking games today? I know other designers counter AAA hegemony in different ways, like how Firewatch adopted a non-photorealistic illustrative art style, or how The Signal From Tolva focused on a somewhat sparse rocky-chunky-sculpted look. Both games feature large open world environments that differentiate themselves with talented art direction that also helped them scope better too.

However, I'm not really a good art director, and I still feel really tied to realism for political reasons, so I guess I have to differentiate my creative strategy in a different way... I specifically set my games in small man-made domestic spaces instead of trying to build huge sweeping landscapes. And even if I did attempt to build a huge landscape, my shabby default Unity 2 tri indie grass will never be able to compare with photoreal translucent Unreal grass, or Breath of the Wild's lush Miyazaki grass, so maybe that's why I don't bother. As much as I enjoy and admire all these grass games, I recognize that it's out of my wheelhouse and capability. Instead of trying to build a giant grassy forest landscape, I can rest with a decently crafted urinal and lean on that.

It might seem like I'm boxing myself in, and maybe I am, but honestly it doesn't feel that onerous to me. Grass is nice, but perhaps there's enough people making grass games already. I'm not sure if I have anything new or interesting to say about grass or trees anyway. (But who knows? Coming in 2018: gay trees)

By constraining the physical-geographical space, I think that helps me explore a wider conceptual-cultural space. One room doesn't just mean one idea? Or if it does, then for now, I think I'd rather make 5 one room games than 1 five room game, or 0.271 forest games.

Friday, June 30, 2017

The Tearoom as a record of risky business



WARNING: This post spoils what happens in The Tearoom. If you care about that, you should probably play the game before reading any further.

The Tearoom is a historical public bathroom simulator about anxiety, police surveillance, and sucking off other dudes' guns. In it, you basically cruise other willing strangers for sex, and try to have some fun without getting caught by undercover police. It's heavily inspired by Laud Humphreys' epic Tearoom Trade (1970), a meticulous 180 page sociological study of men who have quick anonymous sex with men in public bathrooms ("tearooms" in US, "cottages" in UK), along with interviews, diagrams, and derived "rules" for participating in the tearoom trade.

My game is set in a small roadside public bathroom in Ohio in 1962. Much of the game sequences and gameplay are based on Humphreys' notes (in his book, Humphreys even calls it a "game" himself) and the layout of the bathroom is based partly on diagrams from his observation reports. And while I wanted the game to be about gay history, I also wanted it to speak to how video games think of sex and violence.

This is also the most complicated sex game I've ever made. It took me ~8-9 months of on-and-off work to finish it, it has several different systems going on, so it's going to take a while to unpack the history and my intent. Buckle up!...

Tuesday, June 27, 2017

Lol we're all poor


Some recent posts on indie dev failure have been going around lately -- Introversion Software talks about how their experimental exploration game "bombed in a big way", and also Cliff Harris argues "Your Indie Game Will Flop And You Will Lose Money", while Greg Wohlwend writes in his Tumbleseed postmortem about how they will likely never recoup their development costs, and each collaborator earned maybe $10 / hour. You can also connect these threads back to Hugh Monahan's Full Indie 2016 talk "What Scuttled Brigador's Launch", as well as Daniel Cook's theory of "minimum sustainable success" right around when the Indiepocalypse talk was in full gear. I think it's fair to say that the general mood in commercial indie game dev land has been kind of dark for the past few years, and it's getting darker.

I've written in the past about how I don't expect to make a living off of my games. I give away my gay sex games for free because (a) they're short-form games in a market that demands "replay value" even though people don't even touch most of their Steam libraries, (b) I don't want to invest all my time and hope into commercializing it, just to earn like $5k a year if I'm lucky, which does not go far in NYC, (c) when an indie game has poor sales, then that often becomes the game's entire legacy forever. I don't want the conversation around my games to orbit around the awkward pity of my SteamSpy numbers! To me, there's a certain peace of mind in not trying to make the next gay sex minecraft blockbuster happen.

And yes this is totally a weird defense mechanism on my part. I understand that everyone has a different living situation, and I'm not holding myself up as a role-model to emulate. We all have different ways of working in games, but personally I feel like I can't access the same tools or methods as successful commercial devs, so why should I bother trying? If Cliff Harris and Greg Wohlwend can barely make it work, what chance do I have?... I want you to understand why I ask this question:

Why is it so important for us to make our living from selling our games? Why can't we make our living from doing something else?