 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Blob problem (job000189)
and Blob : Toward a solution
(blob surface develops holes when "radius" is very small)
http://news.povray.org/3b99052c@news.povray.org
http://news.povray.org/3B991C90.D715B7A3@free.fr
Superellipsoid epsilon to big ? (job000190)
(strange dark patches occur on a superellipsoid when the east-west-
exponent is set very small)
http://news.povray.org/3b992a81@news.povray.org
Additional (?) blob bug (job000189)
(blob component disappears when radius is 317 or greater)
http://news.povray.org/Xns9115B92CF7D8ACQ@204.213.191.226
(also reported as: Blob rendering error (job000136))
http://news.povray.org/Xns91203DC7F3CCQ@204.213.191.226
Small window title bug ()
(Title switches back to "POV-Ray for Windows" after minimize or
restore.)
http://news.povray.org/3ba92966$1@news.povray.org
Spline bug (job000182)
(The spline path is all wrong when certain time values are used.)
http://news.povray.org/3bb41dc8@news.povray.org
Strange spline problem (job000181)
(Changes from render to render. Control points are sometimes missing.)
http://news.povray.org/Xns9136AC2E64F60seed7@povray.org
Highlight bug (job000137)
(highlights are sometimes visible where they should be in shadow)
http://news.povray.org/3bb4cf08@news.povray.org
Macro bug (job000146)
(POV can dereference a deallocated pointer if you return a local from a
macro.)
http://news.povray.org/3BB4ED11.8EC69CEC@hotmail.com
(also reported as: strings operations crash with both compiles
http://news.povray.org/e3piut8anmf4cli4pnfmstadgc3nleqvb2@4ax.com)
Radiosity sampling, with fix method (job000177)
(radiosity sample counter is reset to the start every time, sampling
artefacts are produced)
http://news.povray.org/3BC5A13E.9C022BD6@reading.ac.uk
Slow rendering when using +ua and antialiasing method 1 (job000191)
(No details available)
http://news.povray.org/3bbf6347@news.povray.org
[bug] orthographic camera bug?
(objects sometimes disappear when the orthographic camera is used)
http://news.povray.org/3bdca5eb@news.povray.org
Bug: dispersion_samples affects photon brightness (job000193)
http://news.povray.org/MPG.1631c5fca936293298969e@news.povray.org
Bug with blobs and media (job000189)
(possibly related to blob surface develops holes when "radius" is very
small)
http://news.povray.org/3be5f0b2@news.povray.org
Another strange photon behavior (job000195)
(a: bright colored caustics. b: holes/circular black spots)
http://news.povray.org/MPG.16510f3e44067d3f9896ae@news.povray.org
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
Black outline in smooth meshes
(The outline of smooth meshes exhibit black dots or areas (which go away
with double_illuminate))
http://news.povray.org/3bf6794e$1@news.povray.org
User_Abort_Command
(User_Abort_Command does not seem to work at all)
http://news.povray.org/Xns913D9F7268736seed7@povray.org
Re: trivial question on topic (job000038)
(Poly Object Bug: heart has a dark line of artifacts)
http://news.povray.org/3BEBEB4C.CA854309@pacbell.net
Camera is off by half a pixel
http://news.povray.org/3bccc696@news.povray.org
Light_sources in light_groups don't cast shadows (job000197)
(rendering without light buffers (-UL) puts the shadows back)
http://news.povray.org/3bfd4d63@news.povray.org
Save during render
(is very slow)
http://news.povray.org/Pine.LNX.4.33.0111271256060.2190-100000@burpc3.en
gin.umich.edu
double_illuminate only works with direct lighting
http://news.povray.org/3BF6F1FE.D21B0C6@oreka.com
no_image, merge and shadows (job000198)
(setting no_image to an object in a merge causes that object to stop
casting shadows)
http://news.povray.org/vqfd0ucm5276q9j8sdh34afjliapc1kj0n@4ax.com
Isosurfaces *much* slower in beta 7?
(isosurfaces with "evaluate" are now very slow)
http://news.povray.org/3bdf24b3$1@news.povray.org
rand.inc VRand_In_Sphere flaw
(VRand_In_Sphere doesn't give uniform distribution)
http://news.povray.org/3bc64790$1@news.povray.org
Re: triangle texture interpolation (job000199)
(the second texture is on the first point and the third texture is used
on the second and third points)
http://news.povray.org/3C0A8288.DDA0905B@free.fr
Blob component textures transformed twize (job000189)
http://news.povray.org/3bf70645@news.povray.org
Crash with no objects in scene
http://news.povray.org/3bd985b0@news.povray.org
(also reported as http://news.povray.org/3C19B9EA.D2E16FBC@gmx.de
bug in sphere_sweep for removing parts of an object
(discontinuous normals on inverse of sphere_sweep)
http://news.povray.org/3C1A5D47.EA38F6E5@amc.uva.nl
color dot operators (job000201)
((Color.red) doesn't work as a macro parameter)
http://news.povray.org/ofpr1ug9r6q3cak417pmj72bck6ufmgbtg@4ax.com
Render Window Bug
(Render window pops up when application minimised, after which the
application doesn't open when clicked on the task bar.)
http://news.povray.org/3bde157e@news.povray.org
Povray main window disappears during rendering
(Possibly the same as the above)
http://news.povray.org/3c1350f4@news.povray.org
Bicubic patch triangles disappear (job000202)
(When the triangles are fairly small)
http://news.povray.org/3c23b26c@news.povray.org
Strange alpha channel bug
http://news.povray.org/3c1168c5$1@news.povray.org
installer behaves strangely
(one would expect povray to install after pressing the "next" button and
not the "button")
http://news.povray.org/Xns916AE9B08012frankverlaathotmailc@204.213.191.2
26
Array assignment crash
http://news.povray.org/3bcc54ab$1@news.povray.org
Keep Single Instance (always does, no matter setting)
(Fixed in some environments)
http://news.povray.org/3c0b0881$1@news.povray.org
problem with transparent image_maps
http://news.povray.org/3c24d1b3@news.povray.org (cancelled)
http://news.povray.org/eGSwuBAritK8EwLH@econym.demon.co.uk
Function (optimization?) bug
('funciton{-y/1/2}' should be same as 'function{-y/1/(2)}')
http://news.povray.org/3c27fd29$1@news.povray.org
Photon Problems
(Rendering the file makes the image strangely bright)
http://news.povray.org/3bc4d0a9$1@news.povray.org
crash during debugging of parsing
http://news.povray.org/332m2uspk9nfqfq6g7oc8qtmkcu5higjs7@4ax.com
Re: Known Bugs 24 Dec 2001
(garbage text in Mac message window)
http://news.povray.org/3C2A7123.E923B0B4@spiritone.com
another crash with max_intersections
http://news.povray.org/j8fo2u8mbo97gi3as0udmab7t9ttap2iom@4ax.com
#macro crush
http://news.povray.org/3c2c78cf$1@news.povray.org
crash with loop
http://news.povray.org/3c2cb9b7@news.povray.org
FIXED IN NEXT BETA
Delayed syntax checking (job000192)
(declare without the "#" can cause a much later line to fail to parse
Parser will ignore the first token following old-style declares without
a #.)
http://news.povray.org/AM3LOAABMO27EwFh@econym.demon.co.uk
sin(X)^sin(X) -> crash! (job000179 and job000180)
http://news.povray.org/3baf7992@news.povray.org
Jpeg and memory problem during animations (job000194)
(It seems that some memory is not properly released between frames when
a jpeg file is used)
http://news.povray.org/3be2ef0d@news.povray.org
Isosurface : 2 bugs
(int() causes crash)
http://news.povray.org/3c082dbe@news.povray.org
IsoCacti.pov
(displays 754 evaluate warnings, most with incorrect values)
http://news.povray.org/3c08c36c$1@news.povray.org
Error in VRand_Object
http://news.povray.org/3bc423e5@news.povray.org
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
From: Slime
Subject: Re: Known Bugs - 31 Dec 2001 (vrand_in_sphere was fixed)
Date: 31 Dec 2001 00:33:48
Message: <3c2ff8bc@news.povray.org>
|
|
|
| |
| |
|
|
> rand.inc VRand_In_Sphere flaw
> (VRand_In_Sphere doesn't give uniform distribution)
> http://news.povray.org/3bc64790$1@news.povray.org
This was fixed for beta 9.
> Photon Problems
> (Rendering the file makes the image strangely bright)
> http://news.povray.org/3bc4d0a9$1@news.povray.org
Yaaaay!
- Slime
[ http://www.slimeland.com/ ]
[ http://www.slimeland.com/images/ ]
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Here is the update with job numbers and other notes:
> User_Abort_Command
> (User_Abort_Command does not seem to work at all)
> http://news.povray.org/Xns913D9F7268736seed7@povray.org
Behavior of GUI platforms will change in next beta.
> Save during render
> (is very slow)
> http://news.povray.org/Pine.LNX.4.33.0111271256060.2190-100000@burpc3.en
> gin.umich.edu
Not a bug. User configuration error (slow system and network).
Later in the thread a feature request for background saving. Note that
background saving is not possible to implement as it would have to guard
against saving of files that are being rendered as well as delay rendering
when files needed for the render are still being written to disk. However,
it is not possible to determine all files which will be used by a scene
prior to running it (i.e. files generated by the script and opened by the
user or files whose name is determined via string functions). Thus
background saving would have to disable the "Start Rendering" functions and
making it not transparent to the user but only _very_ confusing why
rendering isn't possible.
> double_illuminate only works with direct lighting
> http://news.povray.org/3BF6F1FE.D21B0C6@oreka.com
Has not been confirmed!!!
> Isosurfaces *much* slower in beta 7?
> (isosurfaces with "evaluate" are now very slow)
> http://news.povray.org/3bdf24b3$1@news.povray.org
Already fixed in beta 9.
> Crash with no objects in scene
> http://news.povray.org/3bd985b0@news.povray.org
> (also reported as http://news.povray.org/3C19B9EA.D2E16FBC@gmx.de
Duplicate of function problem in beta 8. Already fixed in beta 9.
> bug in sphere_sweep for removing parts of an object
> (discontinuous normals on inverse of sphere_sweep)
> http://news.povray.org/3C1A5D47.EA38F6E5@amc.uva.nl
Logged as job000200.
> Array assignment crash
> http://news.povray.org/3bcc54ab$1@news.povray.org
Logged as job000203.
> problem with transparent image_maps
> http://news.povray.org/3c24d1b3@news.povray.org (cancelled)
> http://news.povray.org/eGSwuBAritK8EwLH@econym.demon.co.uk
I admit it is a naive question, but didn't the behavior of filter and
transmit change in 3.5 and might this be the cause? (I didn't render the
scene to see what it looks like.)
> Function (optimization?) bug
> ('funciton{-y/1/2}' should be same as 'function{-y/1/(2)}')
> http://news.povray.org/3c27fd29$1@news.povray.org
Fixed in next beta.
> Photon Problems
> (Rendering the file makes the image strangely bright)
> http://news.povray.org/3bc4d0a9$1@news.povray.org
Logged as job000204.
> crash during debugging of parsing
> http://news.povray.org/332m2uspk9nfqfq6g7oc8qtmkcu5higjs7@4ax.com
> crash with loop
> http://news.povray.org/3c2cb9b7@news.povray.org
Both logged as job000205.
> Re: Known Bugs 24 Dec 2001
> (garbage text in Mac message window)
> http://news.povray.org/3C2A7123.E923B0B4@spiritone.com
Fixed in next beta.
> another crash with max_intersections
> http://news.povray.org/j8fo2u8mbo97gi3as0udmab7t9ttap2iom@4ax.com
Will be fixed in next beta. Note that setting max_intersections to 0 isn't
allowed.
> #macro crash
> http://news.povray.org/3c2c78cf$1@news.povray.org
Logged as job000206.
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trf de
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Please also note my recent additions in the Dec 24th list thread.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
>
> Not a bug. User configuration error (slow system and network).
>
> Later in the thread a feature request for background saving. Note that
> background saving is not possible to implement as it would have to guard
> against saving of files that are being rendered as well as delay rendering
> when files needed for the render are still being written to disk. However,
> it is not possible to determine all files which will be used by a scene
> prior to running it (i.e. files generated by the script and opened by the
> user or files whose name is determined via string functions). Thus
> background saving would have to disable the "Start Rendering" functions and
> making it not transparent to the user but only _very_ confusing why
> rendering isn't possible.
>
I understand that, but in most cases it would be perfectly sufficient to
enable background saving only when a render is running.
BTW, i presume the situation of saving while a scene is being parsed (that
uses this file) is a problematic case anyway.
Christoph
--
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other
things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" wrote:
> > Crash with no objects in scene
> > http://news.povray.org/3bd985b0@news.povray.org
> > (also reported as http://news.povray.org/3C19B9EA.D2E16FBC@gmx.de
>
> Duplicate of function problem in beta 8. Already fixed in beta 9.
It still crashes on my system using beta 9.
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated Nov 5)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3C307740.72F654E0@gmx.de> , Christoph Hormann
<chr### [at] gmxde> wrote:
> I understand that, but in most cases it would be perfectly sufficient to
> enable background saving only when a render is running.
>
> BTW, i presume the situation of saving while a scene is being parsed (that
> uses this file) is a problematic case anyway.
When saving goes on in the background the behavior gets unpredictable even
for the developers of the software. I.e. what happens when the user starts
rendering (because the current scene has finished) of the scene file while
saving is still in progress? This would again require the "Start Rendering"
command to be disabled.
In short it would be a usability nightmare and adds nothing but confusion.
POV-Ray GUIs are a kind of IDE, not word processors* :-)
Thorsten
* While some may not see the difference, see the GUI as *independent* from
the renderer. There is no such independent element in word processors.
____________________________________________________
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3c3051bf$1@news.povray.org> , "Thorsten Froehlich"
<tho### [at] trfde> wrote:
> Please also note my recent additions in the Dec 24th list thread.
Regarding:
job000208
with orthographic camera objects disappear when "angle" keyword is used
Analysis:
It turns out this never was a bug. 'angle' works exactly as advertised in
the manual. The problem is the user specified the camera type after the
angle, which assumed it was applied to a perspective camera and consequently
changed the direction vector length, which makes it look like the object
disappears.
Solution in next beta:
Now, with version 3.5 specified the camera type has to be the first thing in
a camera statement. The default type (which obviously does not need to be
specified) is still perspective, of course.
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:
> Solution in next beta:
> Now, with version 3.5 specified the camera type has to
> be the first thing in a camera statement. The default
> type (which obviously does not need to be specified)
> is still perspective, of course.
WHAT???
Specifying the orthographic keyword as the last thing in the camera
definition has always been a *very* handy feature which meant you didn't
have to fiddle with the width and height vectors. It's even stated clearly
in the documentation:
"If you add the orthographic keyword after all other parameters of a
perspective camera you'll get an orthographic view with the same image area,
i.e. the size of the image is the same. In this case you needn't specify the
lengths of the right and up vector because they'll be calculated
automatically."
The discussed feature change (not bug fix) would be a *major* brake of
backwards compatibility and would make it much more annoying to work with
the orthographic camera in general. Please don't cripple the software like
that! :(
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated Nov 5)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wasn't it Thorsten Froehlich who wrote:
>> bug in sphere_sweep for removing parts of an object
>> (discontinuous normals on inverse of sphere_sweep)
>> http://news.povray.org/3C1A5D47.EA38F6E5@amc.uva.nl
>
>Logged as job000200.
Oops. You told me this already, but I mistakenly logged the other bug
that was reported in that article as job000200.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
