NavBar

Showing posts with label technical art. Show all posts
Showing posts with label technical art. Show all posts

Thursday, June 16, 2011

Suicidal Computers

In case it hasn't been clear before now, let me make one thing very clear: I love computers. Tooling around with them is incredibly fun, challenging, and rewarding. That word challenging, though, is a fickle one. Today (and last night-ish), for example, I was presented with two challenges: my main webserver died, then my laptop decided it had had enough of my shenanigans. Despite the stress presented by both events, though, it's been a particularly interesting (and challenging) learning experience.

My laptop's mini-suicide is the least involved, so I'll start there. I was doing some animation cleanup and sprite-sheet compositing in Photoshop, and it was certainly pushing my system hard. Moving the layer groups around was taking upwards of 10 seconds per update, but I figured that it would be ok once I finished my task, saved, and shut down the program. I got a little weirded out when my cursor changed from an arrow to a bizarre vertical dotted line for no apparent reason, but it functioned normally otherwise, so I continued to work. Then this happened:



I honestly have no idea as to the actual cause of that. My only guess is that I was pushing the system too hard, it overheated, and gave up the ghost. I'm thankful that after I let it cool down a while, it started back up just fine.

The real kicker was my server dying. It was originally a desktop box, but its CPU heatsink isn't entirely stable, so I relegated it to less stressful jobs. I had a bios password enabled on it, and forgot to take it off when I installed the server OS. For a desktop, the boot-up password wouldn't be a problem, but on a server it means that I can't do any sort of remote reboot. Easy enough to fix, I thought. Boot up to the bios screen, remove the password, reboot to the OS, and everything will be dandy. And it was, until it didn't boot the OS.

I admit that I panicked a bit at first. I tried reinstalling the OS to reuse the existing partitions, and that didn't work. That freaked me out a bit more, so I mounted a usb key and pulled off all the critical data (website, subversion repositories), and tried a full format and reboot. That didn't work, so I transferred the salvaged data to my secondary server and went home to sleep.

I spent the next morning configuring the secondary server's Apache to replace the old server. Honestly, I was surprised at how quickly it went. It took me several hours over many days to figure out how to get it all set up the first few times. Even though it was much easier and much less painless than I expected, it really drilled into me that I need to get a good backup system in place. Looks like I'll be doing an rysnc/cron crash-course soon.

After work, I discovered the most anti-climactic solution to my server's startup issues. I flashed the bios. I don't know what it changed, but it must have fixed something, because it boots just fine now. Since I re-formatted and re-installed the OS, it'll at least give me a fresh start on building it up more efficiently. Also, my dad gave me a bunch of old drives to use. I'm going to shove a few each into the servers to see if I can't stave off any more massive failures.

Also, as an added bonus, here's a crappy ipod photo my current workspace:


A. is my Lenovo T60p laptop, "Cacofonix". It has a 32-bit Core2Duo 2Ghz CPU,3Gb RAM, an ATI FireGl v5250 graphics card, a 100Gb primary drive, 250Gb secondary drive, and runs on Vista Business.

B. is my main work machine, "Fulliautomatix", custom built. It has a 64-bit Core2Quad 2.66Ghz CPU, 8Gb RAM, a GeForce 275GTX, a 150Gb primary drive, a 375Gb secondary drive, a 1.5Tb storage drive, a 300Gb scratch drive, and runs on Windows 7 Pro.

C. is the webserver, "Shoggy" (formerly a desktop named "Tragicomix"), that crapped out on me. It has a 32-bit Core2Duo 2.66Ghz CPU, 2.5Gb RAM, a 250Gb drive, and runs Ubuntu Server 11.

D. is a mystery-box :3 It's not mine, I don't get to keep it, but it was really cool to play around with expensive enterprise-class hardware.

Not shown is my other server, "Merrt" (formerly a desktop named "Asterix"), which is one of my dad's old desktops. It has a 64-bit 2Ghz dual core AMD CPU, 2Gb RAM, a 150Gb drive, and also runs Ubuntu Server 11.

