You Can't Always Get What You Want

I have a philosophy when it comes to UI, especially on mobile devices. I think the fewer the button pushes it takes to get a user somewhere, the better. I don't like wasted space, and I don't like 'back' buttons. The more tiers you have, the more likely a user will get lost in your menus.

That's why, on a Blu-ray or DVD you will often find that selecting an audio option jumps you right to subtitles. And Selecting a subtitle option often jumps you to 'play movie.' The reason being is that's probably where you're gonna go next. This minimizes user input and is just good intuitive design.

Personally, I start by choosing 'scene selections' and then pick chapter 1. Why? Because it skips a lot of warning cards and logos. That's a free tip. You're welcome.

So, I wanted the UI for our game to have one menu. All buttons visible at the bottom of the screen at all times. No matter where you are in the menus, you can always get to where you want to go. In one button push - it's right in front of you. The worst menus I ever experienced were the crafting menus in Final Fantasy XIV. I kid you not, there were around 9 tiers you had to go through to craft one item. When you were finished, you had to back out of each tier. There was no 'close all' option. Terrible UI design.

What they should have done was had the same button that opened the menu close all tiers. Say if it's 'C' to open the Crafting menu - you navigate through it, open a bunch of tiers, etc. - then you just hit 'C' again and they should all go away. I played that game with a combination of a controller and the keyboard & mouse. They had made the game with the controller in mind, but honestly it's difficult to have standard MMO controls conform to a controller's setup.

For our game, people argued against me saying that a 'main menu' with a big 'ole "play" button on it would be more intuitive to users. And if they go to a sub-menu, hiding all other options would make their choices easier, and having a 'back' button would fulfill their need to know that their selections were registered.

I could definitely see the point in their argument. I likened it to the system settings in Macs vs. PCs. On a Windows machine, I'll often hit the 'Apply' button before hitting 'Ok.' Either way works, I'm just a bit OCD about it. On a Mac, if you go into System Preferences and change a  setting, it's done. There is no 'Ok' button. You made the change, you obviously knew what you were doing when you chose it, so it is finalized at that moment.

I find the second method to be more clean. There are no erroneous button pushes. But, as was pointed out to me numerous times, the average user wants a certain set up. They're comfortable with it. And I had to agree that while my way may be the best for me, it is not for everybody.

Another thing I had to contend with was some art criticism. I've probably never had my art critiqued. Well, except for film projects, and they were always given an A+. Lots of people wanted to be on my crew. I really credit Gavin's writing for all that; I just pointed the camera at things and had a knack for editing.

I remember from friends who majored in art that the way to react to criticism is to just shut your mouth and take it all in. Don't try to justify or argue; although I found myself explaining a couple of things. It was very humbling. A lot of people I showed my work to really liked it; it all just boils down to tastes and what one is used to seeing. I refined my work based on the criticisms it received and ended up making most of the adjustments. A large portion of the work was going over the edges of the image with fill paths to give them more natural strokes. There were over 700 paths in the Illustrator doc at one point, so there's a lot going on in there.

Skeleton images from Sorcerer's Odyssey.

 As an aside, I've been learning to code in C#. It's been a long time since I've written any code, like since 1998 when I did C++; so I'm basically just starting over. I have some simple game ideas I could probably pull off with a couple weeks' worth of work, so I want to pursue those in my spare time.

Learning to compromise is a big part of making games for a corporate entity. You have to navigate around the wants of the people paying you, as well as what the programmers are willing to do. A large part of my job is managing people by influence rather than authority. That means I need to be able to bend as much as I ask others to bend for me.

Action is My Middle Name

Monday is behind me and this week is shaping up to be very busy. I have three distinct jobs to do. I say jobs because each one will require something akin to full time commitment.

I have a high-profile BD/DVD project I'm working on, I have to capture "hours" of video for a sizzle reel, and I also have to do creative and advise on other people's work for this new game so that a polished, playable demo is ready by Friday morning.

I was able to capture some footage for the sizzle reel, and it seems to be a lot more manageable than I had originally anticipated. I basically broke down all the shots that were listed in the spot and organized them into digestible chunks. The sources range from the PS3 to an iPad to a PC, and using a Gefen scaler I'm able to capture to my Mac via HD-SDI. The catch is I have to be actively using the apps and websites, so I can't just put it on auto-pilot. I may farm this work out to someone else as the week goes on and other deadlines loom.

