Chaos Corona Forum
General Category => Porting and API => [Archive] Chaos Corona for Maya => Topic started by: AndrewAdler on 2015-03-22, 21:04:43
-
if i set glossiness parameter below 0.300
i start to see mesh of object
Is it ok?
-
Apply turbosmooth and if already applied then increase it.
Sorry
For Maya increase smoothness.
-
I think that's not right, are you sure this happens in max also luvualld?
A sphere with that level of subdivision, at least the right one, should not present this effect I think (I may be wrong).
Cheers.
-
Apply turbosmooth and if already applied then increase it.
Sorry
For Maya increase smoothness.
Thanks for the tip.
sphere on the left has 1600 faces
to look smooth sphere it is necessary to have approximately 25280 faces
if you increase the smoothing, than the problem is solved but the geometry becomes very heavy.
-
I think that's not right, are you sure this happens in max also luvualld?
A sphere with that level of subdivision, at least the right one, should not present this effect I think (I may be wrong).
Cheers.
juang3d
I agree with you
I also think that the detail is high enough to smooth
-
I'll have a look.
-
Sphere from the right has (6400 faces)
Sphere from the left has (25280 faces) after applying smoothing
-
It's an issue of all unbiased renderers
At now only solution is increasing the number of polygons
-
Thanks
now I'll know
-
Uwelcome! (;
You can read about it and more other issues and solutions here in extended Corona Renderer Helpdesk: https://coronarenderer.freshdesk.com/support/solutions/articles/5000516258-objects-in-my-rendering-are-not-smooth-faceted-and-i-can-see-shadows-of-polygons-
-
No, it's not shadow terminator problem. I did a quick render in max with very low poly sphere and glossiness of 0.25. And although shadow terminator issue is very clear, you can see that there's no visible poligonal divisions in reflection whatsoever.
-
Romullus
Thanks for help
a mysterious situation
-
maya version currently still uses the old core version because I have not updated the licensing API yet, so it is perfectly plausible that that was a bug fixed in 1.0
-
This is good news!