Tweet
Ok. Maybe I'm doing smth wrong, but installed latest backburner update and right after first frame completed it waits for a 600 minutes to start second one! Normally, it doesn't work that way. But this time it's all different. I know, that default "wait to render timeout" is exactly 600 minutes... but never thought, that frame, that renders 3 minutes can cause max think it need to wait another 600 minutes for the next one!
Any ideas ?
P.S. Don't tell me to decrease waiting timeout, as this is a temporary solution, suitable only for short and simple flythrough animations with almost constant rendertime between frames.
P.P.S. Maybe it will help:
irrmap medium animation / incremental add
lc flythrough with 2200 / from file
qmc 0.1
adaptive subdivision 0/2
render elements object id
no phys cam
colormaping reinhard bright 1.2
clamp and subpixel on
720x576
frames from 150 to 220
priority of this job in backburner 100%
no active task in RAM, even explorer.exe
winxp 64 sp1 (until next year arrives can't install anything new )
Any ideas ?
P.S. Don't tell me to decrease waiting timeout, as this is a temporary solution, suitable only for short and simple flythrough animations with almost constant rendertime between frames.
P.P.S. Maybe it will help:
irrmap medium animation / incremental add
lc flythrough with 2200 / from file
qmc 0.1
adaptive subdivision 0/2
render elements object id
no phys cam
colormaping reinhard bright 1.2
clamp and subpixel on
720x576
frames from 150 to 220
priority of this job in backburner 100%
no active task in RAM, even explorer.exe
winxp 64 sp1 (until next year arrives can't install anything new
)
Comment