Request to everyone testing POV-Ray 3.5 beta:

  Please go through the officially unconfirmed bugs and test them again to
see if they still happen.
  It could also be really nice if some bug still happens, a short and clear
way of repeating the bug could be provided. If the bug is questionable
(ie. could be just a design decision), a concise and clear explanation of
what is wrong and how it should work.

  Bugs which are not properly confirmed will just be removed from the list.


  Officially confirmed bugs:
  -------------------------

* Macro bug (job000146)
  (POV can dereference a deallocated pointer if you return a local from a
  macro. Causes POV to crash.)
  Reported in:
"Known Bug" for Rune
http://news.povray.org/3BB4ED11.8EC69CEC@hotmail.com
strings operations crash with both compiles
http://news.povray.org/e3piut8anmf4cli4pnfmstadgc3nleqvb2@4ax.com

* Several blob bugs (job000189)
  (Among other problems, blobs have holes in certain circumstances, such as
  very small or big component radiuses)
  Reported in:
blob problem
http://news.povray.org/3b99052c@news.povray.org
Blob : Toward a solution
http://news.povray.org/3B991C90.D715B7A3@free.fr
Possible bug with blobs
http://news.povray.org/3c407ad3$1@news.povray.org
Additional (?) blob bug
http://news.povray.org/Xns9115B92CF7D8ACQ@204.213.191.226
Blob rendering error
http://news.povray.org/Xns91203DC7F3CCQ@204.213.191.226
Bug with blobs and media
http://news.povray.org/3be5f0b2@news.povray.org
Blob component textures transformed twize
http://news.povray.org/3bf70645@news.povray.org
blob casting incorrect shadows on itself
http://news.povray.org/Xns919C1CAA3E23Egerovandordatanethu@204.213.191.226

* Superellipsoid bug (job000190)
  (Strange dark patches occur on a superellipsoid when the east-west-
  exponent is set very small)
  Reported in:
[superellipsoid] epsilon to big ?
http://news.povray.org/3b992a81@news.povray.org

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

