Simon Adameit <gom### [at] gmxnet> wrote:
> What do you think of this idea?

  Can you suggest an implementation which doesn't consume tons of memory
and is as fast to render as the current when those extra features are not
used?
  Each extra feature you add to a texture will increase the amount of
memory taken by that texture, even if the feature is not used (because
the code needs to somehow be prepared to support that feature if it is
used) and extra checks need to be implemented to see if the extra
features are used or not.
  It isn't heavy to have a possible map for a texture, pigment and
normal, but if you are going to add support for a map go each and every
feature inside them...

  I'm not saying it wouldn't be possible to do it without noticeable
speed/memory penalty, I'm just thinking out loud as a coder. Implementation
details always need to be considered when suggesting new features.

  And would there be some advantage over texture maps?

-- 
#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