I think that this list should be divided into more subcategories. For
example:

: panoramic projection bug? (job000196)
: (When "angle" keyword within camera statement appears after "panoramic"
: keyword then looks like ignored.)
: http://news.povray.org/avnfut8fof5ualgf8hnrtpl1knlg8828sp@4ax.com

  This could be in an "under work" category. The "bug" does not exist anymore
in the same way as it was reported, but something has been done about it,
although it's not yet a definitive fix (it's a fix which is still under
developement). IMO it's wrong to have this in its original form as it's not
the case anymore.

: non hollow flat disc
: http://news.povray.org/mi9t3uophkvlv9hfah5uv7enn2pamhuvd7@4ax.com

  This is not a bug and thus it's IMO wrongly listed as one. The disc object
was originally designed to work as it does currently, and it works as designed,
and thus it's not buggy.
  Of course another question is whether the current behaviour is the best one,
but that's a discussion about a feature change, not a bug fix.
  I think that some subcategory should be made for this kind of things.

: max_trace_level affects radiosity recursion_limit
: ((beta 10) max_trace_level sets an upper bound on recursion_limit)
: http://news.povray.org/3BE40295.6C3D54DE@engineer.com

  This is another example of something which is most probably not a bug, but
a design decision. It should go under the same category as the previous one
(ie. it's a feature to be changed, not a bug to be fixed).

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

On 21 Jan 2002 07:35:35 -0500, Warp <war### [at] tagpovrayorg> wrote:
> : non hollow flat disc
> : http://news.povray.org/mi9t3uophkvlv9hfah5uv7enn2pamhuvd7@4ax.com
>
>  This is not a bug and thus it's IMO wrongly listed as one. The disc object
> was originally designed to work as it does currently, and it works as designed,
> and thus it's not buggy.
>  Of course another question is whether the current behaviour is the best one,
> but that's a discussion about a feature change, not a bug fix.
>   I think that some subcategory should be made for this kind of things.

At least it is a documentation bug. Documentation says disc is another 'finite'
but considering discussed design it is infinite and it is simple to show it
with:

#include "strings"
#local P=rgb 1;
#local At=-y;
#while(P.gray=1)
  #local P=eval_pigment(pigment{object{disc{0 y 1}color rgb 0 color rgb 1}},At);
  #local At=At-y;
  #debug concat(CRGBStr(P, 0, -1),"\n")
#end

ABX

Post a reply to this message

>On Mon, 21 Jan 2002 06:19:15 +0000, Mike Williams <mik### [at] nospamplease> wrote:
>> Function declaration and namespace
>> (?)
>> http://news.povray.org/l2ji3uc2k9su99o2gct3n2thgqoq7f4pd5@4ax.com
>>
>> splines - documentation and reality
>> (?)
>> http://news.povray.org/m7fq3u41ctia9e6i3tbnlstn6ek739vpke@4ax.com
>
>What are those '(?)' ?

They are apparently confirmed bugs, but I can't work out from reading
the thread what it is that actually got confirmed.

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

>On 21 Jan 2002 07:35:35 -0500, Warp <war### [at] tagpovrayorg> wrote:
>> : non hollow flat disc
>> : http://news.povray.org/mi9t3uophkvlv9hfah5uv7enn2pamhuvd7@4ax.com
>>
>>  This is not a bug and thus it's IMO wrongly listed as one. The disc object
>> was originally designed to work as it does currently, and it works as 
>designed,
>> and thus it's not buggy.
>>  Of course another question is whether the current behaviour is the best one,
>> but that's a discussion about a feature change, not a bug fix.
>>   I think that some subcategory should be made for this kind of things.
>
>At least it is a documentation bug. Documentation says disc is another 'finite'
>but considering discussed design it is infinite and it is simple to show it
>with:
>
>#include "strings"
>#local P=rgb 1;
>#local At=-y;
>#while(P.gray=1)
>  #local P=eval_pigment(pigment{object{disc{0 y 1}color rgb 0 color rgb 1}},At);
>  #local At=At-y;
>  #debug concat(CRGBStr(P, 0, -1),"\n")
>#end

I'll move it into my "unconfirmed" file for now.

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

I've checked the bug list and couldn't find anything that looks like it
has to do with the "Severe Lightbug, probably concerned with
Macros... (long post)", and I came across it again. The bug isn't
that easy to reproduce.
In the newest case I've used macros to place Objects again,
and now, I get red (!) artefacts on a CSG-difference-surface.

Actually, I've differenced a cone and two spheres from a
superellipsoid, and depending on angle towards the CSG-
hole, red artefacts appear at the rim, or even areas of the
surface. They're not randomly scattered like the typical
coincidence surface problem, and their also RED, which I
think is somewhat strange, since there is no pure red
in scene (only shades of grey). In this case, commenting out
a variable reflection with falloff and exponent cures the
bug, but that is actually needed!

Perhaps someone could at least download the scene-files I
posted and either confirm or deny the appearance. But this
one really starts to bug me, I thought macros would make
object-creation much easier... :(

Thanks, although I am probably creating some trouble, and
being excuse me for be annoying...
I really think it's a bug!

Tim
--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html

Post a reply to this message

Mike Williams wrote:


> bug : declared camera with normal statement crashes
> (In b10 it no longer crashes, but it just errors)
> http://news.povray.org/3C41A226.7030703@skynet.be


It still crashes on my machine with b10. (same conditions as in
first report).

Fabien.

Post a reply to this message

Wasn't it Tim Nikias who wrote:
>I've checked the bug list and couldn't find anything that looks like it
>has to do with the "Severe Lightbug, probably concerned with
>Macros... (long post)"

The "Known Bugs" list only contains confirmed bugs. That one is on my
"Unconfirmed Bugs" list at present.

Your post may well have been cancelled (due to binary attachment in a
non-binary newsgroup) before many people saw it.

Your posting of the source code to povray.beta-test.binaries was
legitimate, but didn't mention what it was that you considered to be
wrong with the included scene.

-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

>
> Your posting of the source code to povray.beta-test.binaries was
> legitimate, but didn't mention what it was that you considered to be
> wrong with the included scene.
>

I'll add a post there to clear it up...

--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html

Post a reply to this message

Mike Williams wrote in message <4M9### [at] econymdemoncouk>...

>>On Mon, 21 Jan 2002 06:19:15 +0000, Mike Williams <mik### [at] nospamplease>
wrote:
>>> Function declaration and namespace
>>> (?)
>>> http://news.povray.org/l2ji3uc2k9su99o2gct3n2thgqoq7f4pd5@4ax.com
>>>
>>> splines - documentation and reality
>>> (?)
>>> http://news.povray.org/m7fq3u41ctia9e6i3tbnlstn6ek739vpke@4ax.com
>>
>>What are those '(?)' ?
>
>They are apparently confirmed bugs, but I can't work out from reading
>the thread what it is that actually got confirmed.


>>> splines - documentation and reality
>>> (?)
>>> http://news.povray.org/m7fq3u41ctia9e6i3tbnlstn6ek739vpke@4ax.com

This one is a bug; I've confirmed it and the source code modifications to
fix it are sitting in my reply to the original post, waiting for a POV-Team
member to add them to the POV 3.5 source.

--
Mark

Post a reply to this message

> [Windows] Save As... with same filename doesn't work
> http://news.povray.org/3c44497e$1@news.povray.org
>
> [...]
>
> [Windows] Save As... with same filename doesn't work
> http://news.povray.org/3c44497e$1@news.povray.org

This bug is listed twice.

Post a reply to this message