Welcome to cycles versus blender render.
In this video we're going to go over how blender end is generally quick and you get a reasonable result
quickly.
It's as simple as that and it uses only your s.p. you.
That's a central processing unit in your computer.
Now cycles itself is a physical based renderer and is accurate but it does take longer.
It is designed for GP use which is a graphics card essentially but runs fine on s.p. Use as well and
we'll go in later on how to configure these to be better and render a little more quickly.
So why are we using cycles.
Well we are using cycle since we are modelling a lamp.
It's a light.
It's a great time to introduce you guys to cycles and the two are not crops compatible.
Okay so there's no real switching between the two and expecting what you've done in one to come across
to the other that is important to know at this stage so you can use other renderos too.
If you have access to them but we won't be covering these in detail some of the supported renders we
can have a look at if we quickly hop over to the blender website.
So here we are on the blender website.
If we go to I believe it's under download and external renderos we can see there's a list of other render
us that do work directly with lend themselves things like vra and octane also work but they're not listed
on this list at the moment.
So there we go.
There's a series of I'm going to stop scrolling up and down randomly there's a series of external renders
that if you already have access to you may want to use they all have their own pluses and minuses as
well.
And that's always worth bearing in mind.
So none of those are absolutely perfect.
So render time differences.
This is an important consideration.
I will be showing you in a few moments three clips of a four second bowling ball animation.
I mocked up a while ago.
A couple of weeks ago now the blender ender itself came to only two minutes for that 4 second clip.
Now that's quite quite a long time to wait for four seconds but I think it was 30 frames a second.
It was actually doing 120 renders in that time a basic cycle's render Well that took 15 minutes and
a thorough wrench cycles render took four hours.
So you can see immediately how being lean with all of this will help massively.
Especially if you're doing a thorough render towards the end.
You don't to spend four hours only to find something wasn't working properly.
It would be better to do a basic cycles render at some point rather than go for the full one and then
when your happy bumping up and doing the fall one.
So I quickly show you that video now.
But here we have blender end.
And as you can see it's a relatively good mock-up straightaway skipping straight into these cycles a
low pass there we get a relatively grainy and horrible result.
So here's a reminder of the blender render and then if we skip straight over into cycles again.
But this time spending a lot more time on the render we get a very polished model.
So what's the solution here.
Well neither really is a blender Ender is great for getting stuff out quickly that whole scene.
Was only four seconds long.
Took about two minutes to render something like that.
The cycles the very basic grainy one took almost 15 minutes to render the blender render again back
down to minutes.
And that really polished one we can see the end frame here of it.
Well that takes a silly amount of time that took nearly four hours.
Now is that worth it.
Probably not in this case.
Now the main thing that's going to determine your render speed is your machine specs.
So let's have a look at the s.p. you at the moment.
Now just like graphics cards there are going to be a lot of different machine specifications that are
going to vary massively across every one of you guys taking the course here.
The simple rule is the more cause you have and the higher the frequency of your cpq the better.
So if you've got an eight core for gigahertz processor it's going to be faster than a dual core three
gigahertz process.
Simple as that you are unlikely to hit any memory limits when using s.p. rendering because of your system
runs out a memory often goes onto virtual memory but we won't delve into the details of that at the
moment as it is important at this point to know that you cannot use s.p. you and GP rendering at the
same time in the same instance of Blender.
So your machine specs again but this time focus on the graphics card so end video cards any that support
what they call Khuda which any modern and video card is going to do hci a cars.
The support has started in blender two point seventy five but it's not complete.
And you may have memory issues if you're using a graphics card AGP you and the simple reason for that
is some cards just don't have as much RAM as your computer would.
A lot of cards may have one or two gigabytes and you may be sat with a computer that's only got one
or two but it can switch over to the virtual memory.
However if it runs out of memory on your graphics card that's it can't do anything it's just run out
of memory and will fail.
If in doubt at all you are having trouble.
Remember you can switch to see Q rendering at any point so that concludes this round of cycles vs. blender
render.
Now there's no reason to not use either one of these.
It all depends on the application you're going to be using it for as they are interchangeable not not
as in switchable between one another but you can use a blender render to work out a scenes animation
quickly or mock it up really quickly get it out there to the person you're working with or even yourself
to make sure that it is what you want.
Before then going back and manipulating the same meshes using cycles to make a much more realistic render
you can do a mix of them both in this section we are using cycles and then the next few lectures will
get blender set up so it can use cycles as well and will also compare cpq vs. g.p you for your particular
machine so you know which one is quicker.
However that's it for now and I will see you in the next lecture.