How long do we think it will be until Cycles is complete

im just curious and was wondering what the general opinion is on when cycles will be finished or at least get hair render.

:smiley:

Finished? never… Hair? maybe september this year? – http://code.blender.org/index.php/2012/01/cycles-roadmap/

At least another year, at minimum, before it can be considered general-purpose enough to be a production renderer. Anyone thinking it will be sooner is deluding themselves.

" or get hair render " that’s where it’ll be finished for you then ? :smiley:
" finished ? never … " it’s hard to please everyone :smiley:

i think in 12 months you will be able to use everything with normal render speed.for example if cycles gets hair on november i dont think it will be fast enough to render a furry character.

in 2012 we will be able to render all interior and exterior renders. in 2013 we will be able to render animals,characters,…

@reC :smiley: nah but its one of those features that im sure everyone will be happy to see…

If you want to speed up, consider crowd sourcing, and sponsor a developer with the funds. :wink:

A render engine can never truly be “finished”, hopefully they will keep updating it for many years to come and not let it become like BI.

It might become “feature complete” during Mango though :wink:

I’m giving it a year and a half to two years until it’s ready to replace BI.

This is like asking when your daughter will be grown up (and you have to let her date). You can attempt to put a date on it, but it totally depends on the person. It’s kinda imperceptible…one day, it’ll hit you when you look at them “oh man, she’s not a kid anymore, and looks all grown up”.

And we all stay like a kid inside, right? :wink:

Cycles is growing up, don’t you worry. :eyebrowlift:

That’s why it’s called cycles. It just keep on cycling round and round, spinning but never completing, repeating but never repetitive. Cycles, like your renders, will be complete when you say it’s complete. If you think it’s not complete, it keeps on cycling. It has no completion date.

Grain can be fixed up or even considered cool, but fireflies are the big issue for me. I will consider it complete when it does not generate fireflies.

I will consider it complete when it does not generate fireflies.

Alright, but even now it has like 10x less than luxrender or indigo.

Alright, but even now it has like 10x less than luxrender or indigo.
It doesn’t matter, as an animator, I could never sell an animation with fireflies. The client would simply not understand why it was not right. And there is no way I am going to hand fix thousands of erroneous frames. The problem seems to be in the Glossy shader, which I try to avoid using as much as possible.

Considering the nature of pathtracers, that might be a difficult job.

Anything that causes the production of caustics in a pathtracer will create fireflies, meaning that most fireflies will often increase in number and later average out as the caustics converge. The only ways to remove them would either be highly targeted sampling algorithms, automatic hotpixel removal, or the user turning off caustic generation (which will eliminate various effects like light refracting through glass).

Of course you might argue that having a photom-mapping algorithm would eliminate the problem, but you might end up trading high-frequency noise for blotches in some cases.