Ken <tyl### [at] pacbellnet> wrote:
:  I think a lot of people think of a plane object as an object similar to
: a piece of paper with no deminsions in two directions but a finite
: thickness. It is this misconception that causes the confusion.

  Perhaps "plane" should be changed to "infinite_box".

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

Somehow, "Reflective sphere over checkered infinite_box" doesn't quite have
the same ring to it.. *grin*

Nieminen Mika wrote:

>   Perhaps "plane" should be changed to "infinite_box".

Post a reply to this message

Alex Vandiver wrote:
> 
> Somehow, "Reflective sphere over checkered infinite_box" doesn't quite have
> the same ring to it.. *grin*

 I agree that certain eshetics must be maintained and this is one of them.
Besides "plane" is much easier to type than Warp's alternative identifier.


-- 
Ken Tyler

mailto://tylereng@pacbell.net

Post a reply to this message

Nieminen Mika wrote:
> 
> Ken <tyl### [at] pacbellnet> wrote:
> :  I think a lot of people think of a plane object as an object similar to
> : a piece of paper with no deminsions in two directions but a finite
> : thickness. It is this misconception that causes the confusion.
> 
>   Perhaps "plane" should be changed to "infinite_box".

maybe "half-space"? BTW, would a very big box render faster than a plane
or vice versa?

Just curious,
/PETER/

-- 
Peter Santo (PUMP development)
Visit: http://www.ieee.rwth-aachen.de/mp3/

Post a reply to this message

Peter Santo <san### [at] poolinformatikrwth-aachende> wrote:
: maybe "half-space"? BTW, would a very big box render faster than a plane
: or vice versa?

  I have always noticed, that planes are strangely slow to render, while
boxes are much faster, and I have always wondered why. In a box, you have to
test the intersection with 8 sides while in a plane you have to test the
intersection with just one side. If you make 50 big boxes it surely will
render faster than 50 planes.
  Can anyone explain why is this?

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

Maybe because planes are bounded larger?   I never really compared them, but
that's my guess.

-Mike

Nieminen Mika wrote:

> Peter Santo <san### [at] poolinformatikrwth-aachende> wrote:
> : maybe "half-space"? BTW, would a very big box render faster than a plane
> : or vice versa?
>
>   I have always noticed, that planes are strangely slow to render, while
> boxes are much faster, and I have always wondered why. In a box, you have to
> test the intersection with 8 sides while in a plane you have to test the
> intersection with just one side. If you make 50 big boxes it surely will
> render faster than 50 planes.
>   Can anyone explain why is this?
>
> --
> 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

wow i'm all glad ya had fun with my question hehe :)

Nobot wrote:

> any one know why when i have a set of planes like the diagram below i
> can't use fog it says camera in non hollow object "o" is the campera
> looking at the smi transpetant planes
>                yyy
>                 | | |
> o               | | |
> _______  | | |_____z
> ________| | |_____z
> ________| | |_____z

Post a reply to this message

Nieminen Mika wrote:
> 
> Peter Santo <san### [at] poolinformatikrwth-aachende> wrote:
> : maybe "half-space"? BTW, would a very big box render faster than a plane
> : or vice versa?
> 
>   I have always noticed, that planes are strangely slow to render, while
> boxes are much faster, and I have always wondered why. In a box, you have to
> test the intersection with 8 sides while in a plane you have to test the
> intersection with just one side. If you make 50 big boxes it surely will
> render faster than 50 planes.
>   Can anyone explain why is this?

	I have not looked at the code but descriptions of how it works
in the docs suggests one of the first things it does before
rendering is check for bounds. That should result in faster
computation such as like precomuting tpi=2*pi when 2*pi is used
thousands of times. 

	An infinite object like a plane does not have bounds and so
there can be no precomputing for speed.

Post a reply to this message

Attachments:
Download 'us-ascii' (1 KB)

Matt Giuer <mgi### [at] giwersworldorg> wrote:
: 	I have not looked at the code but descriptions of how it works
: in the docs suggests one of the first things it does before
: rendering is check for bounds. That should result in faster
: computation such as like precomuting tpi=2*pi when 2*pi is used
: thousands of times. 

  A single box object does not have a bound, and even if it did, it would
be a... box!

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

Yes it does... it's auto bound for the vistas.

Or at least that's what I thought... (switch on vista display and you should
see the auto bounds)

--
Lance.


---
For the latest 3D Studio MAX plug-ins, images and much more, go to:
The Zone - http://come.to/the.zone
For a totally different experience, visit my Chroma Key Website:
Colorblind - http://listen.to/colorblind

Post a reply to this message