 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3C447B93.CC3C8553@gmx.de> , Christoph Hormann
<chr### [at] gmx de> wrote:
>> It is by design for _this_ beta and part of the changes to the output that
>> have been in progress for several weeks now until a final solution can be
>> found. The previous beta versions' output was incorrect, the current change
>> only disables the incorrect output without providing the correct output yet.
>>
>
> I suppose this means that part is still subject to change and i should
> wait with writing the announced doc part.
Only the "evaluate" part, that ios the "dynamic method" part, is subject to
change. Using the method with the constant max_gradient I expect no need
for changes.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"R. Suzuki" <r-s### [at] aistgojp> wrote in message
> That is useful in some cases. For example, try the following JRG's
> code with "evaluate 1.2, 1.1, 0.98" instead of "evaluate 1, 10, 0.99".
> http://news.povray.org/3bdf2d82%40news.povray.org
> The rendering speed would be faster than the fixed max_gradient.
>
> Those parameters of the recent beta work as designed.
> The description of those parameters can be seen at
> http://news.povray.org/3be10cf9@news.povray.org
>
Both of these messages are in the same thread and I had read it at least twice.
But reading it a third time in the context of your explanation of the useful
cases, seems to have helped. I wasn't clear until now exactly what the 'user
error' was. Thanks for helping to clarify.
--
light_source{0,1}#macro c(J,a)sphere{0,1pigment{rgb z}scale a translate J+O}
#end#macro B(R,V,O)c(0,4)intersection{c(V,R)difference{c(-z*4x+10)c(-z*4.1x+
10)c(0<7.5,45,5>)}}#end B(12,0z*25)B(8y*4<0,12,50>) // Batronyx ^"^
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wasn't it Coridon Henshaw who wrote:
>Incidentally, do you have a current list of unconfirmed bugs? I'd like to
>go through it and look for confirmable problems.
This isn't completely up to date. I've been a bit busy recently.
max_trace_level affects radiosity recursion_limit
(Setting max_trace_level 1 disables radiosity and max_trace_level 2 sets
recursion_limit to 1)
http://news.povray.org/3BE40295.6C3D54DE@engineer.com
Bugs with string/macro handling
http://news.povray.org/3be76148$1@news.povray.org
Philosophical objection to fog distance=0
(Fog colour is then ignored)
http://news.povray.org/3BE7E897.FEC8EF6@aol.com
Animated textures
(memory usage goes quite high)
http://news.povray.org/3bea26bf@news.povray.org
Isosurface *disappears* at high resolution (fwd)
http://news.povray.org/3bb0b351@news.povray.org
Media visible container line in front of object
(a visible whitish line appears at the edge of a transparent container
box for media)
http://news.povray.org/3bf45a3d@news.povray.org
Priority troubles
(higher priorities cause slower render)
http://news.povray.org/
[win gui] line with error highlighted but render finished succesfully
http://news.povray.org/va2tvt4tuitd67ik5t9ps334sbg6205bt3@4ax.com
var_refl.pov (\scenes\textues\finishes) Beta 8
(should #include "functions.inc")
http://news.povray.org/3C0A9650.6B98925@compuserve.com
transform syntax
(transform {test_trans} sometimes requires {} and sometimes doesn't)
http://news.povray.org/3C09EE1B.A38DC91A@gmx.de
Win Beta 8: Message window/parse hang error?
(hangs after "Degenerate Blob" warning)
http://news.povray.org/3c0bdc77@news.povray.org
another bug I haven't seen mentioned
(Yellow band around sky_sphere equator)
http://news.povray.org/3c10ef62$1@news.povray.org
media & fog bug?
http://news.povray.org/3c1379e0$1@news.povray.org
bug in sphere_sweep for removing parts of an object
(parameterised sphere_sweeps are very slow. May or may not be related to
job000176)
http://news.povray.org/3C1A5D47.EA38F6E5@amc.uva.nl
Re: Mosaic... some clarifications
(#local A2=P(1,2,3).hf; fails)
http://news.povray.org/9n9j1uo0mdlrs4i5toupujr0pqrj4vvb8d@4ax.com
Re: hollow in light groups
http://news.povray.org/3c21172d$1@news.povray.org
Is there a problem with area light
http://news.povray.org/3c22f013@news.povray.org
Bug with transform syntax
http://news.povray.org/chrishuff-5FC1B7.19310427122001@netplex.aussie.or
g
Minor Windows annoyance
http://news.povray.org/3c2bec89@news.povray.org
[linux] Rendering without display on the console.
http://news.povray.org/3c3f0a80@news.povray.org
Beta 10 bugs
(Demo scenes in scenes\camera\ will not parse)
http://news.povray.org/Xns9197A5B08390CCQ@204.213.191.226
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 16 Jan 2002 11:57:38 -0500, Mike Williams wrote:
> Wasn't it Coridon Henshaw who wrote:
>
>>Incidentally, do you have a current list of unconfirmed bugs? I'd like
>>to go through it and look for confirmable problems.
>
> This isn't completely up to date. I've been a bit busy recently.
> [linux] Rendering without display on the console.
> http://news.povray.org/3c3f0a80@news.povray.org
Fixed in Beta 10.
-Mark Gordon
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Williams <mik### [at] nospamplease> wrote in
news:4gz### [at] econymdemoncouk:
> max_trace_level affects radiosity recursion_limit
> (Setting max_trace_level 1 disables radiosity and max_trace_level 2
> sets recursion_limit to 1)
> http://news.povray.org/3BE40295.6C3D54DE@engineer.com
I can confirm portions of this report. While reducing max_trace_level to 1
does not disable radiosity under beta 10, max_trace_level does appear to
impose an upper bound on recursion_limit. recursion_limit settings in
excess of the max_trace_level appear to be ignored.
> Bugs with string/macro handling
> http://news.povray.org/3be76148$1@news.povray.org
Partial confirmation. I can get error cases #1 (Too many nested symbol
tables) and #2 ("BCFGHJKLMQSUVWXY") but none of the others.
At first glance that the original poster is trying to do with the scene
description language is somewhat akin to driving nails with a shoe. As
such I am unsure if this problem should be fixed or if the workaround
should be 'reimplement your code in perl, Python, rexx, or C.'
> Philosophical objection to fog distance=0
> (Fog colour is then ignored)
> http://news.povray.org/3BE7E897.FEC8EF6@aol.com
Confirmed that the code provided works as the original poster stated.
> Animated textures
> (memory usage goes quite high)
> http://news.povray.org/3bea26bf@news.povray.org
Not tested. I suspect this bug might be another incarnation of one of the
various memory leaks reported elsewhere.
> Isosurface *disappears* at high resolution (fwd)
> http://news.povray.org/3bb0b351@news.povray.org
Cannot duplicate.
> Media visible container line in front of object
> (a visible whitish line appears at the edge of a transparent container
> box for media)
> http://news.povray.org/3bf45a3d@news.povray.org
Confirmed. This problem can be masked--but not eliminated--with
antialiasing.
> Priority troubles
> (higher priorities cause slower render)
> http://news.povray.org/
Uhhh, message-id? ;-)
> [win gui] line with error highlighted but render finished succesfully
> http://news.povray.org/va2tvt4tuitd67ik5t9ps334sbg6205bt3@4ax.com
Not tested specifically, but I've run into this problem before with
ordinary parsing errors (e.g. undeclared identifiers) not related to
#fopen.
> var_refl.pov (\scenes\textues\finishes) Beta 8
> (should #include "functions.inc")
> http://news.povray.org/3C0A9650.6B98925@compuserve.com
Cannot duplicate.
> transform syntax
> (transform {test_trans} sometimes requires {} and sometimes doesn't)
> http://news.povray.org/3C09EE1B.A38DC91A@gmx.de
Confirmed.
> Win Beta 8: Message window/parse hang error?
> (hangs after "Degenerate Blob" warning)
> http://news.povray.org/3c0bdc77@news.povray.org
Insufficient data to make a determination.
A generic scene containing a single degenerate blob did not cause pov to
lock up.
> another bug I haven't seen mentioned
> (Yellow band around sky_sphere equator)
> http://news.povray.org/3c10ef62$1@news.povray.org
Cannot duplicate with the following scene:
sky_sphere {pigment {gradient y triangle_wave color_map {[0 rgb 0] [1 rgb
1]}}}
If the original poster can provide a sample scene I will try again.
> media & fog bug?
> http://news.povray.org/3c1379e0$1@news.povray.org
Confirmed.
> bug in sphere_sweep for removing parts of an object
> (parameterised sphere_sweeps are very slow. May or may not be related
> to job000176)
> http://news.povray.org/3C1A5D47.EA38F6E5@amc.uva.nl
Confirmed.
> Re: Mosaic... some clarifications
> (#local A2=P(1,2,3).hf; fails)
> http://news.povray.org/9n9j1uo0mdlrs4i5toupujr0pqrj4vvb8d@4ax.com
Confirmed.
> Re: hollow in light groups
> http://news.povray.org/3c21172d$1@news.povray.org
Confirmed.
> Is there a problem with area light
> http://news.povray.org/3c22f013@news.povray.org
Cannot duplicate. area_light settings which produce smooth shadows under
3.1 also produce smooth shadows under 3.5.
> Bug with transform syntax
> http://news.povray.org/chrishuff-5FC1B7.19310427122001@netplex.aussie.or
> g
Confirmed.
> Minor Windows annoyance
> http://news.povray.org/3c2bec89@news.povray.org
Chris Cason said (in <3c2c6b4a@news.povray.org>) that he's looking into
this one.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
che### [at] sympaticoca (Coridon Henshaw) wrote in
news:Xns### [at] 204213191226:
>> Isosurface *disappears* at high resolution (fwd)
>> http://news.povray.org/3bb0b351@news.povray.org
>
> Cannot duplicate.
Correction. Confirmed.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <Xns### [at] 204213191226> ,
che### [at] sympaticoca (Coridon Henshaw) wrote:
> che### [at] sympaticoca (Coridon Henshaw) wrote in
> news:Xns### [at] 204213191226:
>
>>> Isosurface *disappears* at high resolution (fwd)
>>> http://news.povray.org/3bb0b351@news.povray.org
>>
>> Cannot duplicate.
>
> Correction. Confirmed.
This "bug" never was one as explained in the same thread.
I am surprised it is still in the unconfirmed list at all...
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" wrote:
>It is by design for _this_ beta and part of the changes to the
>output that have been in progress for several weeks now until a
>final solution can be found. The previous beta versions' output
>was incorrect, the current change only disables the incorrect
>output without providing the correct output yet.
If you want to change the output of 'evaluate' more helpful,
please add "maximum gradient variation" between neighboring rays.
[grad_var = abs(max_grad(Nth ray)-max_grad((N-1)th ray) ) ]
Then, the parameters of 'evaluate' for dynamic max_gradient estimation
should be as follows,
1st parameter < max_grad
1 < 2nd parameter < max_grad/(max_grad - max_grad_var)
1 > 3rd parameter > 1/(2nd parameter)
R. Suzuki
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Coridon Henshaw wrote in message ...
>> Bugs with string/macro handling
>> http://news.povray.org/3be76148$1@news.povray.org
>
>Partial confirmation. I can get error cases #1 (Too many nested symbol
>tables) and #2 ("BCFGHJKLMQSUVWXY") but none of the others.
>
>At first glance that the original poster is trying to do with the scene
>description language is somewhat akin to driving nails with a shoe. As
>such I am unsure if this problem should be fixed or if the workaround
>should be 'reimplement your code in perl, Python, rexx, or C.'
I'm doing this in SDL for much the same reason that Warp wrote the SDL
raytracer and I wrote my POV-Ray Scene Virus -- to show that it can be done.
--
Mark
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wasn't it Coridon Henshaw who wrote:
>Mike Williams <mik### [at] nospamplease> wrote in
>news:4gz### [at] econymdemoncouk:
>
>> max_trace_level affects radiosity recursion_limit
>> (Setting max_trace_level 1 disables radiosity and max_trace_level 2
>> sets recursion_limit to 1)
>> http://news.povray.org/3BE40295.6C3D54DE@engineer.com
>
>I can confirm portions of this report. While reducing max_trace_level to 1
>does not disable radiosity under beta 10, max_trace_level does appear to
>impose an upper bound on recursion_limit. recursion_limit settings in
>excess of the max_trace_level appear to be ignored.
Thanks. Added to known bugs.
>> Bugs with string/macro handling
>> http://news.povray.org/3be76148$1@news.povray.org
>
>Partial confirmation. I can get error cases #1 (Too many nested symbol
>tables) and #2 ("BCFGHJKLMQSUVWXY") but none of the others.
>
>At first glance that the original poster is trying to do with the scene
>description language is somewhat akin to driving nails with a shoe. As
>such I am unsure if this problem should be fixed or if the workaround
>should be 'reimplement your code in perl, Python, rexx, or C.'
I think I'll move that into the "not a bug" box, unless anyone has
serious objections.
>> Philosophical objection to fog distance=0
>> (Fog colour is then ignored)
>> http://news.povray.org/3BE7E897.FEC8EF6@aol.com
>
>Confirmed that the code provided works as the original poster stated.
I knew that, the question is whether the code should behave that way or
not.
>> Animated textures
>> (memory usage goes quite high)
>> http://news.povray.org/3bea26bf@news.povray.org
>
>Not tested. I suspect this bug might be another incarnation of one of the
>various memory leaks reported elsewhere.
>> Isosurface *disappears* at high resolution (fwd)
>> http://news.povray.org/3bb0b351@news.povray.org
>
>Cannot duplicate.
I can duplicate this (although the quick version that I wrote now runs
to completion). The point at which the quick version collapsed into
blankness has varied from beta to beta, and now manages to go all the
way through. The original scene file posted by Warp still fails when
rendered with the specified size and antialliassing.
The question is whether this is a bug, or whether isosurfaces that use
crackle can legitimately be expected to disappear.
>
>> Media visible container line in front of object
>> (a visible whitish line appears at the edge of a transparent container
>> box for media)
>> http://news.povray.org/3bf45a3d@news.povray.org
>
>Confirmed. This problem can be masked--but not eliminated--with
>antialiasing.
Thanks. Added to known bugs.
>
>> Priority troubles
>> (higher priorities cause slower render)
>> http://news.povray.org/
>
>Uhhh, message-id? ;-)
3BF4B750.39EA34A7@joplin.com
>
>> [win gui] line with error highlighted but render finished succesfully
>> http://news.povray.org/va2tvt4tuitd67ik5t9ps334sbg6205bt3@4ax.com
>
>Not tested specifically, but I've run into this problem before with
>ordinary parsing errors (e.g. undeclared identifiers) not related to
>#fopen.
Thanks. I'll add that to known bugs.
>> var_refl.pov (\scenes\textues\finishes) Beta 8
>> (should #include "functions.inc")
>> http://news.povray.org/3C0A9650.6B98925@compuserve.com
>
>Cannot duplicate.
>
>> transform syntax
>> (transform {test_trans} sometimes requires {} and sometimes doesn't)
>> http://news.povray.org/3C09EE1B.A38DC91A@gmx.de
>
>Confirmed.
Thanks. Added to known bugs.
>> Win Beta 8: Message window/parse hang error?
>> (hangs after "Degenerate Blob" warning)
>> http://news.povray.org/3c0bdc77@news.povray.org
>
>Insufficient data to make a determination.
>
>A generic scene containing a single degenerate blob did not cause pov to
>lock up.
>
>> another bug I haven't seen mentioned
>> (Yellow band around sky_sphere equator)
>> http://news.povray.org/3c10ef62$1@news.povray.org
>
>Cannot duplicate with the following scene:
>
>sky_sphere {pigment {gradient y triangle_wave color_map {[0 rgb 0] [1 rgb
>1]}}}
>
>If the original poster can provide a sample scene I will try again.
>
>> media & fog bug?
>> http://news.povray.org/3c1379e0$1@news.povray.org
>
>Confirmed.
Thanks. Added to known bugs.
>> bug in sphere_sweep for removing parts of an object
>> (parameterised sphere_sweeps are very slow. May or may not be related
>> to job000176)
>> http://news.povray.org/3C1A5D47.EA38F6E5@amc.uva.nl
>
>Confirmed.
Thanks. Added to known bugs.
>> Re: Mosaic... some clarifications
>> (#local A2=P(1,2,3).hf; fails)
>> http://news.povray.org/9n9j1uo0mdlrs4i5toupujr0pqrj4vvb8d@4ax.com
>
>Confirmed.
Thanks. Added to known bugs.
>> Re: hollow in light groups
>> http://news.povray.org/3c21172d$1@news.povray.org
>
>Confirmed.
Thanks. Added to known bugs.
>> Is there a problem with area light
>> http://news.povray.org/3c22f013@news.povray.org
>
>Cannot duplicate. area_light settings which produce smooth shadows under
>3.1 also produce smooth shadows under 3.5.
>
>> Bug with transform syntax
>> http://news.povray.org/chrishuff-5FC1B7.19310427122001@netplex.aussie.or
>> g
>
>Confirmed.
Thanks. Added to known bugs.
>> Minor Windows annoyance
>> http://news.povray.org/3c2bec89@news.povray.org
>
>Chris Cason said (in <3c2c6b4a@news.povray.org>) that he's looking into
>this one.
Thanks. Added to known bugs.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
