 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I most likely have missed this, but where can I find a recent list of known
bugs?
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Rune" wrote:
> I most likely have missed this, but where can I
> find a recent list of known bugs?
Hmm, no reply.
Without such a list I find it difficult to keep track on all the known bugs,
which ones have been fixed mean-while, which ones are still there, etc.
Currently there's a lot of messages that goes like "this bug is still there
in beta X". This could better be avoided if there was a list of known bugs
where beta testers could see that the Team is aware of the fact that this
and that bug haven't yet been fixed in the newest beta.
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 25 Sep 2001 21:27:16 +0200, Rune wrote:
>"Rune" wrote:
>> I most likely have missed this, but where can I
>> find a recent list of known bugs?
>
>Hmm, no reply.
>
>Without such a list I find it difficult to keep track on all the known bugs,
>which ones have been fixed mean-while, which ones are still there, etc.
>
>Currently there's a lot of messages that goes like "this bug is still there
>in beta X". This could better be avoided if there was a list of known bugs
>where beta testers could see that the Team is aware of the fact that this
>and that bug haven't yet been fixed in the newest beta.
Want me to send you the list of messages in this newsgroup that I have
marked unread? That's my list of known (or at least reported but not
yet investigated) bugs.
--
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbt 1}hollow interior{media{emission T}}finish{
reflection.1}}#end Z(-x-x.2y)Z(-x-x.4x)camera{location z*-10rotate x*90}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3bb0dafc@news.povray.org> , "Rune" <run### [at] mobilixnet dk>
wrote:
> Without such a list I find it difficult to keep track on all the known bugs,
> which ones have been fixed mean-while, which ones are still there, etc.
Why? It is very simple to find out: Each beta version includes a list of
*fixed* bugs in revision.txt. Obviously every bug not in that list has not
been fixed and does not need to be reported again. If you are unsure if a
sometimes cryptic bug fix description in that list means that your "pet bug"
has been fixed in a current beta, just refer to the change number, post in
the "beta X" announcement thread and someone will tell you (but don't expect
an immediate reply).
As Ken pointed out in the first message in this group, the users are
supposed to keep up with all bug reports posted in this group. If something
is reported already and the beta release notes (revision.txt) do not say it
is fixed, do *not* report it again as it just adds to the noise level in
this group. Of course, if the beta release notes claim it is fixed but it
is not, a new report is appropriate.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Ron Parker" wrote:
> Want me to send you the list of messages in this
> newsgroup that I have marked unread?
Yes please (the list of messages, not the messages themselves)
> That's my list of known (or at least reported but not
> yet investigated) bugs.
I don't think it can be expected of all the beta testers to do something
similar on their own. If I compile the messages from the list you send me
into a list of known bugs, would it be possible that someone from the Team
could update it as new beta versions are released?
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" wrote:
> As Ken pointed out in the first message in
> this group, the users are supposed to keep
> up with all bug reports posted in this group.
I know, but that's sometimes a difficult task with the massive amount of
messages, so I just thougt it could be a good idea to help the testers a
little to get an overview. But if you don't agree, then never mind, I can
live with it...
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3bb0e4a5@news.povray.org> , "Rune" <run### [at] mobilixnetdk>
wrote:
> I know, but that's sometimes a difficult task with the massive amount of
Keep in mind the POV-Team members also have to keep up with the messages, so
you are not alone :-)
> messages, so I just thougt it could be a good idea to help the testers a
> little to get an overview. But if you don't agree, then never mind, I can
> live with it...
OK.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 25 Sep 2001 22:02:49 +0200, Rune wrote:
>"Ron Parker" wrote:
>> Want me to send you the list of messages in this
>> newsgroup that I have marked unread?
>
>Yes please (the list of messages, not the messages themselves)
>
>> That's my list of known (or at least reported but not
>> yet investigated) bugs.
>
>I don't think it can be expected of all the beta testers to do something
>similar on their own. If I compile the messages from the list you send me
>into a list of known bugs, would it be possible that someone from the Team
>could update it as new beta versions are released?
The problem with this approach is that my list of known bugs is not complete.
It doesn't contain things that have been fixed but haven't made their way
into a beta yet. It always will be incomplete in this way, so it's not
useful to anyone but me.
Ideally, we would put all of the bugs into our bug tracking system and this
wouldn't be a difficult task, but of late it's been easier to just fix them
as we duplicate and identify them. (For example, 3 of the bugs I fixed last
night were easier to fix than they would have been to put in the tracking
system.)
I think Thorsten's right: the list of known bugs is everything in this group
that hasn't been addressed in the list of changes for a beta.
--
plane{-z,-3normal{crackle scale.2#local a=5;#while(a)warp{repeat x flip x}rotate
z*60#local a=a-1;#end translate-9*x}pigment{rgb 1}}light_source{-9red 1rotate 60
*z}light_source{-9rgb y rotate-z*60}light_source{9-z*18rgb z}text{ttf"arial.ttf"
"RP".01,0translate-<.6,.4,.02>pigment{bozo}}light_source{-z*3rgb-.2}//Ron Parker
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 25 Sep 2001 17:05:55 -0400, Ron Parker wrote:
>
>The problem with this approach is that my list of known bugs is not complete.
Nevertheless, here's my list for what it's worth:
1 - 92:[Micha Riser ] blob problem
3 - 9:[Jan Walzer ] [superellipsoid] epsilon to big ?
4 - 41:[Jan Walzer ] [SOR] a bug ?
5 - 21:[QQ ] 2 Additional (?) blob bug
6 - 88:[Kari Kivisal] 2 Photon bug
8 - 21:[QQ ] [Beta 2] Blob rendering error
9 - 29:[Bob H. ] 2 omnimax, fisheye lenses wrong with certain pretrace
10 - 12:[Anders K. ] Small window title bug
11 - 21:[Mike Hough ] 16-bit PGM pigment and height field problems
12 - 43:[Bonsai ] bug in texture_map
13 - 74:[Michael Andr] 3 [Bug?] Radiosity, recursion > 1
15 - 14:[ingo ] stop during mosaic: crash
16 - 23:[Warp ] sin(X)^sin(X) -> crash!
17 - 91:[Trevor Quayl] uv_mapping & lathe
19 - 13:[Rick Gutlebe] small but annoying documentation bug... also blob
--
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbf 1}hollow interior{media{emission 3-T}}}#end
Z(-x-x.2x)camera{location z*-10rotate x*90normal{bumps.02scale.05}}
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" wrote:
> Keep in mind the POV-Team members also have to keep
> up with the messages, so you are not alone :-)
That's why I thought a list of known bugs would have been useful for the
POV-Team too...
<shrugs>
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
