Showing posts with label project management. Show all posts
Showing posts with label project management. Show all posts

Saturday, March 8, 2014

"Get Better Soon", dev diary 2: character art and production value.


This is a development diary series for "Get Better Soon", a commissioned game I'm making for Different Games 2014. If you want to see it and play it, then sign-up to attend Different Games in April in NYC (for free!)

Bodies, much like video games, are routinely commodified -- there are "cheap"-looking and "expensive"-looking bodies. Society devalues and discriminates against certain body types, while affording privileges to other body types. We read video games in much the same way, based on the shape of the game's body... the packaging and production values, and/or "paratext", of a game. Production values are a relatively quantifiable way to impress people and convince them to pay $60 USD for a set of mechanics that have remained virtually unchanged for decades.

What if "queer games" weren't popularly characterized by the do-it-yourself gumption of personal stories, expressed predominantly through webpage text, by artists with few resources? What if Electronic Arts directed their next-gen AAAAA commando-developer divisions to build big budget romantic comedies about time-travelling transgender witches who critique Foucault?...

Sunday, April 7, 2013

The joys of sub-projecting in Unity


Let's say you have a personal Unity framework full of useful models, prefabs, shaders, scripts, etc. that you'd like to use across several projects. How do you best deploy that framework?

If you use version control, then maybe in each Unity project folder you'd also have a special folder hooked up to an SVN or a Git submodule. (Though I find Git submodules to be scary and unwieldy and more trouble than they're worth.) If you don't use version control, maybe you'll keep a separate Unity project just for your framework and from that you'll export a new Unity package every now and then, then separately import and update the Unity packages across your different projects as needed.

There's a third way that I'm trying, inspired slightly by how the Source Engine's filesystem works: basically, you keep all your projects *inside* a main Unity project, so they exist more as "mods" or "sub-projects", and they interface with each other as well as a main framework folder that has core prefabs and scripts.