A side bit of fun for me: computer naming. My family has always been a fan of the Asterix and TinTin comic books, so our computers have always been named after things, usually characters, relating to them. I remember at one time, my dad had a trio of servers at his job which he'd named Uderzo, Goscinny, and Herge, after the authors and artists of those two comic series. At home we've had computers named Asterix, Getafix, Geriatrix, Fulliautomatix, Lutetia, Cacofonix, Dogmatix, Tragicomix, Unhygenix, and Panacea.

While I've always loved my family's naming scheme, I've wanted to start differentiating my systems as I starting to create my own networks and administrating my own servers. Thus, I've been naming all my new machines after characters from the Warhammer 40K Gaunt's Ghosts series. With so many good characters to choose from, I have attempted to pair my servers with characters who share similar traits.

The character Shoggy was a trooper who lost his eyes and had them replaced with mechanical ones. He's good at a few things, but can't perform up to the same standard as the rest of the soldiers. Similarly, the server Shoggy has an unreliable heatsink, so I don't trust it to do any heavy lifting, like rendering stuff in 3d.

The character Merrt was an excellent sniper who took a jaw-shot, and had it replace with a mechanical one. He still fights well, but he's no crack shot anymore, and he has confidence issues. Merrt the server was hot stuff when my dad first got him. It was our first 64-bit system, and had an internal RAID system. But as time wore on, he became less shiny, the RAID system started corrupting stuff, and he was finally replaced with new hardware.

I love taking old hardware and making it useful again.

Anyways, enough about computers for now. I hope to have some more fun art to post when I have more free time. :D In the meantime, check out Mighty Rabbit's Website and Facebook page to keep up with what we've been doing.

Monday, May 9, 2011

Gun Rigging

Quick update on what I'm working on! I'm now working as a pixel animator at Mighty Rabbit Studios here in the Triangle area, so I will be delving into more pixel work on here in the near future.

The Angels Fall First project is progressing well, too. The finished mech rig has been put aside for now so that I can do a full overhaul on the first-person arms and weapons.

The arm rigging is pretty nuts right now. The original meshes were created using a poly-decimator, which basically takes a hi-poly mesh and tries to create a low-poly version while maintaining the overall surface shape. The problem is decimators don't create clean topology, and messy topology looks crappy when it deforms. Thus, I've had to re-topo the hands and try to fit them all to approximately the same proportions, with a marginal degree of success. I hope to explain more in a future post.

My latest work, tho, has been on the gun rigs. I've got a ton of awesome weaponry on my hard drive, and I've been having a ball working on getting it all set up to animate. I took one of the assault rifles all the way thru to a finished rig so that I can start testing thing out in-engine soon. Here's a short demo vid:





This rig took a lot more work than I'd expected. It has a lot more moving parts than most guns (sometimes all you need is 2 bones: grip and magazine), which was work enough, but the real challenge was making the switchable pivot points. I tried a number of different methods, but the eventual solution ended up being pretty simple.

At the core, it's a variation off the simple IK/FK triple-skeleton switching system. I have two skeletons for the stock and grip which drive the main control skeleton. One skeleton is rooted at the stock, the other at the grip. The main body control houses the attribute which switches between the two. Ideally, I'd like to set up a script that will allow for matching between the two versions. Way down the road, I'm hoping to write a GUI that would allow the animator to switch out weapons on the fly and do other nifty tricks, but that's gonna take a lot more planning and work.

Alrighty. That's me for now. If things go well, I should have moar soon! :D

Wednesday, April 20, 2011

PyMel

I print tshirts for a living, and that means that a good chunk of my work-day is spent waiting for the machine to spit out the next shirt. It gets pretty boring if I spend that time just sitting and waiting, so I get on my laptop and do useful things instead. This week, for example, I started to look into using PyMel for some of my scripting needs.

To get everyone up to speed, Maya uses its own embedded scripting language called MEL - Maya Embedded Language. It's a good start for learning how Maya works behind the scenes, but it is rather rigid in its structure, and has a tendency to be very very verbose.

