Hi Christoffer, we ran into this exact same problem just last week, contacted the foundry and was told this is a known issue and has been logged as bug #22989.
The work around we found was to set expressions to your frame numbers or seed in order to get the result that you're looking for. cheers, josh 2011/11/14 Christoffer Hulusjö <nuke-users-re...@thefoundry.co.uk>: > Hi, > We are having problems with the ScannedGrain node in 6.3v5 under Linux. > When rendering, what seems to be happening is that if you have a batch/chunk > size set to 1 it will only use one frame for the grain sample and render > static grain over the sequence, if you have a larger chunk size like 5 it > seems to be using 5 samples and might be unnoticeable but it’s still not > using the full 50 frames of the original grain clip. > > I ran my render tests locally through the terminal, rendering a sequence at > 1, 5 and 10 frames at a time. I tried the exact same nuke script with Nuke > 6.3v1 and 6.2v2 and in both those versions it worked fine, so it must be > something introduced recently. > > Cheers > Christoffer > > ________________________________ > Christoffer Hulusjö > http://christoffer.hulusjo.se > _______________________________________________ > Nuke-users mailing list > Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > _______________________________________________ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
