Thanks everyone.  I finally just reinstalled Poser and everything is working fine - for the time being.  I have yet to installSR2.1.  I'm still not sure it works or just messes things up.  Maybe I'll just have to suffer waiting for the preview to come back up after viewing a render.

I don't have an SSD drive, so that wasn't the problem.  Forgive my ignorance - I'm an editor,  not a computer guru - but how do I remove Poser .int?

I just downloaded the file from Renderosity, installed it in a new runtime and it still freezes up the moment I try to do anything with the M2K.  I've gone into other project files that I have worked on and changed up until yesterday and all objects, cameras and lights work fine, but if i touch the M2K, I get the spinning orb.  I let it rotate for about a half an hour, then clicked on the screen - white death. 

I loaded in the Mosquito by itself.  It works perfectly.  Loaded other airplanes and space vehicles.  Everything works fine.  So the problem is with the M2k file and I don't know why as it worked great until today.  It looks like something within Poser pro 2012 has been corrupted and this file will simply not work anymore.  I suppose I'll have to reinstall Poser Pro 2012 once again and see if that fixes the problem.  I never had issues like this with my old Poser 7.  I must say, the additional features in PP2012 don't seem worth the constant struggle to get work done.  It's ending up costing me both money and clients due to this unpredictable behavior.

I'm obviously not up to date on my Vue skills. You say you render against a black background.  Do you create the background in Vue?  Then you hide everything but the one object you want to render including the background you made and this gives you the object with a built in Alpha channel for each frame?

I've used PNG files in AfterEffects for years with good results.  Open to any and all suggestions to improving my workflow.  One thing I noticed is that the "Alpha" PNG generated by Vue are not Alpha channels at all and don't work in AfterEffects.  Poser generates PNG with built in Alpha.

I was trying to do an animated asteroid in Vue, but ended up getting weird red artifacts along the edge of the asteroid and a supposedly Alpha PNG output that contained no alpha at all.  I gave up and imported an OBJ asteroid into Poser, textured it and animated it in less than an hour.  It came out terrific.  The Vue animation also had a really bad flicker that made it unusable.  Vue 8, by the way.

I love using Vue for set extensions and matte shots, but my experience with animation and Alpha channels has been dismal.

I'll give it a try when I get home tonight.  Thanks for the help.

I would update the drivers if I could.  Avid will only work with an older legacy driver.  If try to open Avid with the updated driver, all I get is an error message.  As I make my living as a video editor, I can't afford to lose my editor to make Poser work correctly.  Buying another powerful computer (I do render heavy animation) just for Poser just isn't an option.  The fact that After Effects, Photoshop, Blender, and Vue all run fine on my system with no problems makes me wonder if the driver is the culprit.  As I said, if it is the driver, then my Poser days are over.  A bummer since I just shelled out a bundle for PoserPro 2012, and really liked it when it was running great on Vista.  My Vista system also required an older legacy video driver to run my old Avid system.  No problems then.  If Poser ran fine with even an older video driver than I have now, it may be the Poser - Windows 7 combo that is fouling things up.

Thanks everyone for the help.

If it's the driver, I'm in trouble.  Avid has to run on a specific Nvidia driver.  It was the same situation with Vista and Poser worked fine.  If this updated (Avid) driver isn't compatible with Poser, then my animating days are over.  I make my living editing and relax with Poser projects.  Life is never easy.

Well, how dumb am I?  I had my Avid dongle plugged it - volume H.  Pulled it out and the world is right again.  Sorry to waste everyone's time.

Thanks everyone, that should get me there.

Figured it out.  The light was not inside the room, but in the annex next to it.  For some reason the preview showed it lighting the wall, but as soon as I moved the light inside the room all was well in the render.  As usual, my bad.

Strange.  I did move the house to the top of a hill, so it is not zeroed out.  I'll try it without moving the house and see what happens.  The weird thing is that the preview looks perfect, but the light doesn't show up in the render.

Thanks BB - simple, that's how I like it.

Sorry, Poser 2012.  Too many late night sessions last week.  

Sorry to be so dense, but what shared folder?  I'm a film editor, not a computer guy.    Thanks for the help!

I'll give it a try.  Thanks.

Thanks for the lecture BB - well deserved as usual.

The scene is a car being struck by a train.  The car is an 11 frame sequence of a SUV model I bought on Renderosity.  It's a night scene with two infinate lights at low intensity.  The car is supposedly sitting on the crossing when the train hits it.  The car is the only object in the scene - no other props or objects, no ground shadow.  It's gray but almost black with the night lighting, but it does have transparent glass in the windows.  Firefly render was set at best quality but with stock settings.

I finally just modified it in Photoshop as the scene rendered without blur in about six minutes.

I know dpi doesn't factor in, just the standard set up for hi-def video.