Kinunir Class Battlecruiser redesigned

My Traveller group is making the transition to the new Traveller 5 rules. Or some of them, at any rate. Using the new ship design rules, I recreated the Kinunir class battlecruiser described in Adventure 1. The existing deckplan didn't even follow the design rules set forth by Classic Traveller, so I threw it out the window, redesigned the ship entirely, and created a new more reasonable deckplan.Continue reading →

FumeFX stair-step artifacts

I've had the pleasure of learning some FumeFX* at Eden. Recently I had a scene that gave me some odd artifacts that I couldn't solve. My excellent coworker, Stefan Brederick, spent some time with it and came up with a solution. First, an illustration of the problem:

On the rendering tab, in the Rendering Parameters is a Step Size % setting. By default, this is at 50, and according to the documentation, lowering the value should result in a higher-quality render. In this case, though, for unknown reasons, raising the number improved the result. A comparison render:

I haven't yet figured out exactly why this is happening in this particular scene but not in the others that I've made.

*FumeFX is a plug-in for Autodesk 3DS Max that simulates smoke, fire, and other gaseous fluid effects. I am currently using it to create clouds.

Job titles in VFX and CG: 3d Artists

Stereo "3d" movies have made terminology a bit confusing recently. When I refer to 3d, I mean the virtual 3-dimensional Cartesian system that exists inside the computer. 3d artists create objects that exist in that space and can be looked at from any angle (within the software, of course). When I use the term stereo,  I am referring to what viewers often call a "3d movie." It gives the illusion of three dimensions by tricking the viewer's eye into believing that objects on the screen are at different depths. That's not really 3d, though, since no matter where you stand in the theater, you're going to see the same image.  That is, you can't get a different perspective, even though it feels like you should be able to. So, vocabulary lesson aside, I give you:Continue reading →

Job titles in VFX and CG: 2d Effects Artists

When you're dealing with CG, there are two "art environments," so to speak. There is the 3d world in which objects are modeled and animated, and there is the 2d world of the screen. Things are getting a little blurry in that regard, what with stereoscopy becoming more prevalent and 3d functions becoming available in the compositing software, but it's still a somewhat useful division with regards to categorizing artists.Continue reading →

Job titles in VFX and CG: Illustrators

A friend of mine recently asked for some guidance on getting into CG, and I wrote up everything I currently know on job titles and career paths. It seems like a waste to leave it in a private message to him, so I'm putting it up here in the hopes that others will come along and expand on and/or correct what I know, and maybe it can be a resource to other people thinking about getting into CG. So without further ado:Continue reading →

After Effects defaults and using AE sequences in Maya

If, like me, you get annoyed at always fiddling with the export settings in After Effects, you should take the time to set up some templates and change the defaults.

In the Render Queue window, set up your Output Module with your desired default settings. I typically use a TIFF sequence with alpha channel. Once it's set up, click the drop-down arrow next to Output Module and choose the last option: "Make Template…" You'll get a window with two boxes in it labeled "Defaults" and "Settings."

Give your template a name in the Settings Name window, then in the Defaults box, choose the template as your Movie Default. After Effects will now use those settings as the default whenever you export a Comp.

Now, if you've ever tried to use a TIFF sequence from After Effects as an image plane in Maya, you may have had some difficulty getting it to work. AE's default naming convention is fileName_####.tiff. Maya doesn't like that underscore; it only understands an image sequence if the frame numbers are delineated with a period, like so: fileName.####.tiff.

Click the drop-down arrow next to Output To: in the Render Queue, and choose "Custom…" You'll get a window called File Name Templates. Set up the Template like this: [compName].[#####].[fileExtension] and check the "Default" box.

Now, whenever you set up a TIFF sequence, you'll get file names that Maya can use.

