Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
The minimum radius is clamped to avoid the problems that happen with loss of precision with really small values. Similar problems happen if you're really really far from the origin. This is a limitation of floating point precision, so unless we can come up with some alternative approach or tradeoff, the clamping stays.
It's a shame to hear that. I can remember it worked in early releases. Maybe it was wrong in some way, but there was a result. The only way to get something useful is to scale up the whole scene. (Not really a solution for complex setups...).
Its one of the features that makes Arnold so unique compare to others engines. I hope there will be some improvements.
The default export scale in C4D is set to 1 meter, yet it needs to be set to 0.01 meter to honor the internal default dimensions withing c4d. The sss density scaling works fine enough then, so its no bug.
is there a chance of actually documenting this limitation? Obviously, quite a few people run into this, e.g when rendering thin features like flowers, leaves (which might have thickness for a closeup).
The only way to find out it exists right now is to google exactly the right terms and arrive here and a few other places.
We were able to further improve this limit in Arnold 5.3 (released a couple months after the initial problem in this post was reported). Are you still seeing issues in 5.3 or newer?
