Ian wrote:Eeeeyeah. I was super skeptical first. I've been working on Mango (now called, "Tears of Steel", the latest blender open movie project), and we're trying to do the whole thing with Cycles. When we started out, it was crazy-super difficult to actually get a good render. Fireflies all over the place, insane render times. It was a bit like the fluid sim. Checking YouTube, you see hundreds of videos of water pouring into wine glasses- and it works fine for demos like that- but if you try it on anything larger- good luck! Cycles was great at rendering out little glass trinkets and chessboards, but an actual environment? Nope! But we've finally figured out how to work with it artistically, and the developers have been working like crazy getting stuff optimized and smoothing out the workflow. By the time the project's done, it might actually be production ready
For about 2/3 of the project, I would go home at night and do a project in Blender Internal, just to feel good about CG again, but I'm finally to the point where I'm occasionally using it for Dynamo, and by the time we're done, it might actually be my renderer of choice. Maaayyyyybe.
That said, it definitely helps to have a render farm at your disposal if you're trying to do animation type stuff. E'gads. And it still doesn't do interiors all that great (Mango is almost all interiors!!) But it's getting there.
The biggest thing I had against it at first was that I couldn't use any of my old techniques- every single scene I had to poke at forever until I found something that worked. But stuff's gotten fast enough that my usual "colored ambient light and sun lamp (or 2)" thing works, and the light is behaving predictably (or, I've just learned more how to predict it? I dunno!) And fireflies hardly ever happen anymore!
The First Cib wrote:I played with it for a week or so. I was really excited at first, the live render and the look of the light was awesome. But I have an ATI graphics card which parentally isn't supported so all the advantage of the supposed "lightning fact render times" is not there for me at all, cycles is just about the slowest thing on the planet for me, I haven't tested it but with my current set up I would guess that the Blender internal renderer is 2x faster for me right now. Also, I can't stand the rainy look it gives, it seems that no mater how long I render it just looks like garbage, the little weird grain pixels from the light just wont go away and are UGLY in video... Maybe that is a side effect of having to render with the CPU? Not sure.
Cycles looks crazy promising, I just hope that they come out with ATI card support soon.
Paul wrote:I just noticed we've got a new member!! Welcome Ian Hubert!!!
I was able to smack this project together using cycles early last spring, and finish it up in about 2 weeks including rendering, on my computer and two friend's computers. No problems with fireflies, except on shiny treasure, so I rendered that in a separate pass for 800 laps and stuck it on the scene which rendered in 25 or 50 laps.
I try to do most of my stuff in cycles, because it's really handy to have a realtime lighting preview, faster rendering, and stuff like that.
I've mainly been able to avoid fireflies by limiting caustics if I can, and glossy stuff, and super bright lights and high numbers of lights, and I've maybe once used the clamp feature that clips any pixels above a certain brightness.
I'm interested to see how y'all do on tears of steel in terms of realism and such. You should put a firefly into a scene and see if people see it. (the bug, not the render artifact =) )
Oh, right I forgot about that one. You have some nice results in there, cant see any problems with the renders.Paul wrote:I was able to smack this project together using cycles early last spring, and finish it up in about 2 weeks including rendering, on my computer and two friend's computers.
Limiting lights? I like lights. I agree with Chirps though, I am going to have to look up that clamp feature, sounds fantastically handy as I have basically had to be doing that manually in my composites with a luma key anyway.Paul wrote:I've mainly been able to avoid fireflies by limiting caustics if I can, and glossy stuff, and super bright lights and high numbers of lights, and I've maybe once used the clamp feature that clips any pixels above a certain brightness.
chirpsalot wrote:Actually, what card do you have Cib? If it's an actual ATI card it might be too old to work with it at all in the future. Only moderately new cards support OpenCL 1.1 (well, a card that's a few years old is probably fine).
The First Cib wrote:I have a 2010 iMac with a ATI Radeon HD 5670 512Mb card, so not amazing. Unfortunately because iMacs are built like laptops upgrading the card isn't a real practical option. Right now every mac runs an ATI Radeon card pretty much, so no mac user can really take advantage of cycles ATM. I am really looking forward to working with it though, lighting and texturing in live mode would be fantastic!
The First Cib wrote:Limiting lights? I like lights. I agree with Chirps though, I am going to have to look up that clamp feature, sounds fantastically handy as I have basically had to be doing that manually in my composites with a luma key anyway.
Users browsing this forum: No registered users and 1 guest