 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
AFAICS, "eval" in isosurfaces in version 0.6 of MegaPOV doesn't report
max_gradient like it should. The same scene in MegaPOV 0.5 works just fine.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tony[B] <ben### [at] panama c-comnet> wrote:
> AFAICS, "eval" in isosurfaces in version 0.6 of MegaPOV doesn't report
> max_gradient like it should. The same scene in MegaPOV 0.5 works just fine.
Fixed it again in MP 0.6a.
Smellenbergh
--
e-mail:sme### [at] skynetbe
http://users.skynet.be/smellenbergh
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Fixed it again in MP 0.6a.
Again? Oh, well, it's sweet anyway. Thanks. :) Are you waiting for more
bugs to surface, or will you put it out soon.
BTW, does anyone here feel the need to make a test file that uses all of
MegaPOV's features in one scene? I mean, just run that, and you can tell
right away if a bug has been introduced.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <39e0c15f@news.povray.org>, "Tony[B]"
<ben### [at] panamac-comnet> wrote:
> BTW, does anyone here feel the need to make a test file that uses all of
> MegaPOV's features in one scene? I mean, just run that, and you can tell
> right away if a bug has been introduced.
Some bugs will only surface with certain combinations of features...and
if a feature is changed to behave differently(the new noise function),
is partly random(blurred reflection, radiosity, etc), or affects the
whole output to the exclusion of other features(some post_process
filters), you will run into trouble. And when something does go wrong,
having everything in one scene file will make it harder to find.
A better idea would be a set of files testing the features in the most
common situations, this would be more useful and easier to maintain, but
it would still be a lot of work to create these files.
--
Christopher James Huff
Personal: chr### [at] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/
<><
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tony[B] <ben### [at] panamac-comnet> wrote:
> > Fixed it again in MP 0.6a.
>
> Again? Oh, well, it's sweet anyway. Thanks. :) Are you waiting for more
> bugs to surface, or will you put it out soon.
Well, not again but simply fixed. This happens when you think in dutch
while trying to write english :-)
Don't know yet when exactly 0.6a will be out. We don't want to wait too
long because there are some serious bugs in 0.6.
However, as you suggest, waiting a bit might be the right way to go.
Don't know what Nathan's point of view is at this time.
> BTW, does anyone here feel the need to make a test file that uses all of
> MegaPOV's features in one scene? I mean, just run that, and you can tell
> right away if a bug has been introduced.
It's a good idea but actually writing such a scene is something else.
Have you any idea how complex the syntax is? We added dialog templates
in our GUI for almost every feature of POV-Ray/MegaPOV (to see what we
mean, there are some screenhots on our home page).
We had to look for every keyword where and how it can be used. If you
see all the possible combinations and exceptions you will realise that
it is just not possible to have it all in one scene.
We rendered *all* demo scenes before releasing 0.6. Those scenes should
cover all new features in MegaPOV but even this wasn't enough to
discover those bugs in 0.6.
Smellenbergh
--
e-mail:sme### [at] skynetbe
http://users.skynet.be/smellenbergh
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
