Dave Dunn <poi### [at] aolcom> wrote:
: Reflection blur - I've seen enough workarounds in these groups to know this
: is needed.

  Why? With the "workarounds" you get a nicer result, often even faster. It's
also more versatile, as you can scale non-uniformly the blur amount, and even
make the blurring amount to follow a pattern (or function). This is not
possible with the "hack" in megapov.

: Heightfield_height_at (no way trace works better on hfs, sorry).

  I don't understand why not.
  Tracing is also a lot more versatile than height_at, as you can trace also
from other directions than just directly from above (for example suppose that
you want to simulate meteorites falling and creating holes on a heightfield
at an angle of 60 degrees). Tracing also works if you have a union of a
heightfield with other primitives, which is just not possible with height_at.

: Text object enhancements (why use a macro when you can just use this?).

  Why not?

  I have explained several times why using macros is better than making an
internal feature (if the macro is not annoyingly slower). Macros should always
be preferred to internal support whenever possible.
  Macros are more versatile (internal support is fixed and rigid), changeable
(you can't change internal support) and you can learn from macros (they are
much more readable than reading the povray source code) and make your own
macros based on it.

: Ini_option (why in the world was this removed?).

  Because it breaks the boundaries of what a scene file should be able to
do. It's up to the user to specify rendering settings (such as image
resolution), not the scene file.
  Suppose that you have a really huge scene file with an extremely obfuscated
ini_option which sets the resolution of the rendering to 500000x500000 pixels.
Happy swapping then...

: Mesh Type 2 (parsed much faster and came out smoother).

  Uh? You mean pov3.5 has no mesh2?
  And what do you mean "smoother"?

: OK, there are a few things I like about 3.5 Beta+, like the easier
: dispersion and improved functions (especially for isos), but, let's face
: it, MegaPOV in general is more powerful.

  Not that more powerful. Most of the things you said made just no sense.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message