Chaos Corona Forum
Chaos Corona for 3ds Max => [Max] Feature Requests => [Max] Resolved Feature Requests => Topic started by: Oltskul on 2013-01-22, 23:24:09
-
Hi,
one little button, which will globaly override all glossines to 1 and disables all maps in "reflection glossines" slots.. And also exclude..
for example: If you want to test material on one object.
Please do not confuse with material override :)
-
I don't understand. If you want to test material on one object, then why don't you use material override? Non-blurry reflections will just get in the way.
-
Or, setup a separate scene with hdri and some custom lights to set up a material. Corona renders that kind of scene instantly so you have all the flexibility and speed you might need for material creation.
Even if it would require some additional adjustments in final scene, it will be much less tweaking... no?..
-
I am really trying to understand the problem. I know Vray has this toggle. but i can't wrap my head around why, except for optimization purposes. But in corona, blurry reflections probably won't render any slower than sharp ones.
If you have a scene, where you need to preview and tweak a material on a single object, it makes sense that you would want to disable reflections on everything except that object in order to get rid of surrounding distractions. But if you keep reflections there, just make them all perfectly sharp, they will still remain there to be a distraction.
-
OK OK..
it is for performance purposes. If I am doing previews, and do not want to wait like 10minutes for "not-too-noisy" image, then i would like to switch off all glossines.
And global reflection would be awesome too.
In Corona they render at the same speed maybe, but i takes looonger to converge to the aformentioned "not-too-noisy" image.
note to myself: do not think when tired :)
-
Are you sure about that? Try to make some comparisons of noise level between glossy and sharp reflections. Not that i do not believe you, but i never did such a comparison myself, so results could be interesting.
-
OK OK... but give me like 6 hours to get to corona :)
-
It seems logical that it would take more time to produce clear glossy reflection, but I'm curious about the tests...
-
*yawn*
test complete... I almost forgot... 2minute each, glossiness 0.0, 0.5 and 1.0..
see ya tomorow!
-
I don't see much use for such override (although it would be possible to implement), so I would prefer not to do it, to keep both UI and code simple. The difference in the images is nowhere near dramatic.
PS: you should buy new computer instead ;) 400k rays/s is waaay too low, in such simple scene you should be able to get about 8M/s with i7
-
those test suprised mi a little bit, but on the other hand they didnt as i was thinking about them before the tests..
It is all about Ray per second..
And if you look at non reflecting objects (empty sphere and teapot on the stand), they are both noisy in roughly same way.. But it suprised me, that reflection is noisy in same rate.. That was that suprise..
It would be pointless to implement it - but nice placebo :)
AD ps: jeah, this would be awesome, but there is problem with my bugdet :D
Anyway my PC is maybe HW broken. Because this scene started on ~1,3M rps and ended at shown rps. Or it is just computational way? Or is this logycal conclusion, becase CPU have "more and more to worry about" - parsing more and more pixels to VFB? I have to do another longer test if the value stops, or it contuiniues to drop to some ridiculously low number.
HaND Olt
-
Higher glossiness makes renders more noisy. What a strange renderer. :)
-
Higher glossiness makes renders more noisy. What a strange renderer. :)
Of course it makes it noisier! Diffuse transport is the easiest to render. What you see in the bottom images are complex specular-diffuse-specular paths that are difficult for the renderer (I assume bidirectional path tracing has been used here). One option would be to discard such paths. This would mean that you'll be missing reflections of caustics.
-
Higher glossiness makes renders more noisy. What a strange renderer. :)
Of course it makes it noisier! Diffuse transport is the easiest to render. What you see in the bottom images are complex specular-diffuse-specular paths that are difficult for the renderer (I assume bidirectional path tracing has been used here). One option would be to discard such paths. This would mean that you'll be missing reflections of caustics.
Sure, but if you are using some, ehm... other renderers, that can only do lambertian BRDF with irradiance caching, and rest with very slow path tracing, then glossy specular is the most difficult mode ;) (SDS gets clamped, vray does only E(S*|D)D*L anyway)
-
I still can't see why you'd want one material to be as is, but others to have glossiness at 1.0, you've utterly lost me.
-
I still can't see why you'd want one material to be as is, but others to have glossiness at 1.0, you've utterly lost me.
i do not want that anymore :) folks over here and test proves me "redudancy and uselesness" of this feature :)
I thought that corona works in different way :)
-
Sure, but if you are using some, ehm... other renderers, that can only do lambertian BRDF with irradiance caching, and rest with very slow path tracing, then glossy specular is the most difficult mode ;) (SDS gets clamped, vray does only E(S*|D)D*L anyway)
Of course. I was speaking in the context of the renderer used in the test above.