The new game has us all excited and the Design team is going to be ready to show some of their work tomorrow. I was busy most of the day updating our internal wiki with guidelines for the designers. Matt and I also showed the designers how to use the Mantis bug tracking software; creating an entry, assigning it to a designer, and how to resolve and close out an issue.

What do I have in common with Quentin Tarantino? We both had floor seats at the Staples Center for Morrissey on Friday night. I briefly imagined a conversation where I chided him for not getting back to me with his approvals on a certain project. However, I realized it would not have been nearly as funny in reality as the poor guy was instantly mobbed the moment the lights came up.

I was trying to make my way back from whence I'd come when event staff told me to turn around and go another way. Someone was down on the floor, clearly injured. I passed a pair of EMTs who were wheeling in a stretcher on my way out the doors. It was actually the second stretcher I'd seen brought out that night. Some kind of fight had broken out in the section next to me about 3/4 of the way through the show.

For some reason, the Morrissey show required more EMTs and stretchers than the Marilyn Manson concert last week. Morrissey himself was blissfully unaware of any disturbances, however Manson's show at the Nokia was much smaller and intimate, so he felt the need to address the combatants. What are you tusslin' over? Are you tusslin' over a woman? Are you tusslin' over me?

Is Paul playing NIN's 'hurt' at the onset of this clip?

I'm looking forward to seeing the design concepts tomorrow and hopefully I'll get to make a few assets myself before the day is out.

New Game

It's been a bit since I last posted. I had hoped to continue something of a regular series of posts as I work on projects, but honestly I've been far too busy to stop and write.

Since the last entry, I was able to get a higher-poly version of the character put into the game without much fuss. The framerate didn't dip significantly, even with all the particle effects from the traps I made (flame gouts, arrow traps, etc.) going off all around the character. I also refined the walking and added a jump animation. I went for something akin to Mario with the fist pump in the air and the character's front foot propped out front. I feel confident that I could delete it all and do it again in about 20 minutes. Same with all the rigging. I know because I've had to, hah.

I was about to add the obligatory /dance animation as well as one of my faves from the DAoC days, /beckon (Think Neo from The Matrix), however that project has been put on hold.

Come at me, bro.

For the past few weeks, people have been kicking other ideas around. I spent countless hours prototyping 2D and 3D concepts. The directions were to come up with something simple and fast, but fun and engaging. Oh, and new & innovative. Finally, one night last week, Matt and I sat down and wrote a game design doc for an idea we've had for a few months. It was definitely not something that could be done quickly, but it was a game we would actually play and really liked. We stayed up til about 2am working on it. I stayed up another hour or so drawing concepts and wireframes. We presented it the following day.

While it was received very well, the higher-ups were looking at a really short turn-around time on development. So we went and cut about 80% of our ideas, leaving one core gameplay element and a little bit of flair. This concept was accepted, and we've begun work on the new game.

The assets are mostly 2D, and some 3D elements are going to be displayed as 2D. I think the game should be fun, and will hopefully pave the way to doing the full-blown concept we had originally mapped out. We have an internal wiki set up so that we can share the design bible and keep everyone on the same page. We can also use it to track bugs when the time comes. I'm having meetings with the design team today to go over my concepts for creatures as well as the UI layout. I'm really looking forward to working on this new title and I think it will be fun.

Breakthrough

I finally had a breakthrough today with a character I've been working on for months. I had been struggling for a few weeks (before the holiday break and again afterward) with an issue importing into Unity3D. The character came out looking like a misshapen pancake, whereas previous iterations looked just fine. I had added joints and skin weights to the skeletal structure, so I was certain it was something along those lines which had affected it, causing the model to implode on itself when added to the scene.

After some headaches and much Google searching, Matt was able to find me some good posts to check; a couple threads suggested to uncheck 'Segment Scale Compensate' in every single joint. I was skeptical, saving the model beforehand with a new iteration number lest I screw something up royally (or if there were no effects shown) and have to revert.

This turned out to be what I needed to do. Why it's on by default, what it does... doesn't really concern me. I can look it up later.

Pancake

I'm still working on texturing and I'm hoping to go with a higher-poly final result, but at least I'm no longer looking at a smashed, inverted lump when it's in the game world.