PDA

View Full Version : Rasterized Rapid Motion Blur results in strange white dots/artifacts/sparkles


Anghenfil
12-24-2009, 06:14 AM
I've run into a troubling issue with Maya 2009's Rasterized Rapid Motion. On our render farm running from the linux command line, Rapid Motion produces white dots and smears on the frames.

We have occasionally gotten this error to occur on our workstation computers as well, but mostly when running render.exe from the windows command line. Rendering inside Maya batch or the viewport does not (usually) produce this error. Obviously, the next test for us will be to try batch and viewport renders on the farm to compare, but with the holidays we are indisposed.

On the left is the error, the right side is rendered correctly.

http://img709.imageshack.us/img709/9800/example1.png
http://img709.imageshack.us/img709/4171/example2.png
http://img705.imageshack.us/img705/6694/example3.png

Note that in these examples, the file and the version of Maya are identical. The right side comes from the farm, the left side is from my laptop.

Here is what we currently know about this problem:

1. It only occurs in the Rasterizer with rapid motion. Putting it on Scanline (standard "Production" Motion blur) fixes the problem, but results in far longer render times for a grainier blur.

2. It doesn't happen all the time. There was a Rasterized scene on the farm where the error did not occur. Rarely, we have been able to get the error to happen on our workstation computers from batch or viewport, but usually it occurs strictly from the command line.

3. It usually, but not always, occurs in areas of frames with a lot of blur. The white artifacts appear to have affinity for the edges of objects in some cases, but again, not always. I can occasionally find little dots of white in relatively still areas in the middle of objects.

4. The dots can appear on any object in the scene, usually during a camera move, but it appears most often on characters and other moving objects.

5. The dots are sometimes frame-consistent, meaning you can render the frame again and have the dots come out the same way. This does not always hold true: Sometimes the dots are slightly different (larger, smaller, a few missing or added). Each computer that we've tested on has a particular pattern of dots that it "prefers" on a given frame, and will either produce that exact same set of dots or a slight variation. The preferred pattern tends to be different from computer to computer.

6. The dots are random from frame to frame, meaning they affect different areas of the object through time, resulting in a "sparkling" effect when the frames are played back.


Has anyone ever seen this error? Any ideas or hypotheses of what might be going on?

Anghenfil
12-25-2009, 03:06 AM
New development. I pooled resources with some colleagues and our old school, and we determined that the error was only happening in Maya 2009. Scenes rendered from the command line in 2008 or 2010 have not produced the error thus far. If we manage to find an exception (it starts failing in 2008 or 2010, or we find a more concrete pattern) I'll be sure to update.

Anghenfil
01-04-2010, 07:52 PM
All right, this is a followup just in case anyone else runs into this problem.

We could not get the white-and-sparklies to leave us alone in 2009. Downgrading to 2008 was the only solution we could find. Very annoying, but at least we can render now.

If anyone has the time or inclination, can someone run a Maya 2009 command line render to try and replicate the bug? I encourage you to post your findings, no matter what you end up with.

Remember to set it to Production: Rapid Motion inside the file. Then from the command line run this:

"C:\Program Files\Autodesk\Maya2009\bin\Render.exe" -r mr -v 5 -s STARTFRAME -e ENDFRAME -rd PATH_TO_OUTPUT_FOLDER -proj PATH_TO_PROJECT PATH_TO_SCENE_BEING_RENDERED

Replace all caps with your relevant data. Full paths only (ie, starting from a drive letter). If the path has a space in it, put it in quotes.

CGTalk Moderation
01-04-2010, 07:52 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.