First of all. No problem for me with you.
Ok, honestly your reply disappointed me a little bit because it sounded a little bit harsh.
But, no problem. I understand that sometimes it's not easy to communicate the right things on a forum.
For example, English is clearly not my native language, and sometimes it's difficult to write my thoughts.
With that said.
I perfectly know that HDRI is not photorealism, or fast renderings obtained with software like 3D-Coat or similar is not photorealism, or other things like that :)
Etc...etc...
A true photorealism involves a biased rendering engine, that can provide lots of complex calculation trying to mimic the behavior of the light and the materials into the real world.
Also, I perfectly know, and these was totally INTENTIONAL, that all of my posts of 3D-renderings here on this forum are TOTALLY not photorealisc :)
In fact here I almost always wanted to share with other guys, fast and quick concept renderings, just for the fun of modelling something very easy and very fast and doing a similar quick and dirt renderings.
And consider that also, as I've said some times ago, actually I'm so bored by all the tech things related to 3D that I really don't want to spend my time actually with all the tons of tech stuff about rendering and modelling that I've played with and studied during almost two decades.
(In fact actually I'm almost totally returning to the study of 2D fine arts and digital painting)
With that said, again, talking about photorealism, I do not consider photorealistic, NONE of the examples your provided of enterior renderings in EVEE.
That kind of rendering are absolutely far miles away from a real photorealistic scenes.
I'm confident that also you agree with me about this point.
And, YES, when I named "UNITY" or "UNREAL" I perfectly know that they're not photorealistic rendering engine.
They simply are (at least UNITY), EVEE on steroids.
As you know a true photorealism involves so many things, that a simple HDRI or GI environment, or a render engine like EVEE, can't provide.
Anyway.
I really hope that you understand my point of view and the fact that (I repeat) I have no problem with you.
To be honest, I have to say you, just in order to avoid misunderstanding, that really I don't want here to start and endless debate, so please don't think bad if I will not reply any further message about this argument.
> A true photorealism involves a biased rendering engine
I think you mean unbiased.
BTW. The term photorealism was coined long ago, before
modern biased and unbiased render engines saw their light.
I remember very well CGI stuff from the mid 80's which was
named photoreal too. I still have that on VHS tapes! :-)
If you would compare such footage with today standards you
would not agree that this is also photorealism.
A quick Wikipedia look-up for photorealism and non-photorealism
might help.
O.K. back to work … let our creative juices flow and i will end
this discussion now too. :-)
Hi Stefan
I think to jump into Blender,and buy Chipp's course
If i remember, you got Maxwell,and being you an expert about renderers can you tell me differences about Cycles and Maxwell?
I did all my renders with Fry before,then Arion that is similar to Maxwell
Thanks:M
I am by no means a render expert … I am only a 3D doodler, so to speak.
However, I try to do images the possibly easiest way to produce and that they
are for me showable. Maxwell Render allows me to do this because it is for me
easy to use and very logical. I am still using and old version, without GPU support.
The reason why i started to play with Cycles is that i can produce nice images as
well but with much shorter render times. And thanks to Metins tip about the denoiser
i can render now much faster with Cycles (or Maxwell …). That said the learning
curve to use Blender and Cycles is higher for me, because there are much
more settings (node set-up for shaders etc.), but once mastered i should be good
to go.
Eevee is a totally different beast, i was all ears when Chipp released his
course, because i have found no similar course for learning Eevee, which i like
to use later too.
When it comes to direct comparison of render engines there is a nice comparison
available to check out the pros and cons of Cycles and Maxwell.
Cycles is unbiased like Maxwell, Fry and Arion,
but the terminology for Material definitions
and its used parameters are slightly different
and you can use nodes for the material creation
as well, which Maxwell does not have.
Lighting wise there are no watt/lumen etc. presets/
settings for different lamp types in Cycles like Maxwell has,
nor a physically sun you can set the hours / day etc.
I think if you download Blender and play
with Cycles or Evee settings a bit you see
the differences compared to Arion and Fry.
while reading about lighting with Cycles and wondering about translating some things
from Maxwell i found this very interesting article for Cycles, explaining how to create
an accurate sun intensity model and using kelvin values for emitters via the blackbody
node. While not an add-on i think it could be very useful for some of us.
Just a minor remark: Cycles is not unbiased. The term unbiased is used for renderers that do no simplifications to speed up rendering. An unbiased renderer will have a minimal amount of settings and will always converge toward a result that is as realistic as possible.
Maxwell is an unbiased renderer, but Cycles is a biased renderer that uses methods to simplify the result in order to gain speed. This doesn't mean that Cycles is not a realistic renderer. V-Ray is also a biased renderer, and the physics math behind the light ray calculations is correct, but rendering is sped up by using methods like a light bounce limit, ray tresholds, blurring glossy reflections, noise reduction and other approximations that increase speed at the expense of realism. Using the right settings, a biased renderer can yield very similar results to an unbiased renderer while offering more speed.
The Blender 2.81 master builds now include Intel's AI-powered Open Image Denoiser (OIDN). It's quite impressive what it can already do with a one-sample rendering:
