Screamernet Segments don't match Camera value

[Johnny]

I have a SN session going now..first try, LWSN modules were reporting 45 segments, when the Camera Properties were showing 1 segment.

I fiddled with the bucket size, and now they're saying 2 segments, despite Cam Properties saying its 1 segment.

Whassup with that? any clues?

J

[mlinde]

The segment on an SN node are memory dependent. Are you running OS X? If so, then what else is running on the machine, and how much RAM is available? Typically segment memory issues come up in SN because that specific node does not have enough free memory to load the full scene and all associated files and render with one (or a few) segments.

The other possiblity is that the nodes are reading a different preference file, with different segment settings.

[Johnny]

OK..took awhile before I had the chance to investigate everyone's suggestions..

I wonder now if my file in question is "broken" in some way..

Here's what I did:

1. Made super-simple test sequence, small size, lowest quality, just to see if the two macs would screamer render properly; they did.

2. took the file I had trouble with the other day, set up a lowest-quality, small image size sequence of 30 frames, triple-checked all my settings, and I'm still getting 33 passes, 39 segments!

All my permissions are good. I'd think my quickie test file would "prove" whether my SN location is shareable.

Now, the file I'm having trouble with, I've been rendering huge stills with, with no trouble at all on the G5; 3200 pix square in about 2'40" at Enhanced Extreme, no caustics and the same 3 lights as with the failed SN test.

Nothing seems strange w/respect to Menu Metering the memory...

Would it be an accurate method to find whether there's a bad item in the model by selectively rendering a few at a time in their own scene/SN session?

J

[mlinde]

Originally posted by Johnny
I'm still getting 33 passes, 39 segments!This is easy to split up though. 33 passes are due to using Enhanced Extreme Antialiasing. What I've heard and experienced is that you RARELY need to get past Enhanced High. The 33 passes should be happening on all systems regardless of the number of segments.

As for the segments, after looking at your systems, I need to know which one(s) are getting 39 segments. I'm guessing it's the iBook, but if it's also the G4, I'm a little surprised. Segments are dependent on the individual system memory, and with all your machines having different memory capacities, you will run into each machine rendering in different segments with large files like this.

Now, the file I'm having trouble with, I've been rendering huge stills with, with no trouble at all on the G5; 3200 pix square in about 2'40" at Enhanced Extreme, no caustics and the same 3 lights as with the failed SN test. The size of this file, and the level of anti-aliasing are contributing to the render time differences. You are working first on a G5, with an order of 2-3 times faster processing power than the G4, and almost 2x the RAM of the G4. It's going to be significantly faster. The times for the G4 and the iBook will come down when you reduce AA to a more reasonable setting. Enhanced High AA is the highest setting I've ever used, regardless of output and target. I assume you are outputting for a 10"x10" print file, or larger as well, with that 3200x3200 resolution. Oh, unless you are doing some sort of kiosk installation, I guess that's possible too. Even so, EEAA is overkill. Take it down to EHAA.

[Zarathustra]

It was my understanding that the only thing EEAA was for was dealing with motion blur; therefore, EHAA is the highest setting you need for just stills.

I don't know about DOF, though.

[Johnny]

well, that's a handy bit of info in general...

thanks for passing it along; I just assumed that you picked the top quality if you want the absolutely preemo results, but good to know that you can get the same quality in less time!

J

[Johnny]

at the risk of sounding like a complete nim-rod, and being flamed for eternity, I think that the problem with this file (same as in "SN turns in no frames") was that some of the surfaces were trying to use an Image Map which no longer exists, or which has been misplaced...

I only recall using one map with this thing, but there may have been others.

I went through surface by surface, and carefully examined each one, and elminated "I" layers where the map had been lost.

I'm now SN-ing on the G5/G4 net that "problem" file...successfully. And the G5 is beating the snot out of the G4..had 8 frames done before the G4 had even begun!

Thanks for all the help; sorry to report such a lame cause!

J

[Zarathustra]

FLAME!!!