edit: I've been doing some research on file formats (post on that topic coming soon), and I've decided to stop working in tiff. I've had problems with it in the past where I couldn't open an image I created with a PC on a Mac, or I couldn't read tiff sequences created by Nuke in Premiere (don't use DEFLATE compression—Premiere can't read it). Tiff certainly has some useful features, but there are so many different flavors that compatibility becomes an issue. Instead, I intend to switch to Targa for wider compatibility or OpenEXR if I need high bit depth and/or more than four channels. The only gotcha to that is that if you need transparency with Targa, you need to tell AE to render 32-bit files (four 8-bit channels). I don't know why the Targa export specifies bits per pixel when everything else is in bits per channel, but there you go.

The Maya Project Directory Structure

Update: Additional information on the Data folder.

When you create a new Maya project and hit the "use defaults" button, several folders are created. Each of these folders has a specific purpose, but they aren't detailed in the help files, nor could I find much about them in the usual online fora. So here they are, with my evaluations of what they're for:

  • 3dPaintTextures:  If you use the 3d Paint tool in your texturing process, this folder will contain subfolders for each scene in which you have used 3d Paint. Within those folders are the texture files created by the tool.
  • assets: I'm not sure how it works, but I assume it has something to do with the Assets system. It is associated with "Templates."
  • clips: No idea.
  • DAE_FBX: Maya will store exported dae_fbx files for exchanging data with other software here. I think this is a Collada format in a fbx wrapper.
  • data: Fluid and nParticle caches will show up here, with a folder for each scene with a cache.
  • DXF_FBX: Maya will store exported dxf_fbx files for exchanging data with other software here. I am almost certain that this is for exchanging with AutoCAD.
  • fbx: Standard fbx import and export files will go into this folder. These are the files you could open with, for instance, Nuke, so long as they are formatted correctly. Autodesk publishes an fbx converter to assure that your fbx files are of a standard format.
  • image: I honestly don't know about this one. I haven't yet seen anything go into it, nor has Maya ever defaulted to asking for something from it.
  • images: Most raster images exported from Maya will go into this directory. This includes UV layouts and renders. If you render in layers, each layer will get its own subdirectory. Likewise, each render pass will get its own subdirectory under the appropriate layer unless you direct Maya to do otherwise.
  • mel: This is where Maya will look for imported MEL scripts.
  • mentalRay: I'm not really sure what this folder is for. A good deal of MR data goes elsewhere, so I have no idea what this one is for.
  • particles: Particle disk caches, but not nParticle caches, will go into this directory. I'm sure there are other particle-related files that will go in here, as well, but I haven't yet encountered them.
  • renderData: This is a very important folder, with four subdirectories, two of which I have never used. Depth and iprImages are a mystery to me. I have my suspicions about them, but I haven't tested them yet. The Shaders folder is for any shader networks that you import or export from the Hypershade. Mentalray has four additional subfolders: FinalgMap contains frozen final gather maps, which serve to speed up renders using Final Gather. LightMap contains baked light information, including Ambient Occlusion, which can be very useful both for texturing and for speeding final renders if you choose to bake your AO. ShadowMap stores shadow depth maps.
  • renderScenes: Another folder whose purpose I do not know.
  • scene: This is one of three folders most people should be familiar with. All of your scene files will be stored here.
  • sound: I have never attempted to add sound inside Maya, but I assume that this is where you'd store your audio clips.
  • sourceimages: The third of the most well used folders in your project directory, the sourceimages folder is where Maya will look for texture maps of all kinds, including image planes.
  • textures: I am not sure what this folder is for, since your texture maps are all in the sourceimages directory, and procedural textures that are baked out to files go into the images folder.

So that's everything I know about the project folder structure at this time. All clarifications and additions are welcome, and I'll be sure to add a credit to anyone who helps to fill out the rest of this information. Just leave a comment!

After Effects and Windows Vista

After Effects CS4 and Windows Vista 64-bit do not get along well. Although my newish computer renders my projects over 60 times faster than my old one did, the interface has always been somewhat sluggish. My most recent project made significant use of the Vector Paint effect, which served to highlight the problem. The paint tool was very hesitant, and it crashed frequently. Quite a bit of hunting around on various support forums revealed a solution: Run After Effects in XP compatibility mode. My interface is now very responsive, and Vector Paint works flawlessly.

So there you go. I haven't yet encountered any drawbacks, but I'll post an update if I do.