|
![](/i/fill.gif) |
"Slime" <slm### [at] slimeland com> wrote in news:3e307631$1@news.povray.org:
> The problem with all of these no_something flags is that they're not
> backwards compatible. For instance, right now, objects have:
Ack!! Backwards compatibility should NEVER be a factor in determining
features of new versions of *any* software. The POV syntax is plain text,
it's easy to edit a scene to fix/replace old code with new. It might be
time consuming (I'm currently converting an old 3.1 scene that used Halos
extensively) but it isn't hard. It's not even an issue of some people not
wanting to upgrade to the latest version of POVRay because they can't
afford the upgrade price. <smile> Backwards compatibility is the bane of
all programmers!
I *really* want some kind of keyword that allows me to turn off radiosity
calculations on an object-by-object basis, so I can use iso's in a
radiosity scene without POV taking days between test renders. <grin>
--
Rich Allen
(Remove SPAM from my address to reply by e-mail)
Post a reply to this message
|
![](/i/fill.gif) |