Cycles, Mitsuba, Nox and Yafray render engine comparisons
With so many different external render engines and many new arising, it can be confusing as to which you should use. Testing each individual engine can be time consuming and sometimes confusing for the less experienced so blender-artist
JoseConseco has created a short but comprehensive comparison between the a few engines; Cycles, Mitsuba, Nox and Yafray.
I remember when i wrote my multi render engine comparison.
This is short but good comparison. Nice to see that we have so many free or open source choices now.
It would be nice to have a more comprehensive list. I understand that’s kind of a lot to ask for but I remember not too long ago when I learned there were even different render engines. It also seems like different engines are good for different purposes. I’ve been playing around with LuxRender because of Blender Cookie tutorials and I *love* the quality of renders I can get from it. On my POS machine though, it takes forever to use. I wouldn’t want to use it for animations, I’d be more likely to stick with the default Blender Render because it’s a lot faster.
That’s the sort of information a newbie like myself could use. People on the forums start talking about plugins, API and a lot of other language I’m getting used to and it gets confusing pretty fast. Which, I don’t fault them for! A big chunk of the forums is to be able to discuss these sorts of things in detail and it IS good for newbies to be exposed to the jargon. Mostly, it would be nice to have a break down for the beginner and if anyone would be so inclined to put together something I’d love you forever.
Alexis,
I to am saddled with an old pc – I have been experimenting with Amazon EC2. It doesn’t seem to be worth while using it by simply adding it as a network renderer because of the file transfer time, and running the gui from the cloud using ssh -X is worse, there is the possibility of rendering it on your pos until you get to the point that you think everything is going the way you want, then saving the flm and uploading to the cloud, then run lux from the colsole and…wala – you now have 8 cores crunching the render for a relatively low price – something like 7.5 cents an hour. Really not that bad.
The trick is to be able to script the whole process from starting the instance, uploading the file, start and stop rendering (adding halt time to the .lxs file, transfer the image and stop the instance.
I have only done preliminary testing with the scripting portion, but it is very doable using the Amazon EC2 API Tools, and sc3md from s3tools.org.
I have the benefit of using a linux pc, as well as a linux server in the cloud – windows server time cost more.
Alexis,
Don’t worry, Lux is uber-slow even on a super rig
Which CPU did you use? Is it really a AMD 3core?
Please test it with some kind of “normal” CPU like a Intel QuadCore!
So anybody could compare it.
I think nobody has a AMD 3core!
I couldn’t deal with the speed of LuxRender, so I moved up to Thea Render.
It is fast, and it gives you both biased, and unbiased rendering engines.
The biased is very good for animations, and it is fast… Relatively speaking.
link was broken
thank you !
i’ve written in my article about more render engines , you can check them here : http://www.tip-day.com/top-render-engines-for-blender/ have a nice day .