Newer versions of Maya have begun to include a Python runtime as well as a library which ports all (most? I'm not 100% sure) of Maya's MEL commands for use in Python. This essentially allows you to write MEL code while taking advantages of some of Python's nicer features: dynamically typed variables, more refined string manipulation, and not having to check every freaking line of code for the one semi-colon you missed that's causing your whole script to break. However, it still requires you to think largely in more of a MEL-type flow, which ends up feeling like a half-baked hybrid that nobody really would want to look at.

That's where PyMel is intended to come it. From what I gather, PyMel is designed as a more Python-y integration of Maya commands into Python. Honestly, I don't have enough experience to say for sure, but at first glance it does seem to be an improvement. I will add one caveat: it appears that others more experienced than I have a less-than-enthusiastic opinion of PyMel, primarily because they have found it to become excessively slow for large iterative tasks. However, since I'm writing small helper scripts rather than full-on tools, the speed differences have so far been indistinguishable. (As a final aside, a brief websearch indicates that PyMel is faster overall for scripting control, but it is faster to then switch to the Maya.Cmds functions for iterating large loops.)

Anyways, why is all this important? Because I'm a perfectionist and a minimalist (usually within reason). I like to do as much as I can with as little as I can get away with. For example, why write 5 lines of MEL code when I can do the same thing with 1 line of PyMel?

//Parent constrain lower-level control object's zero-group to higher-level control object
//MEL Code
string $OA_ctrl_parent_selection[] = `ls -sl`;
string $parent_ctrl = $OA_ctrl_parent_selection[0];
string $child_ctrl = $OA_ctrl_parent_selection[1];
string $child_group = "GRP_" + $child_ctrl + "_zero";
parentConstraint -mo $parent_ctrl $child_group

//Parent constrain lower-level control object's zero-group to higher-level control object
//Python/PyMel Code
parentConstraint( ls(sl = 1)[0] , "GRP_" + ls(sl = 1)[1] + "_zero" , mo = 1 )

I'll be the first to admit that the PyMel snippet is much more difficult to decipher, but ultimately it's going onto my shelf as a button anyways. I'm also working on translating to PyMel the script I talked about in my previous post, but it's still a work in progress. In the end, though, I just really love writing these bits of automation to make my life easier. My rigging is already getting faster just by reducing the number of operations I have to execute to get the same results.

Thursday, January 27, 2011

Obsessions

It feels good to be coding again. Minecraft quickly turned into an addiction, which I have curbed by turning it into a project. I'm writing a Python script that converts Minecraft's world save data into Maya scenes.

When I was looking for Minecraft wallpaper for my desktop, I discovered an image where someone had taken Minecraft's level data and exported it to a different game engine, then used the game engine to export an OBJ to Blender. The final render looks like this:



I was blown away, but I quickly discovered that their method was quite specific to their software and, more importantly, Mac-only.

My script is still in the rough stages, but much of the basic functionality is there. It can open the .DAT files in which Minecraft stores its world chunks, strip out the section about what kind of blocks make up the chunk, then use that data to re-create the chunk inside of Maya. The end result looks like this:


It's an ugly pile of dirt, but it's a start. The blurry stuff on the top is water, and the various colored blocks are the different materials that make up the chunk. In the end, the script should create a set of geometry like this, as well as a proxy model, save to a file, then reference all the completed chunks into a central map scene.

I also have a list of features I'd like to add:
1) A shell mode where blocks that cannot be seen will not be created. Each chunk is 16 blocks wide, 16 blocks deep, and 128 blocks tall. That comes out to 32768 blocks per chunk...
2) A way to generate better water geometry. In the end, this may just have to be put in manually using planes.
3) UV layout and assignment to use the in-game textures.
4) Automatic lighting creation and placement for things like torches, lava, glowstone, etc.

I'm having a lot of fun with this. It's the biggest technical challenge I've had to tackle, and it's been a rewarding experience.