* Color dot operators as macro parameters bug (job000201)
  (Eg. Color.red doesn't work as a macro parameter)
  Reported in:
color dot operators
http://news.povray.org/ofpr1ug9r6q3cak417pmj72bck6ufmgbtg@4ax.com

* Radiosity doesn't take double_illuminate into account (job000207)
  Reported in:
double_illuminate only works with direct lighting
http://news.povray.org/3BF6F1FE.D21B0C6@oreka.com

* Mapping warps+transformation bug (job000212)
  (Object lighting is calculated incorrectly when mapping warps are used
  in normals and the object is rotated)
  Reported in:
Mapping warp and render window bugs
http://news.povray.org/Xns9190F27EBFE9Bcsbhccse@204.213.191.226
Severe Lightbug, probably concerned with Macros... (long post)
http://news.povray.org/3C4ABED3.F038E200@gmx.de

* Photon bug (job000213)
  (A combination of photons, union, ior and lathe causes the intel compile
  to crash.)
  Reported in:
crash with photons, union, ior, lathe
http://news.povray.org/vfra4u0ndv4rf951196881cpt842an4906@4ax.com

* POV-Ray crashes with some very long function definitions
  (POV doesn't check when the max VM code is exceeded.)
  Reported in:
long function with crash
http://news.povray.org/8pe56usuudisacgrocav0l0ovqvetsno83@4ax.com

* Crash with "Reallocing Finite with extension"
  Reported in:
Reallocing Finite with extension (with crash)
http://news.povray.org/8laa5us450irp75g6l2i4e84dm1c4v4i01@4ax.com
crash with some boxes /infinite boxes
http://news.povray.org/3c375d62$1@news.povray.org

* max_trace_level affects radiosity recursion_limit
  (This is a design decision and the possibility of a change is being studied.)
  Reported in:
max_trace_level affects radiosity recursion_limit
http://news.povray.org/3BE40295.6C3D54DE@engineer.com
Re: known bugs 28 Jan 2002
http://news.povray.org/Xns91A7BA6876851CQ@204.213.191.226


  Bugs with no official confirmation:
  ----------------------------------

* Crash with empty scene
  (Not properly confirmed. Most people report no problems.)
  Reported in:
Crash with no objects in scene
http://news.povray.org/3bd985b0@news.povray.org
POV-Crash on empty scenes
http://news.povray.org/3C19B9EA.D2E16FBC@gmx.de

* 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

* Prism transformation problem
  (Conic prism illumination is not correct after certain rotations. Bug
  status unclear.)
  (Note: It has been reported that this bug would not happen in POV-Ray 3.1.
   This needs verification.)
  Reported in:
rare conic prism bug
http://news.povray.org/3C51212E.9090707@irrwerk.de

* Shadow rendering problem
  (Shadows are not rendered correctly in certain scened scaled small. The
  nature of this problem is extremely unclear and requires much more
  confirmation. Also it should be compared to POV-Ray 3.1.)
  Reported in:
Shadow faults
http://news.povray.org/3c53b38e@news.povray.org

* Crash during radiosity pretrace
  (Needs confirmation.)
  Reported in:
crash during radiosity pretrace
http://news.povray.org/3C517D27.54270E7@gmx.de

* Slope pattern problem
  (The slope pattern is not rotated by subsequent rotate commands.
  This issue is being investigated.)
  Reported in:
Non-rotating slope maps in 3.5.beta.11.incl.win32
http://news.povray.org/3c6bcc65$1@news.povray.org

* library_path to network drives problem
  (POV-Ray crashes if there's a network name in the library_path.
   Does this still appear?)
  Reported in:
Re: Beta 10 bugs
http://news.povray.org/Xns9198B5827CCC9CQ@204.213.191.226

* Image_maps using png images are gamma-corrected (when they shouldn't)
  (Confirmed by users.)
  Reported in:
image_map png gamma bug
http://news.povray.org/3c817af3@news.povray.org


  Problems still being worked on:
  ------------------------------

* Camera problems (job000196)
  (Heavy changes to camera behaviour are being developed which should get
  rid of all previous problems and make it more consistent.)
  A related bug report:
panoramic projection bug?
http://news.povray.org/avnfut8fof5ualgf8hnrtpl1knlg8828sp@4ax.com

* Splines
  (Splines are still being developed and constantly changing.)
  A related report:
splines - documentation and reality
http://news.povray.org/m7fq3u41ctia9e6i3tbnlstn6ek739vpke@4ax.com

* TIFF problems
  (Several problems reading different types of TIFF images. The problems
  are related to the TIFF library itself. TIFF support might just be
  removed.)
  Reported in:
tiff problems in reading (including crash, including [doc])
http://news.povray.org/n96b3uk1ft7mvb991s3htjt14ekb7j8fn7@4ax.com

* HF_* macros in std includes problems
  Reported in:
[std include] hf_* macros doubts
http://news.povray.org/1dtd4ug8htn1ns9md3vp9i1mbcq5qf10sb@4ax.com


  Problems in "suspended" status (most probably will not be fixed in 3.5):
  -----------------------------------------------------------------------

* Poly object bug (job000038)
  (Some polys show artifacts)
  Reported in:
Re: trivial question on topic
http://news.povray.org/3BEBEB4C.CA854309@pacbell.net

* Radiosity sampling problems (job000177)
  (radiosity sample counter is reset to the start every time, sampling
  artefacts are produced)
  Reported in:
[bug]: radiosity sampling, with fix method.
http://news.povray.org/3BC5A13E.9C022BD6@reading.ac.uk
  (A possibly related report:
Radiosity samples during pretrace.
http://news.povray.org/3c587c7a@news.povray.org)

* Highlight bug (job000137)
  (Highlights are sometimes visible in the non-lit side of a surface with
  highly perturbed normals)
  Reported in:
Highlight bug
http://news.povray.org/3bb4cf08@news.povray.org

* Julia object problem (job000216)
  (Julia objects sometimes present random artifacts. Whether this is an
  actual bug or just a floating point or other type of precision problem is
  not clear.)
  Reported in:
Julia object bug (Michael McKnight)
http://news.povray.org/3839f08c@news.povray.org

* Smooth triangle problem
  (In smooth meshes and smooth heightfields surface normals are sometimes
  inverted when they shouldn't. The nature of this problem is such that it
  will probably be fixed only in POV4.)
  Reported in:
Heightfield bug (most probably an inverted normals problem)
http://news.povray.org/3c4ca8ff@news.povray.org

* Vector arithmetic using t problems
  (Cannot be changed until 4.0.)
  Reported in:
<1, 0, 0> + 1*t
http://news.povray.org/3c4bb31d$1@news.povray.org
Initialisation of a 4-vector array
http://news.povray.org/3c4fe83b@news.povray.org

* "Camera inside non-hollow object" reported erroneously in some cases
  with light_groups. (job000226)
  Reported in:
Re: hollow in light groups
http://news.povray.org/3c21172d$1@news.povray.org

* Sphere sweep bug (job000200)
  (discontinuous normals on inverse of sphere_sweep)
  Reported in:
bug in sphere_sweep for removing parts of an object
http://news.povray.org/3C1A5D47.EA38F6E5@amc.uva.nl

* Bicubic patch bug (job000202)
  (Bicubic patch triangles disappear in some circumstances.)
  Reported in:
Bicubic patch triangles disappear
http://news.povray.org/3c23b26c@news.povray.org

* Media+fog problem (job000230)
  (Using media and fog has strange effects. Bug status unclear.)
  Reported in:
media & fog bug?
http://news.povray.org/3c1379e0$1@news.povray.org
  Another Media+fog problem report with unclear bug status:
Funky fog vs. media
http://news.povray.org/3c642f94$1@news.povray.org


  Fixed bugs:
  ----------

* Exponentiation operator bug (job000180)
  (An operation of the form sin(x)^sin(x) causes a crash in some cases.)
  Reported in:
sin(X)^sin(X) -> crash!
http://news.povray.org/3baf7992@news.povray.org

* Spline bug (job000181)
  (Changes from render to render. Control points are sometimes missing.)
  Reported in:
Strange spline problem
http://news.povray.org/Xns9136AC2E64F60seed7@povray.org

* Spline bug (job000182)
  (The spline path is all wrong when certain time values are used.)
  Reported in:
Strange spline bug
http://news.povray.org/3bb41dc8@news.povray.org

* Light groups bug (job000197)
  (In some cases lights in light groups don't cast shadows)
  Reported in:
Light_sources in light_groups don't cast shadows
http://news.povray.org/3bfd4d63@news.povray.org

* Triangle texture bug (job000199)
  (Problems with triangle texture interpolation.)
  Reported in:
Re: triangle texture interpolation
http://news.povray.org/3C0A8288.DDA0905B@free.fr

* transform syntax bug (job000214)
  (transform sometimes requires {} and sometimes doesn't)
  Reported in:
transform syntax
http://news.povray.org/3C09EE1B.A38DC91A@gmx.de

* WinPOV problem
  (If POV-Ray starts minimized and shows 'tip of the day', it causes problems
  in trying to restore the main window.)
  Reported in:
Minor Windows annoyance
http://news.povray.org/3c2bec89@news.povray.org

* Memory leak in interrupted renders
  Reported in:
Partial render memory leak
http://news.povray.org/3C47228A.D7680441@twoalpha.net

* Camera is off by half-pixel
http://news.povray.org/3bccc696@news.povray.org

* function_id highlighted in WinPOV editor
http://news.povray.org/jfji3ug1faevn1jk3mlko64sb71ptmmn97%404ax.com

* Crash when interrupting while #debug is printing.
http://news.povray.org/332m2uspk9nfqfq6g7oc8qtmkcu5higjs7@4ax.com

* #while crash..
http://news.povray.org/3c38646f@news.povray.org

* Crash with infinite loop
http://news.povray.org/3c2cb9b7@news.povray.org

* Bicubic patch UV-vector bug
http://news.povray.org/3C5F1E36.C7C513A3@amc.uva.nl

* WinPOV render window problem (job000217)
  (Maximizing the render window during a trace will occasionally leave a
  partial line of the checkerboard background visible.)
  Reported in:
Mapping warp and render window bugs
http://news.povray.org/Xns9190F27EBFE9Bcsbhccse@204.213.191.226

* WinPOV: -GA causes winpov to clear the render window between frames
  (job000224)
  Reported in:
-GA causes winpov to clear between frames
http://news.povray.org/3c61aed7@news.povray.org

* Declared camera bug
  (A declared camera with normal statements causes POV-Ray to crash.)
  Reported in:
bug : declared camera with normal statement crashes
http://news.povray.org/3C41A226.7030703@skynet.be

* WinPOV problem (job000221)
  (Maximizing the POV-Ray window by double-clicking on the title is reported
  to cause an error prompt about text selection.)
  Reported in:
http://news.povray.org/3c3b7a3f@news.povray.org

* WinPOV problem (job000223)
  (WinPOV crashes in some situations when opening the ini dialog.)
  Reported in:
[win] ini dlg crash - stack overflow
http://news.povray.org/3c57985c$1@news.povray.org

* Array assignment crash (job000203)
  (It should overwrite the old array with the newly created, correct
  array, but crashes)
  Reported in:
http://news.povray.org/3bcc54ab$1@news.povray.org

* Macro parsing crash
  Reported in:
#macro crush
http://news.povray.org/3c2c78cf$1@news.povray.org

* Bicubic Patch bug
  (Problem with comma parsing)
  Reported in:
http://news.povray.org/3c65d8af@news.povray.org

* WinPOV window title problem (job000218)
  (Title switches back to "POV-Ray for Windows" after minimize and
  restore even though a file is open.)
  Reported in:
Small window title bug
http://news.povray.org/3ba92966$1@news.povray.org

* 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

* Alpha channel bug (job000210)
  (assumed_gamma affects the transparency of shadowed areas)
  Reported in:
Strange alpha channel bug
http://news.povray.org/3c1168c5$1@news.povray.org

* Photons bug (job000195)
  (In some cases photons cause abnormally colored caustics and circular
  black spots)
  Reported in:
another strange photon behavior
http://news.povray.org/MPG.16510f3e44067d3f9896ae@news.povray.org

* 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

* POV for Linux crashes at photon sorting stage (job000222)
  (Confirmed only in the Linux version.)
  Reported in:
Beta10-Linux Segmentation Fault
http://news.povray.org/3C4D93F1.2000005@gmx.de
Fatal error.
http://news.povray.org/3bb5d946$1@news.povray.org

* Radiosity bug (job000215)
  (Rendering slows down when repeatedly started and stopped during radiosity
  calculations.)
  Reported in:
Slow render time after several runs
http://news.povray.org/3bd40c6d$1@news.povray.org
  (A possibly related report:
radiosity problem
http://news.povray.org/3c49968f@news.povray.org)

* Photons bug (job000204)
  (Image brightness problems in some cases.)
  Reported in:
Photon Problems
http://news.povray.org/3bc4d0a9$1@news.povray.org

* Function namespace problem
  (Declared function names can't be used as macro parameter names. Might
  not be possible to be fixed with the current parser. This is being
  investigated.)
  Reported in:
function declaration and namespace
http://news.povray.org/l2ji3uc2k9su99o2gct3n2thgqoq7f4pd5@4ax.com

* Functions in arrays problem
  (Using the function at the index 0 of an array causes an error/crash.)
  Reported in:
Still a first function initialisation error?
http://news.povray.org/3C612786.9000004@reading.ac.uk

* dispersion_samples affects photon brightness (job000193)
  (higher dispersion_samples also gives brighter refractive photons)
  Reported in:
Bug: dispersion_samples affects photon brightness
http://news.povray.org/MPG.1631c5fca936293298969e@news.povray.org

* "povray --help" causes an infinite loop in the unix version
  (Confirmed by users.)
  Reported in:
Linux: --help causes loop
http://news.povray.org/3c84e479@news.povray.org

* Function redefinition bug
  (Parser fails to trap some attempts to illegally redefined functions)
  Reported in:
can't redefine identifier
http://news.povray.org/tis83ugh1kcc22h5o6is9qpkv61pjgunc0@4ax.com

* Shadow problem with merge and no_image (job000198)
  (Setting no_image to an object in a merge causes that object to stop
  casting shadows)
  Reported in:
no_image, merge and shadows
http://news.povray.org/vqfd0ucm5276q9j8sdh34afjliapc1kj0n@4ax.com

* image_map transparency bug (job000211)
  (Objects with transparent image_maps have "non-transparent" shadows)
  Reported in:
Re: problem with transparent image_maps
http://news.povray.org/eGSwuBAritK8EwLH@econym.demon.co.uk

* Problem with function parsing
  (Confirmed by users)
  Reported in:
crash with "recursion" in functions
http://news.povray.org/uoj68uk5m391emvphovqfbg5vl0en7h2q6@4ax.com

* Functions can't be #undef'd
  (Confirmed by users)
  Reported in:
#undef function parsing error
http://news.povray.org/3ca0f412@news.povray.org

* Spline array problems
  (Trying to initialize or copy an array with spline identifiers causes a
   "Cannot copy identifier" message.)
  Reported in:
cannot copy array with spline
http://news.povray.org/tp5p8uoemqon1um6i4j75nc09ho61364su@4ax.com

* Powers of 0 in functions do not work correctly
  (Confirmed by users.)
  Reported in:
Buggy power operator in functions
http://news.povray.org/3C847750.BE9AD3A5@hotmail.com

* Math operator bug (job000179)
  (Some operators causing a crash in some cases. Confirmed only in
  Windows 2000; no confirmation in other systems.)
  Reported in:
crash inside two #while
http://news.povray.org/3c3f1f29$1@news.povray.org

* Crash with parametric object
  (Confirmed by users)
  Reported in:
crash with parametric object
http://news.povray.org/cu31auko3a0g3gnqgjb5t8uog4tj8id65q@4ax.com


-- 
#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

"Warp" wrote:
> * Crash with empty scene
>   (Not properly confirmed.
>   Most people report no problems.)

In an ini file, Bounding_Threshold must be set to 0 for the bug to show up.
When doing this, the bug happens for me consistently. When setting
Bounding_Threshold to some higher value, the bug doesn't happen. For a scene
file I use a completely empty text file.

I'm using beta 15 on Windows 98, Athlon XP 1700+.

Can anyone confirm? Can anyone not confirm?

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

> * Photons bug (job000204)
>   (Image brightness problems in some cases.)
>   Reported in:
> Photon Problems
> http://news.povray.org/3bc4d0a9$1@news.povray.org

This was in the fixed bugs list, but it's not fixed in beta 15. (The sample
scene still shows the problem.)

I did, however, find that if I increase the space between the two nested
objects to 1/10 of a unit, the problem goes away. That's acceptable for my
purposes (thankfully), but the problem may still be worth looking into.

- Slime
[ http://www.slimeland.com/ ]
[ http://www.slimeland.com/images/ ]

Post a reply to this message

In article <3ca86fad@news.povray.org> , "Rune" <run### [at] mobilixnetdk>
wrote:

> In an ini file, Bounding_Threshold must be set to 0 for the bug to show up.

Ah, so you want bounding of no objects in the scene to bound "nothing"? :-)

With this information I can confirm it:  As bounding of nothing is "unusual"
the code assumed the threshold is positive.  This will be fixed in the next
beta.  The Bounding_Threshold will then be adjusted to its minimum legal value
of one (together with a warning message) automatically.

    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

"Thorsten Froehlich" wrote:
> With this information I can confirm it:  As bounding
> of nothing is "unusual" the code assumed the threshold
> is positive.  This will be fixed in the next beta.
> The Bounding_Threshold will then be adjusted to its
> minimum legal value of one (together with a warning
> message) automatically.

This means that if there's less than 1 object in the scene, the bounding
will be turned off, right? I also seem to remember that in animations, the
first frame of the animation determines if bounding is turned on or not for
all the frames, even if there are more objects in the next frames.

So, if Bounding_Threshold can't be set to 0, and one has an animation where
there's no objects in the first frame, then bounding will be turned off for
all the frames, thus causing a major slow-down.

If the above is not correct, I apologize, but if it is, then I think a
better solution should be found, like evaluating the Bounding_Threshold in
every frame instead of only in the first frame.

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

In article <3ca8831b@news.povray.org> , "Rune" <run### [at] mobilixnetdk>
wrote:

> So, if Bounding_Threshold can't be set to 0, and one has an animation where
> there's no objects in the first frame, then bounding will be turned off for
> all the frames, thus causing a major slow-down.
>
> If the above is not correct

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

    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

"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