"Thorsten Froehlich" wrote:
> Yes and no :-)  It was a bug in 3.1 that has been
> fixed in 3.5 a long time ago.

Ah, good! I thought it was a "feature".

Rune
--
3D images and anims, include files, tutorials and more:
Rune's World:  http://rsj.mobilixnet.dk (updated Mar 19)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Ring:  http://webring.povray.co.uk

Post a reply to this message

I hate to say it but,

>   Fixed bugs:
>   ----------
>
> * WinPOV problem (job000219)
>   (Render window pops up when application minimised, after which the
>   application doesn't open when clicked on the task bar. Might be a
Windows
>   problem instead of a WinPOV problem.)
>   Reported in:
> Render Window Bug
> http://news.povray.org/3bde157e@news.povray.org
>   This report might be the same problem:
> Povray main window disappears during rendering
> http://news.povray.org/3c1350f4@news.povray.org

is still there.

I just tested it by using a scene with many photons to delay the display of
the render window until after I could minimize the editor.

Win XP Pro - Athlon XP 1500+

N Shomber

Post a reply to this message

On 1 Apr 2002 08:30:59 -0500, Warp <war### [at] tagpovrayorg> wrote:
>  Officially confirmed bugs:
>  -------------------------
> * Macro bug (job000146)

still exist

> * Several blob bugs (job000189)
> blob problem

still exist

> Blob : Toward a solution
> http://news.povray.org/3B991C90.D715B7A3@free.fr

still exist

> Possible bug with blobs
> http://news.povray.org/3c407ad3$1@news.povray.org

still exist

> Additional (?) blob bug
> http://news.povray.org/Xns9115B92CF7D8ACQ@204.213.191.226

still exist

> Blob rendering error
> http://news.povray.org/Xns91203DC7F3CCQ@204.213.191.226

still exist

> Bug with blobs and media
> http://news.povray.org/3be5f0b2@news.povray.org

still exist

> Blob component textures transformed twize
> http://news.povray.org/3bf70645@news.povray.org

still exist

> blob casting incorrect shadows on itself
> http://news.povray.org/Xns919C1CAA3E23Egerovandordatanethu@204.213.191.226

still exist

> * Superellipsoid bug (job000190)

still exist

> * Slowdown using +a +am1 +ua (job000191)
>  (Using +ua and antialiasing with method 1 causes abnormal slowdown.)

can't recreate
any reference to original script ?

>* Color dot operators as macro parameters bug (job000201)

still exist

> * Radiosity doesn't take double_illuminate into account (job000207)

still exist

> * Mapping warps+transformation bug (job000212)

still exist

> * Photon bug (job000213)

still exist

> * POV-Ray crashes with some very long function definitions

still exist

>* Crash with "Reallocing Finite with extension"

still exist

>* max_trace_level affects radiosity recursion_limit
>  (This is a design decision and the possibility of a change is being studied.)

still studied probably

>  Bugs with no official confirmation:
>  ----------------------------------
>* Crash with empty scene

verified by Rune, fixed by Thorsten now probably

>* Media problem
>  (A visible whitish line appears at the edge of a transparent container
>  box for media. Needs confirmation.)
>  Reported in:
> Media visible container line in front of object
> http://news.povray.org/3bf45a3d@news.povray.org

I can confirm appearance of bright line. I have changed camera location in
example to location <1+clock, 1.7, -5> and started animation.
I have rendered with +FN with standard settings 800x600, AA 0.3.

> * Prism transformation problem
>   (Conic prism illumination is not correct after certain rotations. Bug
>   status unclear.)

Note I have repeated this behaviour with matrix also (coded rotation)
http://news.povray.org/d1oh6u821648rvs7frgmt4cl7u41s6cmmo%404ax.com

>   (Note: It has been reported that this bug would not happen in POV-Ray 3.1.
>     This needs verification.)

What about recompilation of 3.1 with the same compiler and settings as current
betas to verify compiler issues ?

>   Reported in:
> rare conic prism bug
> http://news.povray.org/3C51212E.9090707@irrwerk.de

still appear, hard to say what it is

>* Shadow rendering problem

At first I think originall report needs some changes. First instead multiplying
coordinates of camera probably scale sc should be applied at end. Second
light_source should be also scaled with sc to recreate the same exact world.
Anyway I think it is EPSILON problem.

> * Crash during radiosity pretrace
>  (Needs confirmation.)

since example crashed after 7 hours on Athlon 1 GHz, 512 Mb RAM
I'm probably not the best person to check this with poor PII 233 MHz, 128 MB

>* Slope pattern problem
>  This issue is being investigated.

So nothing to confirm probably (but still exist)

> * library_path to network drives problem

Can't confirm becouse no such enviroment possibilites at this moment

