Attached Link: http://www.youtube.com/watch?v=xVc0hUNVRf0

After spending all day to render some 4-5 seconds of animation, I noticed the video had some glitching to it. Any ideas what could cause that?

I used the included island scene as a backdrop, is it not compatable with some things? Or could it be the lighting levels blowing out transparancy or some other wierdness like that?

I liked how it turned out otherwise, so it might be up for a redo - provided there's a good fix for those artifacts.

The artifact are those black square in the video? What your rendering settings? Using GI ?
Just one thing more, put your videos at Veoh.com to get more quality... Youtube compression always make the video file bad to see artifacts.

Yeah, the black square stuff showing up towards the end. Island is the "Palm Trees" under special FX in the scenes tab of the browser. Using Carrara 5.1 Pro...

Redoing it now...  Hopefully it doesn't glitch this time. I figured that the default photon count, ray depth, and some detail levels may have been too low for the starting Carrara scene I was building on. Also I wanted a longer duration, since it goes by too fast in 4 sec. Should be more "dramatic" at 10 seconds, right? (It still has to be short though, I can't do much other than browse some stuff while this compy I'm on renders in the background.) Also doing it as a .jpg sequence this time around, the .avi files were huuuuge. Dunno if a sequence will be smaller, but I've gotta dump to VirtualDub anyways to make it uploadable size.

it goes too fast to tell, but it appears there's bad light interactions with partially transparent plane(s).

gk, obrigado fr the lnk to veoh.com.  google video definitely sux IMVHO.

Something to do:

Reduce the Shadow Accuracy to the same as the Object Accurary (I always use 0.5). This will make shadow more shapen.

Turn off the Interpolation in the Global Illimination tab (you are using a 4 pixels shadow pus interpolation... this will create big artifacts in the final render)

Use Lightning Quality to Fast and 1 pixel to get better results (I know the render will slowdown but you will end with a more quality)

This is after trying some better settings. The new run is being done as a .jpg sequence. The funny thing is that the artifacts come and go in adjacent frames of the animation. Thus there would be a good frame, followed by a glitchy one, followed by another good frame (or a frame with glitching elsewhere in the scene.)

At least with the sequence I can either postwork or re-render a specific frame. I also found the sequence folder is smaller than the .avi's Carrara makes anyways.

Anyhow I'll go back and check some other settings. Maybe that'll reduce problems in the rest of the 80 or so frames to go. And to think this is all for some 10 seconds of UFO flyby when all is said and done. :rolleyes:

Thats why is always a good idea render as a frame sequence and not as animation file! But this is a very strange thing, I think that you could post this as a bug to the Daz Bug Track, so the developer team can look at this file:

http://forum.daz3d.com/bugs/main_page.php

It's still glitching, even after unchecking interpolation and making shadow accuracy match object accuracy. Only other things I could think to try are to change the ray depth and move up the photon count and map accuracy.

Edit: Would they be interested in 5.1 Pro bugs? I thought limited support was part of the CG World magazine deal, unless you opted to upgrade to the current version.

Ahh! Theres no version 5 in the bug track menu now...

I found something else interesting now. Somehow after restarting and playing with one of the network settings (I made port 1 the same port number as on the render node) I finally got the render node to work. Which is cool, because now I can have 3 CPUs working on it. This is where I found the oddness.

It seems the rendernodes don't have the glitching. But then I noticed something else. There's a dome on the bottom of a spaceship, and it's coloration is different on the nodes than on the part my PC is rendering. It may be an experimental shader property plugin I didn't copy over to the node machine. So apparently it also affects transparent objects that don't have the shader property applied to it? This is wierd. But I can't really complain, since it's an experimental shader channel that I got to try for free. I think I'll just have to pull it from my main Carrara folder, and forgo being able to use the cool effect it makes when it does work properly.

Gonna pull it out and see what happens. Hopefully that change won't break too much.