I'd like to know what the numbers mean in the Indigo UI when rendering? I'm presuming you can tell how long a render will take, how do you go about this?
Can you connect and disconnect render nodes when you like in the rendering process?
And I'm asking all the above now as I don't know the answers?...
"FAQ"-forum?
Sure but I'd like to know when 1000 samples/pixel, 2000 samps/pix and 3000 samps/pix is roughly going to happen?As for when a render is "finished"... well that depends on when you're happy with it. Indigo will render forever unless stopped.
Can you work it out from the UI's numbers? I suppose that the figure 20.7847 micro samples / second is an average over the renders life? I don't think my slaves are helping when they restart as this figure keeps building rather than shrinking even though they are maxed out with cpu work?
you need the samples/pixel number and the elapsed time.
convert the elapsed time into seconds, and divide samples/pixel by it. you will then have samples/pixel/second.
take your target samples/pixel and divide it by your samples/pixel/second value to get an estimate of the number of seconds until you reach your target.
substract from that the elapsed seconds and you have the time remaining.
ie
convert the elapsed time into seconds, and divide samples/pixel by it. you will then have samples/pixel/second.
take your target samples/pixel and divide it by your samples/pixel/second value to get an estimate of the number of seconds until you reach your target.
substract from that the elapsed seconds and you have the time remaining.
ie
Code: Select all
S = samples/pixel
E = elapsed time in seconds
P = S/E = samples/pixel/second
T = target samples/pixel
C = T/P = total render time in seconds
R = E - C = remaining render time in seconds
-
StompinTom
- Posts: 1828
- Joined: Mon Sep 04, 2006 3:33 pm
i agree a FAQ would be cool, but wouldnt most of it belong in the documentation? i think then the issue would be making the documentation more prominent/easily accessible. part of that would be posting threads in a couple sections that provide direct links to the FAQ part of the documentation or outside resources.
if someone can give a clear outline/system of what needs to be done, we could dish out the tasks and get started. im willing to put some time in for documentation, im just not sure of the where and how of it at the moment (ie. whats been done already, what needs fixing, etc etc).
ive been very busy as of late and should have some more free time in the next little while so i will see what i can do.
as always, feel free to get in touch with me directly if theres anything you wanna talk about (ideas n such).
if someone can give a clear outline/system of what needs to be done, we could dish out the tasks and get started. im willing to put some time in for documentation, im just not sure of the where and how of it at the moment (ie. whats been done already, what needs fixing, etc etc).
ive been very busy as of late and should have some more free time in the next little while so i will see what i can do.
as always, feel free to get in touch with me directly if theres anything you wanna talk about (ideas n such).
Althought I voted "yes", I rather support the wiki solution.
Basically ppl have questions on:
- installation
- lighting
- materials
- ... pretty much for anything in fact !
so one FAQ per wiki section sounds right, to me. Not on every page, but if you have a look at the wiki it's maybe not up to date and certainly not exhaustive but pretty much structured already.
Basically ppl have questions on:
- installation
- lighting
- materials
- ... pretty much for anything in fact !
so one FAQ per wiki section sounds right, to me. Not on every page, but if you have a look at the wiki it's maybe not up to date and certainly not exhaustive but pretty much structured already.
obsolete asset
