Goran Begicevic <gor### [at] tidaxse> wrote:
: be to use bezier curves for this. It would rule-out hand-writing scenes
: with motion blur, but who cares. It's time to say goodbye to it anyway

  Nonsense. You will never be able to achieve the same functionality that
a scripting language gives you with a graphical modeller. There will always
be very handy things that are quite easy to write but completely impossible
to achieve with a modeller (unless the modeller supports a scripting
language by itself, of course).
  The good thing about a scripting language is that you can program (almost)
anything you will which is not directly supported by povray. For example look
at Chris Colefax's include files. The things they do are not directly
supported by povray (there are no keywords for them), but they are perfectly
possible and quite easy to make.
  Now, you can never achieve this kind of flexibility with a modeller.
  Most advanced modellers have their own scripting language for this reason.
  And besides, certain things are just easier to try by hand.

: 3. While rendering , every time that ray intersects this motion-blur
: bounding box, object should be jittered across it's motion path in
: time-domain and re-tested with same ray. This would give us oversampled
: Monte-Carlo approximation of it's blurred trail. It will also work
: satisfactory with shadows, reflections and such.

  It will look very grainy. Like current media or focal blur with a small
confidence (like the default one).
  You can get a very good idea of how slow it will be by putting a plane
at the focal_point, differencing a hole in it and putting some object behind
it and then rendering with focal blur with a high enough confidence
(like 0.999).

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message