Chris Huff wrote:
> 
> In article <38791f53@news.povray.org>, "Nathan Kopp" <Nat### [at] Koppcom>
> wrote:
> 
> > There are two concepts here.  One is the portal (hologram), the other is
> > the camera.  They would have to work differently, I think.
> 
> Good point, if you made a security camera monitor using the portal
> pigment, the areas visible through it would change as you moved around
> the monitor.

Hence flaten Key word with extra angle. which i forgot to mention
in the first post. However it does require an addition to both
Trace(.., MaxDepth) and Compute_Pigment(..., Ray)

They would work differntly.. but only by calculation of 
the ray to trace other wise the other configurations 
can be applied to each type.


-- 
Matthew Corey Brown                                         XenoArch
mcb### [at] xenoarchcom                             http://www.xenoarch.com

Post a reply to this message

Chris Huff <chr### [at] yahoocom> wrote...
> One possible solution would be a pigment which would take the same
> information the camera takes. This would probably have to render the
> scene from the point of view of the target position and use that as an
> image map(internally). While this would be very useful, it might be
> quite difficult to code.

Actually, there is a very nice function called create_ray() in render.c that
would make this relatively easy, with no need to use an internal image map.

-Nathan

Post a reply to this message

In article <38794ffc@news.povray.org>, "Nathan Kopp" <Nat### [at] Koppcom> 
wrote:

> Chris Huff <chr### [at] yahoocom> wrote...
> > One possible solution would be a pigment which would take the same
> > information the camera takes. This would probably have to render the
> > scene from the point of view of the target position and use that as an
> > image map(internally). While this would be very useful, it might be
> > quite difficult to code.
> 
> Actually, there is a very nice function called create_ray() in render.c 
> that
> would make this relatively easy, with no need to use an internal image 
> map.

How would it handle the projection? Since it is being projected onto an 
arbitrary object, not necessarily a flat screen plane.

-- 
Chris Huff
e-mail: chr### [at] yahoocom
Web page: http://chrishuff.dhs.org/

Post a reply to this message

Chris Huff <chr### [at] yahoocom> wrote...
> How would it handle the projection? Since it is being projected onto an
> arbitrary object, not necessarily a flat screen plane.

I would use a syntax as a mix between image_map and camera.  You'd specify a
bunch of camera options, and then image_map options.  The image_map options
would determine the mapping (which determines the x and y values that), and
the camera options would determine how the new ray that was created (by
calling create_ray with those x and y values).  Then, you'd just have to
trace the ray that create_ray created.

-Nathan

Post a reply to this message

Chris Huff <chr### [at] yahoocom> wrote:
: Good point, if you made a security camera monitor using the portal 
: pigment, the areas visible through it would change as you moved around 
: the monitor.

  Not if you make the ray to go always in the same direction, independently
of the direction of the incoming ray.

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

I am thinking mirage would be fairly descriptive. This does pretty much
what they do. Bends the view to see something that you can't see
from where you are.

Chris Huff wrote:
> 
> In article <3878EA1A.7B5E34A7@pacbell.net>, lin### [at] povrayorg
> wrote:
> 
> > Portal sound more like an object identifier than a pattern modifier or
> > type.
> >
> >  How about "Transwarp" ?
> >
> > It has a catchy ring to it and is moderately descriptive of the process.
> 
> I still prefer "portal", it is more descriptive of what the pigment does
> than "transwarp". An object with this pigment will act like a portal to
> another part of space.
> 
> A couple other possibilties:
> wormhole
> mirage
> gateway
> space_time_bending_thingammajiggy_pigment :-)
> 
> One thing that might be even more interesting would be a pigment that
> takes a scene file as a parameter. Both scene files would be parsed, and
> a ray could travel from one scene into the other through objects with
> the portal pigment. Of course, this would require extensive
> modifications to the code, and wouldn't be much more useful(if at all)
> than just one scene.
> 
> --
> Chris Huff
> e-mail: chr### [at] yahoocom
> Web page: http://chrishuff.dhs.org/

-- 
Mr. Art

"Often the appearance of reality is more important 
than the reality of the appearance."
Bill DeWitt 2000

Post a reply to this message

Nieminen Juha <war### [at] punarastascstutfi> wrote...
> Chris Huff <chr### [at] yahoocom> wrote:
> : Good point, if you made a security camera monitor using the portal
> : pigment, the areas visible through it would change as you moved around
> : the monitor.
>
>   Not if you make the ray to go always in the same direction,
independently
> of the direction of the incoming ray.
>

But that wouldn't do exactly what you want.  That would only produce an
orthographic camera, not a perspective camera.  And what if you wanted your
camera security camera to do ultra_wide_angle.

Even better, if you could specify an entire camera for the pigment, it would
make it really easy to set up those cross-eye 3D images, since you could
create one main camera which points at two boxes, each with a pigment
created from another camera.

-Nathan

Post a reply to this message

In article <387958f4@news.povray.org>, "Nathan Kopp" <Nat### [at] Koppcom> 
wrote:

> I would use a syntax as a mix between image_map and camera.  You'd 
> specify a
> bunch of camera options, and then image_map options.  The image_map 
> options
> would determine the mapping (which determines the x and y values that), 
> and
> the camera options would determine how the new ray that was created (by
> calling create_ray with those x and y values).  Then, you'd just have to
> trace the ray that create_ray created.

I think I see what you are saying, sort of UV-map a camera onto the 
object?
Hmm, and two additional types would be a pseudo-orthographic(where the 
rays are always shot in the same direction, no matter what their 
position), and one where the rays are always shot through a point in 
space. This might be similar to perspective.

This could be a very fun tool, especially with warps and pigment_maps.

-- 
Chris Huff
e-mail: chr### [at] yahoocom
Web page: http://chrishuff.dhs.org/

Post a reply to this message

mirage ?

Post a reply to this message

Nathan Kopp <Nat### [at] koppcom> wrote:
:>   Not if you make the ray to go always in the same direction,
: independently
:> of the direction of the incoming ray.

: But that wouldn't do exactly what you want.  That would only produce an
: orthographic camera, not a perspective camera.  And what if you wanted your
: camera security camera to do ultra_wide_angle.

  Ok, my statement was incomplete.
  What I meant was that for a _specific point_ the ray could go always to
the same direction. The direction could then depend on the point calculated
(but not on the direction of the incoming ray), thus allowing perspective or
whatever.

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