Yeah, that'll work, but what if a person
receives a scene from someone else that
hasn't been set up that way and he doesn't
know how to edit scenes?

And who's to say that every scene writer
would choose the same constant names
for their quality options, anyway? There's
no guaranteed way to make a quickres.ini
entry that will turn off blur in every scene.

I'd say it's a bug: the quality INI setting
is intended to render scenes faster when
the quality is lower, but it doesn't
actually do that, because it lets some
high-quality features remain enabled.
Being able to work around the problem
isn't a solution, because expending the
effort for the workaround defeats the
very purpose of the Quality setting: to
provide an easy way to globally render
scenes faster without having to care
about the scene's content or code.

Ray


"Gilles Tran" <tra### [at] inapginrafr> wrote in message
news:3ee71132$1@news.povray.org...

> 3ee6e5ce@news.povray.org...
> > I just noticed that setting the quality lower
> > doesn't speed up scenes using camera blur.
> > Is there an INI option to disable a scene's
> > use of blur?
>
> When I say you really should using POV for real, lol.
> In addition to what ABX said, the usual way to deal with complex (or even
> less complex) scenes is to add switches at the beginning of your scene
that
> can turn on and off objects and features (or replace objects by dummies).
So
> it's like :
> #declare BlurOn=1;
> #declare RadiosityOn=2; // 0=no rad ; 1=test ; 2=final
> #declare MediaOn=1;
> #declare MyBigMeshOn=1;
> etc.
> This makes previewing and testing subsets of the scene very fast.
>
> G.
>
> --
>
> **********************
> http://www.oyonale.com
> **********************
> - Graphic experiments
> - POV-Ray and Poser computer images
> - Posters
>
>

Post a reply to this message