Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
Re: Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
Ops, it is getting worst and worst for Maxwell.
Maxwell 60 seconds
Luxcore 60 seconds
test set-up
Attached the scene file
Maxwell 60 seconds
Luxcore 60 seconds
test set-up
Attached the scene file
- Attachments
-
- light bounce stress test3.zip
- (103.05 KiB) Downloaded 176 times
Re: Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
That's why i'm saying the giga benchmark battle tests are totally misleading. They simply do not squeeze the render engines showing their real capabilities.
Re: Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
I'm a bit surprised of Maxwell: it is pretty much supposed to be the best BiDir out there, may be with Indigo Render. Actually, they haven't very much competition, as far as I know, they are the only commercial available BiDir to say the true.
"Pitch black" ... or to use another movie tittle: "The Mist". Cycles (like Blender internal before) is really intended for toons animation, I have no idea why people use it for ArchiViz or Photorealism.
Re: Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
And i can show about other 4-5 tests in which luxcore beats Maxwell. I think luxcore is by far the best bidir around.
Re: Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
I think because of high flexibility of setting up scene. If you took closer look to people like Gleb Alexandrov, Ian Hubert or "Default Cube", you can notice how ingeniously they use the full set of Cycles features to create really interesting scenes, compositions and virtual spaces. Gleb provides interesting thoughts about setting lights and env in scene, Ian shows quick and dirty, but pleasant way to build 3d environment in scene and animate it, Default Cube gives us understanding of non-destructive node based material creation.
And what about ArchiViz - I guess it's quicker to send scene to render, cuz you have no special "nerd orientated" settings to tweak - everything is simple.
Re: Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
Most of the light in this scene is indirect light.
You can see how maxwell is faster in removing the overall noise. But there is a big cost in acccuracy compared to Luxcore.
Maxwell 2 minutes
Luxcore 2 minutes
Maxwell almost completely ignores reflecting surfaces illuminated by indirect light. Similarly, Maxwell is unable to reflect caustics in a mirror.
Suddenly a small tweak on the code in one of the most reputable rendering engines gives a completely wrong result.
If you are working in a project with these lighting conditions, which are quite common, you can go crazy if the rendering engine doesn't behave correctly and gives you dull images. What would Corona do with a scene like this? What about Cycles?
You can see how maxwell is faster in removing the overall noise. But there is a big cost in acccuracy compared to Luxcore.
Maxwell 2 minutes
Luxcore 2 minutes
Maxwell almost completely ignores reflecting surfaces illuminated by indirect light. Similarly, Maxwell is unable to reflect caustics in a mirror.
Suddenly a small tweak on the code in one of the most reputable rendering engines gives a completely wrong result.
If you are working in a project with these lighting conditions, which are quite common, you can go crazy if the rendering engine doesn't behave correctly and gives you dull images. What would Corona do with a scene like this? What about Cycles?
Re: Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
Please Dade can i have all the settings for the super fast RR ? the one that produce this image :Dade wrote: ↑Sat Jul 10, 2021 11:04 amThere are more settings:
Code: Select all
# Higher is the max. depth and more effect RR settings will have path.maxdepth = 32 # At what depth, RR will start to operate: lower is faster. Range [0, path.maxdepth] path.russianroulette.depth = 3 # At what value, RR will start to operate: lower is faster. Range [0.0, 1.0] path.russianroulette.cap = 0.5
Re: Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
I trust on you and your words but I can't match what you wrote with what my eyes is watching.Dade wrote: ↑Sat Jul 10, 2021 11:00 am This is a rendering with intentionally fast RR settings (6.12M samples/sec):
good.jpg
As you see I can manipolate the samples/sec however I want. But check the "rays per samples": the first one traces ~36 rays per samples while the last one only ~4 per samples. Clearly the last one is perceived 6 time "faster" ... but it isn't, it has just more noise and potentially fireflies.
I mean that you wrote it has more noise and potentially fireflies but in your example it seems the reverse.
At least the noise is many many times lower and I really like the noise free reflection.
About the fireflies it seems lower as number but probably they could arise later when an higher sampling level will be reached...but as now we can clamp, it could be interesting to see if it's possible to avoid them just with clamping.
Re: Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
This (faster):Sharlybg wrote: ↑Mon Jul 12, 2021 9:24 amPlease Dade can i have all the settings for the super fast RR ? the one that produce this image :Dade wrote: ↑Sat Jul 10, 2021 11:04 amThere are more settings:
Code: Select all
# Higher is the max. depth and more effect RR settings will have path.maxdepth = 32 # At what depth, RR will start to operate: lower is faster. Range [0, path.maxdepth] path.russianroulette.depth = 3 # At what value, RR will start to operate: lower is faster. Range [0.0, 1.0] path.russianroulette.cap = 0.5
Code: Select all
path.maxdepth = 32
path.russianroulette.depth = 1
path.russianroulette.cap = 0.0
Code: Select all
path.maxdepth = 32
path.russianroulette.depth = 32
path.russianroulette.cap = 1.0
Re: Giga Benchmark battle : Luxcore Redshift CyclesX ECycles Vray Corona
Are you mislead by the number of samples per pixel ? I took the screen shots at random points to show the difference in samples/sec and not in noise.
First was taken with 31 samples per pixel while the last was taken with 207 samples per pixel (clearly the last has less noise even with fast RR settings).
Yes, like I wrote before, now with clamping and denoiser it may be worth having more aggressive RR settings.