|
|
Hi!
I think I've found a bug in sor :-(
I use Linux (Kernel 2.2.5-ac1), AMD K6-2-350
self compiled Povray version 3.1e (tried with and without uvpatch)
I've also tried an inofficial version of I've compiled 3.1 and the bug
didn't seem to be present...
In povray 3.0 there seemed to be a bug, too... but it looks different.
I've sent a mail to povray.binary.images with attached images of the bug.
The subject is "sor bug" and "sor bug forgotten images".
Below is the sourcecode of the scene:
camera {
location <10,20,-30>
look_at <0.01,0.01,0.01>
}
light_source {
<5,100,-20>
color rgb <1,1,1>
}
light_source {
<50,-100,-20>
color rgb <1,1,1>
}
sor {
19
<10,0>
<11,1>
<13,2>
<14,3>
<15,4>
<16,5>
<17,6>
<18,7>
<19,8>
<20,9>
<21,10>
<22,16>
<23,17>
<24,18>
<25,19>
<26,20>
<27,21>
<28,22>
<30,23>
finish {ambient 0.4}
texture {
pigment {
checker
color rgb <1.4,1,0.6>
color rgb <0,1,0>
}
}
sturm
scale -y
}
--
Ronald Lembcke (aka _crash)
es1### [at] fenbaynetde
Post a reply to this message
|
|
|
|
If you are referring to the missing end caps, I think that's a known
"feature" and a mistake in the dokumentation.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
|
|
Apparently so. Version 3.0* renders the 'sor' objects as 'open' as
default it seems. And version 3.1e is rendering them as closed unless
the 'open' keyword is used, so it was a problem with the 3.0* version.
This is now correct behaviour and the latest DOC is not corrected being
still the same as version 3.0* DOC.
Nieminen Mika wrote:
>
> If you are referring to the missing end caps, I think that's a known
> "feature" and a mistake in the dokumentation.
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/homepage.htm
mailto:inv### [at] aolcom?Subject=PoV-News
Post a reply to this message
|
|