What about the "sphere_sweep and radiosity" bug? I hope I don't look like a
monomaniac, but IIRC C. Hormann could replicate that as well... needs this
more confirmation?

--
Jonathan

"Rune" <run### [at] mobilixnetdk> ha scritto nel messaggio
news:3bb8e6a2@news.povray.org...
> Here are the known and confirmed bugs as per today. Corrections to the
list
> are still very welcome.
>
> Blob problem
> http://news.povray.org/3b99052c@news.povray.org
>
> Blob : Toward a solution
> http://news.povray.org/3B991C90.D715B7A3@free.fr
>
> Superellipsoid epsilon to big ?
> http://news.povray.org/3b992a81@news.povray.org
>
> Additional (?) blob bug
> http://news.povray.org/Xns9115B92CF7D8ACQ@204.213.191.226
>
> hf_gray_16 + png creates wrong output image
> http://news.povray.org/3BA3BAE6.4671C0BB@free.fr
>
> Blob rendering error
> 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
>
> 16-bit PGM pigment and height field problems
> http://news.povray.org/3ba99adb@news.povray.org
>
> Blend map crash
> http://news.povray.org/3ba9f8e9$1@news.povray.org
>
> Radiosity with recursion > 1
> (With recursion_limit > 1 clear axis aligned bands appear on the
surfaces.)
> http://news.povray.org/3BAB71AF.B0F503CA@reading.ac.uk
>
> Rendering animation (MS Windows)
> (Message that indicates the frame to be render is displayed AFTER the
> rendering.)
> http://news.povray.org/3BAC1D0C.74A4A503@free.fr
>
> Stop during mosaic: crash
> http://news.povray.org/Xns9126925CDC108seed7@povray.org
>
> sin(X)^sin(X) -> crash!
> http://news.povray.org/3baf7992@news.povray.org
>
> Bug with parse_string
> http://news.povray.org/9pk0rto8s07dnm320f5m503aqu43ak6g3p@4ax.com
>
> Spline bug
> (The spline path is all wrong when certain time values are used.)
> http://news.povray.org/3bb41dc8@news.povray.org
>
> Radiosity crash when user stops render during pretrace.
> http://news.povray.org/3bb4605d$1@news.povray.org
>
> Highlight bug
> http://news.povray.org/3bb4cf08@news.povray.org
>
> Macro bug
> (POV can dereference a deallocated pointer if you return a local from a
> macro.)
> http://news.povray.org/3BB4ED11.8EC69CEC@hotmail.com
>
> Crash after constant function
> http://news.povray.org/kc3hqtkgj93f82rpkj6puvlj8f5cs7nk0q@4ax.com
>
> Bug with intersection stack (with crash)
> http://news.povray.org/5f13rtc0v0rso4fk7lut5e0980qa9g756b@4ax.com
>
> Crash with long strings
> (Ignore documentation bug report.)
> 3b54rt8puoibdtdsquqgv1fuo0m9mn6k30@4ax.com
>
> Rune
>
>

Post a reply to this message

JRG wrote:
> 
> What about the "sphere_sweep and radiosity" bug? I hope I don't look like a
> monomaniac, but IIRC C. Hormann could replicate that as well... needs this
> more confirmation?
> 

I have mentioned this several times during pre-beta with sample code and
renders so the POV-Team is aware of it.  

Should certainly be part of the bug list IMO.

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

But it seems like Nathan Kopp cannot replicate it, which is a problem since
it's him who should fix it.

--
Jonathan

"Christoph Hormann" <chr### [at] gmxde> ha scritto nel messaggio
news:3BBA31C3.ED219A49@gmx.de...
>
>
> JRG wrote:
> >
> > What about the "sphere_sweep and radiosity" bug? I hope I don't look
like a
> > monomaniac, but IIRC C. Hormann could replicate that as well... needs
this
> > more confirmation?
> >
>
> I have mentioned this several times during pre-beta with sample code and
> renders so the POV-Team is aware of it.
>
> Should certainly be part of the bug list IMO.
>
> 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

JRG wrote:
> 
> But it seems like Nathan Kopp cannot replicate it, which is a problem since
> it's him who should fix it.
> 

Ok, i will post scene and renders again so everyone can try to replicate
it.

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

"JRG" wrote:
> What about the "sphere_sweep and radiosity" bug?

Thanks, I have included this bug report on the list.

Rune

Post a reply to this message

"Redbeard (MDJohnson)" wrote:
> no one seems to have even looked at, or at least replied to.

> http://news.povray.org/3bb2bcc4@news.povray.org

At least I could reproduce it. Beta4, W2k sp2, 2*Celeron 400 on Abit
BP6, 512Mb memory.

-- 
          /"\                           |    iki.
          \ /     ASCII Ribbon Campaign |    fi/
           X      Against HTML Mail     |    zds
          / \

Post a reply to this message

"JRG" <jrg### [at] hotmailcom> wrote...
> But it seems like Nathan Kopp cannot replicate it, which is a problem
since
> it's him who should fix it.

Breakthrough!!!!  I figured out why I couldn't replicate your problem.  I
also figured out why adding an "invisible" object made the problem go away.

I have the following lines in my POVRAY.INI file:
Bounding=on
Bounding_Threshold=1

If I comment out the second line, I am able to replicate the problem.  These
settings determine if POV-Ray uses bounding slabs, which in turn affects the
use of light buffers and use of the vista buffer.

I still don't know the exact cause of the problem, but I'm getting much
closer now!

For now, the workaround is to add those two lines to your povray.ini file.

-Nathan

Post a reply to this message

Nathan Kopp wrote:
> 
> Breakthrough!!!!  I figured out why I couldn't replicate your problem.  I
> also figured out why adding an "invisible" object made the problem go away.
> 
> I have the following lines in my POVRAY.INI file:
> Bounding=on
> Bounding_Threshold=1
> 
> [...]

Hmm, interesting.  Isn't it normally that bounding causes problems and not
that they are solved by it?

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

I wonder what is the purpose for the bounding threshold? Why it couldn't
be just 1 and that's it? Is there any case where this would make rendering
considerably slower (and I'm not talking about 3 seconds vs. 1 second, but
for example 30 minutes vs. 10 minutes)?

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

Post a reply to this message

That's good to hear.
The only problem is that the scene which showed me the bug the first time
contains some thousands objects, so I think bounding was used by default.

--
Jonathan.
"Nathan Kopp" <nat### [at] koppcom> ha scritto nel messaggio
news:3bc0c2c6@news.povray.org...
>
> "JRG" <jrg### [at] hotmailcom> wrote...
> > But it seems like Nathan Kopp cannot replicate it, which is a problem
> since
> > it's him who should fix it.
>
> Breakthrough!!!!  I figured out why I couldn't replicate your problem.  I
> also figured out why adding an "invisible" object made the problem go
away.
>
> I have the following lines in my POVRAY.INI file:
> Bounding=on
> Bounding_Threshold=1
>
> If I comment out the second line, I am able to replicate the problem.
These
> settings determine if POV-Ray uses bounding slabs, which in turn affects
the
> use of light buffers and use of the vista buffer.
>
> I still don't know the exact cause of the problem, but I'm getting much
> closer now!
>
> For now, the workaround is to add those two lines to your povray.ini file.
>
> -Nathan
>
>
>
>
>

Post a reply to this message