Tuesday, April 6, 2010

I'm a tool (writer)

Things are getting pretty busy. The film is due for marks on Friday, and I'm busy trying to get something patched together for marks. To help try to meet that, I took some time today to write a little pair of tools to get me working faster.

The UDK has a nifty command switch called "dumpmovie" which forces it to save every rendered frame to the screenshots folder. In combination with the "fps XX" switch (where XX is the number of frames per second), it essentialy performs like a batch render in Maya, except there's not automatic off. Instead, it plays in a game window, and stops recording when you exit the game. Of course, the options with this are very limited. You can't (as far as I'm aware) set the path for the screenshots, and it only saves in BMP format, but it works, and that's what's important. Since BMPs are uncompressed, they take up a lot of space. A 120-frame render weighs in just over 300Mb. With WinRAR, I can collect and compress those 120 frames into a single 20Mb RAR file. That's about a 93% storage savings.

With those facts in mind, here was my workflow for rendering out a scene:
  1. Save final map and assets in UDK, then close editor.
  2. Open command prompt and type in really long UDK shell command to start a Dumpmovie render. (example: C:\UDK\UDK-2010-03\Binaries\Win32\UDK MapName -dumpmovie -benchmark -fps 24 -resx=1280 -resy=720)
  3. Render out scene.
  4. Open Explorer to the UDK screenshots folder.
  5. Select all new rendered frames.
  6. Right click, "Add to archive."
  7. Set up WinRAR options.
  8. Delete leftover frames.
Not optimal at all.

So instead, I wrote two simple batch files. One does the rendering side, the other runs the archiving. The rendering one also has the option of calling the archiver as soon as the render finishes. This is my new workflow.
  1. Run UDK_Render.bat.
  2. Give map name, choose resolution (full or half 720p).
  3. Run render.
  4. Choose to archive (or not).
  5. Give archive name.
  6. Done.
This leaves me with a screenshots folder that has nicely organized archives for each shot, plus it deletes the source files after creating the archive, so the screenshot folder is clean and primed for the next render. This also makes it very easy extract each archive into its own folder to prep for rendering out an uncompressed AVI from AfterEffects so I can then throw it into Premiere for editing.

As a side note for comparing UDK render time against Maya: If we assume Mental Ray is rendering at 5 frames/minute and UDK at 15 frames/sec, the ratio is 4500:1!!
Render time essentially becomes a non-issue. I could render my entire film (if it were contained in a single map), check for errors, tweak the map, and re-render in about the time it would take MR to render 3-5 frames. This by itself is one of my major arguments for using real-time rendering engines (like game engines) for rapid film production work.

Tuesday, March 23, 2010

Pewpewpew!

I've been fiddling around with animation tests and setting up particle effects this week. Now that my rigs are done, I have to put them through some quick paces to debug controls/weighting. So far the planes look good. Chester needs some work, but what he needs can only really be solved by remodeling and doing some custom rigging instead of the autorigger, so I'll just have to make do.

Anyways, I spent Sunday learning how to use the UDK's Cascade particle effects editor. It's a nice tool, very powerful and modular, but (obviously) not nearly as crazy as Maya's stuff since it all needs to run realtime. The main downside to Cascade is that comparing it's interface and workflow to Maya's is like comparing command line Linux to Windows. There's a lot you can do, but it's not pretty, it's not easy, and you better know what you're doing.

So I got some basic muzzle flash FX working, and hooked them up to my carrier plane to see how they look...

B17 Particle/Animation test from Adric Worley on Vimeo.



Pretty sweet. I hope to get the plane textured and add some tracer particles when I have some downtime from animating. I'm loving the pewpewpew.

Wednesday, March 17, 2010

:D!

Guuuuuuuuh. Had to rebuild Chester's head and his whole rig. Here's a shot from painting weights.



That is all.

EDIT:



Chester's so happy to have a (minimal) working facial rig. Definitely not ready for any sort of real lip-sync, but it'll have to do. In my ideal world, I'd have time to make a snazzy face UI that has crazy stuff like, you know, labels for what controls do what, or blendshapes, or something. No time for that (both b/c of time setting up in Maya and working on downstream UDK implementation). Gotta crunch as much in as fast as possible to get a passing film.

Reeeeeally want to start working on a side-project that we've got cooking on the back burners. May throw out some hints later on... :D

Friday, March 12, 2010

Lightmass

Just upgraded to the latest build of UDK since I'm still in Content Creation, and haven't committed too many assets to the engine yet. One feature I hadn't played with at all til today was Lightmass. Lightmass is a new system for creating the baked-in lightmaps for level geometry. Unlike the old system, which used purely direct lighting (requiring individual lights for all lighting effects), Lightmap uses global illumination to create more realistic effects. The results are pretty incredible.






These shots are from the DM-Deck map that ships with the UDK. The only work I did was rebuild the lighting with and without Lightmass. It's amazing to see how good the lighting looks in comparison to the old system. As an added bonus, Lightmass comes with a network redistribution feature, so I can shunt some of the workload onto my lappy and speed the process up. As a comparison of build time, the old system lighting rebuilt in just over a minute, while Lightmass rebuilt in about 15.

Tuesday, March 2, 2010

Nazis and Shaders!

Finally! Something visual to throw out into the world.

One of the options that caught my attention when I first started playing around with UDK's material editor was the Specular Power parameter. Specularity is essentially how shiny an object is. In reality, specular highlights are reflections of whatever is casting light. In CG, esp. for games, it's an approximation. The two control parameters given are Color and Power. Color is obvious, but the Power parameter is control over the spread of the highlight. Really shiny objects like polished metal have tight, bright highlights, while things like rough-textured plastics, unfinished wood, or other duller objects would have very wide, diffuse highlights. What first came to mind was how to control that across a surface? If you could control the SpecPower, you could simulate multiple material types without having to create and assign a new shader material for each material type. It took a few tries, but I think I have a basic working solution.

In addition to creating Diffuse, Specular Color, Bump, and Normal maps for a material, I worked out a way to make a Specular Power map. The way it works is it divides the texture into 4 color channels (RGBA) and assigns each one a specific specular power. It then adds each area back together, then divides the result by the sum of the original channels. Here's an image of this set up as a shader network in UDK:


The texture can't be applied directly to the Specular Power parameter because UDK sees each color channel as a value between 0 and 1, while the SpecPower parameter is a (relatively) unlimited number, and 1 creates a very very diffuse specular. By multiplying each channel by a fixed desired SpecPower, the artist can apply a range of specular intensities in the same material. Here's a quick example of the shader in action:


SpecPwr Shader Demo from Adric Worley on Vimeo.

As you can see, the reflected white highlight is larger and more diffuse on some areas, and smaller and more focused in others.

I don't know if this has any practical application in games, or if it's too expensive for too little payoff, but if was certainly a fun problem to try to solve.

Next up: Zombies!

Now that I have a working rig with a skinned mesh, I've finally gotten down to pumping out some animation. It's not great, it's not finished, but it's something. So far all I've done is a rough walk and run, but I'm slowly getting back into the groove. Emphasis on slowly. (Also, Vimeo, in its infinite wisdom, appears to have enabled frame blend on its upload encoding, so the vids aren't great quality. shame.)


NaziWalk from Adric Worley on Vimeo.



NaziRun from Adric Worley on Vimeo.

To be perfectly honest, I'm quite disappointed with animation here at Sheridan. I haven't done any animation of note in about two years. Most of the later work in 2nd year was all lip-sync, and as I've said before, character animation does not come easily. Combine that with my still-developing character-drawing skills, and you end up with a lot of meh work. Third year was a bust, too. My action analysis was terrible because I spent so much time trying to keep up in all the other classes that animation kept getting pushed to the side (a common problem here), and my group film went similarly. I wish that we'd been given more opportunity to focus on doing animation, or at least have enough time outside of schoolwork to explore it more on our own. My friends can attest that the time I took out of class work to explore Maya took its toll on my marks. With any luck (and dedication), I'll be able to do more animating on my own once all this film stuff is done.

EDIT: I've written more about this overly-complex SpecPower shader in this post, where I realize a more efficient solution.

Friday, February 26, 2010

No Moar Trax

After looking into Maya's Character Set and Trax animation features, it is clear to me that there is good reason for there to be so little information about them on the net. They suck. The concept is really cool and would be useful in production, but the implementation is finicky, frustrating, and has the potential to completely screw your work.

The character set creating workflow is simple enough at first, but there are a number of major problems that crop up:

  1. Character sets interrupt how Maya stores animation curve data in relation to actual controls. If a character set is changed on the rig file, it has the potential to wipe the animation from a curve, since its curves are connected to the character set node rather than the control itself. For example, taking the structure LowerBody>Legs>LeftLeg/RightLeg and merging the lower nodes up into a single LowerBody node will wipe all animation from the controls that the lower-level nodes contained.

  2. The Trax editor can only create clips at the lowest character level in a set with subcharacters rather than allowing you to choose the level at which the clip is created. For example, creating a clip by choosing the top node in the LowerBody>Legs>LeftLeg/RightLeg character/subcharacter hierarchy will result in between 2 and 4 clips (depending on whether or not the higher levels have controls not contained in lower levels), instead of a single LowerBody clip. EDIT: There is a way to group clips so you don't have to fiddle around as much with each individual clip, but that seems to leave more room for fiddly errors than creating a single clip at a higher level.

  3. There doesn't seem to be any clear way to save Trax clips as external files. Defeats the purpose of creating a library of clips which can be imported into a scene as needed. EDIT: Apparently you can export the clips as MayaBinary or MayaAscii files. Doesn't rectify the more egregious issues mentioned above.


Some of these shortcomings are based solely on my own expectations, needs, and limited experience, so I admit that there are those who won't find any problems with what I've pointed out, or who can show that I don't know what I'm talking about. In any event, the tool I was expecting this to be shouldn't really be that hard to implement. It wouldn't surprise me to learn that most studios have their own scripts written to do just that. In the meantime, I'll have to find an alternative solution for segmenting and storing my animation clips.

EDIT: As these later comments show, I wasn't writing from the full picture. Even with clip grouping and exporting abilities, though, the animation-wiping nature of character set nodes is a deal-breaker for me. It's unconscionable to me for a setup artist to use a system that could potentially destroy large chunks of, if not all of, previously completed animation when updates and alterations are added.

Thursday, February 25, 2010

Exploratoring

Continuing in the vein of my previous few posts.... PROBLEM SOLVING!

Probably the most exciting part of solving problems for me (other than the thrill of finally fixing a tricky issue) is research. I'm a self-admitted information junkie, and I love learning new stuff. Anyone who knows me can attest that I spend a lot of time browsing for new techniques, cool tricks, or just stuff I want to know (I've gotten into a bad habit of reading Wikipedia articles on food when I'm hungry). One of the side effects of this is I've gotten reasonably good at targeting searches and finding elusive information. The sad reality is, though, that just because I'm looking for information doesn't mean that it's there to be found. This has been especially true in the case of Maya Character Sets and Trax information.

Tuesday, February 23, 2010

I love solutions

I figured I'd break up the last post into two parts to avoid TL;DR syndrome.

FUN PROBLEMS
Today my friend Andrew posed me with an interesting problem: He was working on a scene with a relatively large number of complex character rigs (high polycounts combined with lots of lattice deformers), and he chewed up all of his RAM. This killed Maya, and somehow corrupted his file. This raises two interesting points with solutions I enjoy. First, saving often and making backups. I am terrified of losing my progress and work, so I like to have as many safety nets as possible.

My favorite solution for giving me peace of mind is source control. I have a modest Ubuntu box sitting under my desk running Subversion, and my laptop and work machine both have TortoiseSVN for Windows. It's great because it's easy to keep both machines up-to-date, and I feel much safer knowing that a broken file is only a few clicks away from reversioning to a working file. As an added bonus, I've set my machines to be accessible from any point on campus (password protected of course), so I don't have to lug around a bulky external hard drive. I have never had to actually use the safety net features of my setup, but I am willing to take more risks knowing that, failing a total system meltdown, I can always go back to an earlier version.

The second solution Andrew's situation brings up is proxies. I haven't done much exploration with proxies, but the concept seems highly useful, and I plan to learn more about them. In general terms, referencing files in Maya allows you to pull in assets from other scenes (like character rigs or environment elements) and use them without fear of accidentally breaking them in some way. Also, going back to that compartmentalization I mentioned in my last post, it gives flexibility to edit the original asset file, with changes being reflected in the new scene without needing any user interference short of a reference reload. The problem with referencing is that scenes can often eat up tons of RAM (what with rigs, smooth skins, deformers, textures, etc...), and that's where proxies come it.

From what little fiddling I've done with them, proxies allow you to create low-resolution versions of your assets and have them stand in for the more complex ones. Low-res is, of course, a wide term. It could be anything from a simpler rig with fewer controls and parented geometry chunks instead of smooth skins. It could be just a bounding box. Or it could be somewhere in-between. Whatever the case, it gives you a way to see the asset working in the scene without it taking up unnecessary resources, and, if set up properly, allows you to rough in placement/animation before switching it out with the high-res version for final tweaks. I'm still rather vague on specific implementation, but I'm looking forward to working out how to use them appropriately for smoother workflow.

Also on my list of things to figure out: Maya Trax and how well it works with planning out Matinee work in UDK.

Monday, February 22, 2010

Still alive...

The cake is a lie...

Just doing a quick post to keep this thing going. I don't have anything to show for the past two weeks... yet. I've been doing a lot of rigging work which is all very technical and not very visual. Long story short, I got my Nazi Grunt character fully rigged and weighted, which made me very happy. Then I exported him to the UDK for testing, and that did not.

Maya uses the Y-axis as its world-up, while UDK uses Z-up. I've been doing all my modeling and character prep in Z-up space, but the autorigger I've been using doesn't play nicely with Z-up, so I did all the rig setup in Y-up. Needless to say, that causes problems. Additionally, the autorigger adds a lot of extra bones to handle IK/FK arms, legs, and spines, and those get exported to UDK as a mass of crazy. Had to figure out how to pare it down to just what I need.

Technical Stuff
For those interested, here's how I solved these multiple problems:
1) I saved the whole rig to a new file, where I stripped the skeleton of everything except the smooth-bound joints. I then parented the floating joints (spline-IK spine) to the root spine joint.
2) I then exported a skin weights map to preserve all the weighting I'd done this weekend, then removed the mesh's smoothing skinning.
3) With the mesh and skeleton separate, I was able to rotate the mesh to orient correctly, and could freeze the rotation of the skeleton's root joint. This solved the issue where my animations played along the wrong axes in UDK. Previously, even with the controllers pointing correctly, the actual skinned bones were receiving translates/rotates along the wrong axes.
4) I smoothbound the rotated mesh to the skeleton and re-imported the skin weight maps. Because I have some mirrored UVs to save on texture memory, I had to re-paint some of the weights and mirror.
5) This file was saved, then imported into the file with the full rig. I deleted the mesh attached to the full rig, then parent/orient constrained each of the bound joints on the imported file to the rigged joints of the existing file.

This gives me a certain level of compartmentalization between the rig I'm animating versus the rig that's actually moving the mesh. I can now change around the controller mesh in various ways without affecting the bound skeleton and mesh. If, for example, the leg rig turns out to be something other than what i wanted, I can remove the control structure, create my own, and I don't have to worry about re-exporting a new version of the skinned mesh to the UDK or having to update any exported animation to account for new/deleted bones, or changed proportions.

The downside to all this is I've realized that I have to do this to Chester, too. Not as bad as having to figure it all from scratch again, tho.