 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello!
transform is not transforming the bounding boxes in this release (beta
35). I think this happened already in beta 32 (if i remember). Again,
this code renders ok in pov 3.6:
global_settings{#if(version < 3.7) assumed_gamma 1 #end}
camera{location x*10+z*5+y*5 look_at 0}
light_source{(x+y)*10 1}
background{rgb <0.5,0.6,0.7>}
#declare T1= transform{translate x}
#declare Ob1= intersection{
sphere{0 10 translate -z*9.5}
sphere{0 10 translate z*9.5}
cylinder{z*2,-z*2 1 inverse}
pigment{red 1}
bounded_by{box{2.6, -2.6}}
transform{ T1}
}
#declare Ob2= intersection{
sphere{0 10 translate -x*9.5}
sphere{0 10 translate x*9.5}
cylinder{x*2,-x*2 1 inverse}
pigment{green 1}
bounded_by{box{2.6, -2.6}}
transform{ T1}
}
union{
object{Ob1} //<----- :?.. where is my bounding box!
object{Ob2}
transform{T1}
}
Thank you!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Martin a écrit :
> Hello!
>
> transform is not transforming the bounding boxes in this release (beta
> 35). I think this happened already in beta 32 (if i remember). Again,
> this code renders ok in pov 3.6:
Manual bounding is not clipping.
From my historical knowledge: windows-pov got a default +MB3 whereas
unix sticked to +MB25
Maybe the 3.7 get a uniform value for all ?
With so few objects, bounding would be turned off, which might explains
your issue.
Whatever, if you want to clip, use clipping_by.
--
A: Because it messes up the order in which people normally read text.<br/>
Q: Why is it such a bad thing?<br/>
A: Top-posting.<br/>
Q: What is the most annoying thing on usenet and in e-mail?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le_Forgeron <lef### [at] free fr> wrote:
> Whatever, if you want to clip, use clipping_by.
clipped_by is another possibility. It's slightly better in that it doesn't
give any parsing error.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le_Forgeron escribió:
>
> Manual bounding is not clipping.
>
> From my historical knowledge: windows-pov got a default +MB3 whereas
> unix sticked to +MB25
> Maybe the 3.7 get a uniform value for all ?
> With so few objects, bounding would be turned off, which might explains
> your issue.
>
> Whatever, if you want to clip, use clipping_by.
>
What is it that makes you think that i want to clip? I want to bound.
The objects should look as two lenticular shapes. Is just a test.
I have more complex objects prperly bounded_by, to speed render, that
rendered ok with beta 34, and now don't render as they should, and the
objects are exactly the same.
+MB25 gives the same (wrong) results in this beta.
Thank You
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 14/01/2010 11:58, Martin nous fit lire :
>
> What is it that makes you think that i want to clip? I want to bound.
> The objects should look as two lenticular shapes. Is just a test.
But that bounding is:
1. Manual (and probably not needed)
2. far too big at least in one direction
3. wrong: some part of the intersection are outside the box (check it
with clipped_by or adding the box in the intersection)
Garbage in, Garbage out.
Hence my suggestion to clipped_by.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le_Forgeron escribió:
> Le 14/01/2010 11:58, Martin nous fit lire :
>> What is it that makes you think that i want to clip? I want to bound.
>> The objects should look as two lenticular shapes. Is just a test.
>
> But that bounding is:
> 1. Manual (and probably not needed)
> 2. far too big at least in one direction
> 3. wrong: some part of the intersection are outside the box (check it
> with clipped_by or adding the box in the intersection)
>
> Garbage in, Garbage out.
> Hence my suggestion to clipped_by.
All right, sorry. At first sight it seemed to me the same problem, so I
was using a test 2 years old, thinking it was well bounded :).
Now I try to see what happens, and seems like the cone is inverted.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I installed beta 35 just five days ago, and i've seen the new one right
now. Problem solved.
Thanks to you and all the Pov-team for doing pov-ray.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
