 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
What type of values can I input for the max_gradient of the parametric object?
The docs don't give a default value, or describe what the effect of changing
the values are. Also, the example provided in the docs has two question marks
("??") instead of a float value. This causes the render not to start.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> What type of values can I input for the max_gradient of the parametric
> object?
> The docs don't give a default value, or describe what the effect of
> changing
> the values are. Also, the example provided in the docs has two question
> marks
> ("??") instead of a float value. This causes the render not to start.
This is the same as for isosurfaces, I think, so the default would be 1.1.
Larger numbers render slower... it's a float value so you can turn it up
if you are willing to wait... and you can look at the discovered
max_gradient warning to set it just a bit over what is needed.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tim Attwood napsal(a):
>> What type of values can I input for the max_gradient of the parametric
>> object?
>> The docs don't give a default value, or describe what the effect of
>> changing
>> the values are. Also, the example provided in the docs has two question
>> marks
>> ("??") instead of a float value. This causes the render not to start.
>
> This is the same as for isosurfaces, I think, so the default would be 1.1.
> Larger numbers render slower... it's a float value so you can turn it up
> if you are willing to wait... and you can look at the discovered
> max_gradient warning to set it just a bit over what is needed.
>
>
I always use precompute 20 x,y,z. It doesn't take much time to parse and
renders a lot faster.
Also, I try to avoid parametrics whenever possible.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jan Dvorak <jan### [at] centrum cz> wrote:
> I always use precompute 20 x,y,z. It doesn't take much time to parse and
> renders a lot faster.
> Also, I try to avoid parametrics whenever possible.
Yeah, they're really slow.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> I always use precompute 20 x,y,z. It doesn't take much time to parse and
>> renders a lot faster.
>> Also, I try to avoid parametrics whenever possible.
>
> Yeah, they're really slow.
>
You can make parametrics much faster by converting them into
meshes with Ingo's meshmerizing macros.
http://code.google.com/p/mmgm/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Tim Attwood" <tim### [at] comcastnet> wrote:
> >> I always use precompute 20 x,y,z. It doesn't take much time to parse and
> >> renders a lot faster.
> >> Also, I try to avoid parametrics whenever possible.
> >
> > Yeah, they're really slow.
> >
> You can make parametrics much faster by converting them into
> meshes with Ingo's meshmerizing macros.
> http://code.google.com/p/mmgm/
Thanks for the tip! I'll have to try that.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
