What exactly does this mean? 21:07:47 -------- 27:31 It's what I saw under the render button. So what do all those numbers mean? - is the first one the estimated time for the render? Then if so, what's the second number? And how come on the next pass it says: 1:48:46 ------- 1:48:54 ????

first off, afaik, bryce's own render calculations are accurate only for short renders. know you're gonna deathkneel it with some 18 hour render and it's gonna be way off. that said, i have absolutely no idea what those numbers mean, in 5 years of brycing i have never bothered to check them. i just figure out how long the nano-preview takes to render and how long the first rendering step takes. based on the latter, theoretically each sub-pass will be at least twice as long. which gives me a pretty good idea. drac (doesn't really help)

... and if you stop a render and then resume later, the percentage (at least on a windows PC) also means nothing. I'm not sure why the percentage when you stop and save can't be carried over to the resume, but it isn't.

in other words.. eh?

Uh,............21 Years, 7 months, 47 weeks, 27 days 31 hours ? Now that's a LONG render ! I don't have a clue. It's not your bank account number is it ?

Drac, Twice as long? Heck! I looked all through the Bryce Bible - nothing on it anywhere. jfike, But on the next pass after that resumed pass, the percentage is visible again... are you saying it's not true? I mean that I see a percentange for each pass... It seems to be right...

Lol! @sackrat More likely to be my debts!

with those numbers u can calculate the arrival of the newest bryce version. ;)

Gosh, it'll be here THAT soon??? ROFL...

Fran you know that is one thing i have noticed and really never thought about. One test render i was doing with a standard sphere and 100 radial lights in it was going to take 18 hours to render yet the bottom number was on 11.27..go figure. CD (Off to the gods at DAZ for an answer)

How about this. The top number is the estimated time of the current pass, then smaller number below is the actual time of the previous pass and the bottom number is next weeks lotto numbers?

Setting lights to ranged falloff will often decrease render times significantly. Set each up to where you get the overall desired effect and there you go. Good luck.

The first number tells you how long the render should take. The next number tells you how much time has elapsed so far. Both numbers get updated at the end of each render pass.

Thanks to Silkrooster over at DAZ for this. PS: The third number is for the time line at the bottom of bryce, to do with animation..

Message edited on: 12/03/2005 23:34

Well, I was darn close.

21:07:47 -------- 27:31 21billion bad pixels/ 7 good ones/ 47 don't knows! Kidding!

On the first pass, the estimated time is wildly inaccurate, however it does improve with subsequent passes. However, as jfike pointed out, the elapsed time and percentage are lost whenever the render is interruped. The other problem is that it does only update at the end of a pass, in some cases the later passes can take a few hours, which means your estimated time left and elapsed time don't update for a few hours. Mahray

CrazyDawg, Oh yes, I knew the bottom number was to do with animation, that's why I didn't mention it. Thanks for the gen from the horse's mouth on this. This render started off saying 1 day, 4 hours, 51 minutes, 2 seconds, but actually that first pass took 27 mins 31 secs... and subsequent passes were faster than I expected from that first estimate... but the darned thing REALLY slowed down on anti-aliasing... so at 3am last night... morning? I stopped it . Only starting it again at 11 something when I finally got up this morning... afternoon? it's saying 3% now, since about half eleven... it's now 12:15... gonna take a while... gee! I just hope it's worth it when it finally finishes... This is a different angle to the ten passes and still going original... I got fed up with staring at the darned thing... began to see odd things in it, like I'm sure there was a doggy's nose in the middle somewhere.. So, changed the angle, and now I'm not sure if it's any good or just plain weird.

Fran watches the Render-Line Fran watches the Render-Line Fran watches the Render-Line LOL When your render FINALLY finishes, I'll tell you how to correct your mistakes without having to render the whole damn pic again..!

21 hours; 7 minutes; 47 seconds Estimated rendering time

27 minutes; 31 seconds Actual rendering time

Fair enough?

The numbers will converge as the rendering is completed.

Message edited on: 12/04/2005 17:43

Bryster, I may well take you up on that - I've noticed a couple of out of place lines.... and as this is a totally new departure for me (nicking something of AS's) I'm a bit lost... Fran watches the Render-Line Fran watches the Render-Line Fran gives up on the Render-Line and goes and does something more exciting instead... like my email.

hahahha Fran on images with slow anti-aliasing you can set the render to "fine art" or "premium" mode at 4 rays per pixel. In these modes, bryce oversamples each pixel, so there is actually no final anti-aliasing pass, it's included in the normal passes. This can really help when you have a lot of bump maps and usually gives better quality than with regular AA in the first place. I find that for regular setting images the clock is way off because anti-aliasing takes a lot longer or shorter depending on the scene. On premium settings, since there is no AA pass, the clock tends to be much more accurate.

Thanks for that. And anti-aliasing hesitates when it get to hair... then once past it, it leaps ahead. Can you tell? I've been watching the render line...

If I have a really Long render time image (like with lots of glass) I will usually do a rough render of the whole thing, save the file and then come in and do a plop-render of a selected area. When that is done I will save the image (not necessarily the Bryce file) and then go on to do a plop-render of another portion. This way I can do it in stages (so my computer isn't completely tied up and unavailable for other uses if I need it) and if something should freeze up during one of the partial renders I can go back and load in the last saved one and continue without losing ALL that render time. Sometimes Bryce hangs on me. Does that happen to anyone else?

No, I've never yet lost anything part way through a render. Part way through texturing the darn thing often crashes but I don't loose anything so long as I've saved up to the last change of texture.