> * Image_maps using png images are gamma-corrected (when they shouldn't)
>  (Confirmed by users.)

Can't confirm becouse lack in knowledge.

>  Fixed bugs:
>  ----------
> * CPU time used printing problem
>   (CPU time used in NT-derived OS's not reported in stream when render
>   completes normally. Confirmed by users.)
>   Reported in:
> [win] "cpu time used" not works properly
> http://news.povray.org/llj84uk2findr74u9jpge6dlteqf19c70o@4ax.com

this is not fixed in beta 15
when +GAout.txt is used then cpu time not appear in stream

ABX

Post a reply to this message

Skiba <abx### [at] babilonorg>  wrote:

> On 1 Apr 2002 08:30:59 -0500, Warp <war### [at] tagpovrayorg> wrote:
>>  Officially confirmed bugs:

In

Message-ID: <3ca86112@news.povray.org>
From: Warp <war### [at] tagpovrayorg>
Subject: Known bugs 1 Apr 2002 (beta15) and request
Newsgroups: povray.beta-test

Warp asked to "Please go through the officially unconfirmed bugs", not through
all bugs...                                     ^^


    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, 02 Apr 2002 14:43:07 +0200, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> Warp asked to "Please go through the officially unconfirmed bugs", not through
> all bugs...                                     ^^

Yes, I noticed this. I walked through all becouse of many resons:
- new beta
- many instances of povray started so best free short time to fight with bugs
- before confirmation of unconfirmed bugs I wanted to refresh current not
working but confirmed list to verify later if there could be something related
in unconfirmed list
- walking through fixed list sometimes shows that something is not fixed
- it not hurt anybody probably
- errare humanum est

ABX

Post a reply to this message

Skiba <abx### [at] babilonorg>  wrote:

>>* Media problem
>>  (A visible whitish line appears at the edge of a transparent container
>>  box for media. Needs confirmation.)
>>  Reported in:
>> Media visible container line in front of object
>> http://news.povray.org/3bf45a3d@news.povray.org
>
> I can confirm appearance of bright line. I have changed camera location in
> example to location <1+clock, 1.7, -5> and started animation.
> I have rendered with +FN with standard settings 800x600, AA 0.3.

I tried it and at least don't see anything unexpected.  Could you post an
image, please?

>> * Prism transformation problem
>>   (Conic prism illumination is not correct after certain rotations. Bug
>>   status unclear.)
>
> Note I have repeated this behaviour with matrix also (coded rotation)
> http://news.povray.org/d1oh6u821648rvs7frgmt4cl7u41s6cmmo%404ax.com
>
>>   (Note: It has been reported that this bug would not happen in POV-Ray 3.1.
>>     This needs verification.)
>
> What about recompilation of 3.1 with the same compiler and settings as current
> betas to verify compiler issues ?

So you have tried it in 3.1 and it doesn't appear?  If it doesn't happen in
3.1, could you post an image of the result in 3.5, please?

>>* Shadow rendering problem
>
> At first I think originall report needs some changes. First instead
> multiplying coordinates of camera probably scale sc should be applied at end.
> Second light_source should be also scaled with sc to recreate the same exact
> world. Anyway I think it is EPSILON problem.

So you are suggesting it is only an odd camera and light position together
with an overall very "small" scene?  Does it go away when scaling everything
by 10 or 100?

>> * Crash during radiosity pretrace
>>  (Needs confirmation.)
>
> since example crashed after 7 hours on Athlon 1 GHz, 512 Mb RAM
> I'm probably not the best person to check this with poor PII 233 MHz, 128 MB

Which means it can be close to anything.  Maybe it was just an overheated
processor :-)

    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

>> * Slowdown using +a +am1 +ua (job000191)
>>  (Using +ua and antialiasing with method 1 causes abnormal slowdown.)

> can't recreate
> any reference to original script ?

  It seems that it happens (only?) with media. Make a clear sphere with
some media inside and render with those settings.
  I'll add a note.

-- 
#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 Tue, 02 Apr 2002 15:32:03 +0200, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> > >* Shadow rendering problem
> >
> > At first I think originall report needs some changes. First instead
> > multiplying coordinates of camera probably scale sc should be applied at end.
> > Second light_source should be also scaled with sc to recreate the same exact
> > world. Anyway I think it is EPSILON problem.
>
> So you are suggesting it is only an odd camera and light position together
> with an overall very "small" scene?

I suggest that after intersection test for 'screen ray' interesection test for
'shadow ray' returns point so close to original intersection point that distance
between them is lower than some epsilon and therefore is considered as the same
surface and not produce shadow.

> Does it go away when scaling everything
> by 10 or 100?

Yes I tested, It appear only for small values, not for large.
Try below animation with +KFF20

#declare sc=10^div(frame_number-9,2);

#if(mod(frame_number-1,2)=0)
  merge {
#else
  union {
#end
box{<-.5,0.8,-.5>,<.5,1.2,.5> pigment{rgb 1} scale sc }
box{<-.5,0,-.5>,<.5,.4,.5> pigment{rgb 1} scale sc }
box{<-.5,0,-20>,<20,-.2,20> pigment{rgb 1} scale sc }
}

background{rgb<1,0,0>}

light_source{<-200,150,100> rgb 1 scale sc}

camera{
  location<2,3,-4>
  look_at<-200,-400,1000>
  scale sc
}

ABX

Post a reply to this message

On Tue, 02 Apr 2002 15:32:03 +0200, "Thorsten Froehlich" <tho### [at] trfde>
wrote:
> > >* Media problem
> I tried it and at least don't see anything unexpected.  Could you post an
> image, please?
> > > * Prism transformation problem
> So you have tried it in 3.1 and it doesn't appear?  If it doesn't happen in
> 3.1, could you post an image of the result in 3.5, please?

all above posted to povray.beta-test.binaries

ABX

Post a reply to this message

> * Image_maps using png images are gamma-corrected (when they shouldn't)

Note that everything works fine when assumed_gamma (of any value) is
specified in the scene. The problem is only when no assumed_gamma is
specified. I don't think the solution is to not gamma-correct them at all.

Anders

Post a reply to this message