![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Okay I have a patch designed and am about ready to implement. But
I haven't clue what to call the keyword. I have come up with two
but rejected for various reasons.
What it does:
Its a new pigment (non pattern) that Transforms
the ray and traces that to determine the color of the pigment.
you would be able to make holograms, security monitors
recursive images , surreal images etc.
the syntax would be
PIGMENT_TYPE
[transmit float]
[filter float]
[depth float]
transforms
the two names i've comeup with are
warp (rejected to parsing confusion}
displace (rejected as not to confuse
non exsistant displacement mapping)
any ideas?
--
Matthew Corey Brown XenoArch
mcb### [at] xenoarch com http://www.xenoarch.com
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>What it does:
>Its a new pigment (non pattern) that Transforms
>the ray and traces that to determine the color of the pigment.
>you would be able to make holograms, security monitors
>recursive images , surreal images etc.
I'm afraid I don't understand your explanation. Could you perhaps rephrase
this? After I get it, then I'll suggest a name. Perhaps "hologram" wouldn't
be a bad idea, if you say it does that. Could you post an example image?
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <3878D443.E7B1EE2B@xenoarch.com>, Matthew Corey Brown -
XenoArch <mcb### [at] xenoarch com> wrote:
> Okay I have a patch designed and am about ready to implement. But
> I haven't clue what to call the keyword. I have come up with two
> but rejected for various reasons.
>
> What it does:
> Its a new pigment (non pattern) that Transforms
> the ray and traces that to determine the color of the pigment.
> you would be able to make holograms, security monitors
> recursive images , surreal images etc.
Unless I completely misunderstand you, this sounds like something I have
been thinking about for some time now, but never got around to
implementing. I would call it "portal", because it would make the object
act like a link to another position in space.
And what I was thinking of would be less flexible than what you are
doing.
--
Chris Huff
e-mail: chr### [at] yahoo com
Web page: http://chrishuff.dhs.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
TonyB wrote:
>
> >What it does:
> >Its a new pigment (non pattern) that Transforms
> >the ray and traces that to determine the color of the pigment.
> >you would be able to make holograms, security monitors
> >recursive images , surreal images etc.
>
> I'm afraid I don't understand your explanation. Could you perhaps rephrase
> this? After I get it, then I'll suggest a name. Perhaps "hologram" wouldn't
> be a bad idea, if you say it does that. Could you post an example image?
Heh can't post an image till i implent it and i don't like
to implement till i have everything fleshed out (that includes
keywords, its the software developer in me)
.. also forgot to add following keywords (for security/tv monitor
functions)
[flatten [angle float]]
I'll try to explain better
okay instead of having a pattern and color map to determin the color
of the object, it takes the incoming ray.. transforms it with the
pigments transformations and warps then traces a new ray in the
scene using the transformed ray. Applys the resulting color
as the pigment...
Hologram is too limiting though... hmm maybe transmission
(from TV or Hologram transmissions) but would that be
confused with transmit?
another possiblity is to call it portal (ie Unreal's Portals for
those that play and it works along the same idea as that game's
portals)
well at least you got me to think of a couple more possibilties
to call it.
--
Matthew Corey Brown XenoArch
mcb### [at] xenoarch com http://www.xenoarch.com
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Chris Huff wrote:
>
> In article <3878D443.E7B1EE2B@xenoarch.com>, Matthew Corey Brown -
>
> Unless I completely misunderstand you, this sounds like something I have
> been thinking about for some time now, but never got around to
> implementing. I would call it "portal", because it would make the object
> act like a link to another position in space.
> And what I was thinking of would be less flexible than what you are
> doing.
>
Thats 3 votes for portal heh (posted same time heheh.. and chris counts
as two cause he posted as i was writing my last one =} )
anyone else have any ideas?
BTW this would require you to have superpatch or megapov to work.
(uses the intersection that was added to compute_pigment)
--
Matthew Corey Brown XenoArch
mcb### [at] xenoarch com http://www.xenoarch.com
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Matthew Corey Brown - XenoArch wrote:
>
> Okay I have a patch designed and am about ready to implement. But
> I haven't clue what to call the keyword. I have come up with two
> but rejected for various reasons.
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.
--
Ken Tyler - 1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <3878EA1A.7B5E34A7@pacbell.net>, lin### [at] povray org
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] yahoo com
Web page: http://chrishuff.dhs.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Not useful? Might be an understatement there. Imagine the one scene (call it
an included scene) doing things while the main scene is rendering it in as a
sphere or box or what have you and being dynamically linked, most useful in
animation.
This type of thing reminds me of the old window viewport "world coordinates" and
such stuff somehow.
http://hpsalo.cern.ch/TaligentDocs/TaligentOnline/DocumentRoot/1.0/Docs/classes/
TGrafPort.html while not exactly the same thing I suppose it mentions "Port"
anyway and that sounds about right for this so 'portal' or at least 'port' might
be good. If the idea is to have a window on another scene part (if I follow
this at all) then I can't see a more fitting term.
Not really pigment or texture anyway is this? I mean, could be a objectless
entity right?
Bob
"Chris Huff" <chr### [at] yahoo com> wrote in message
news:chrishuff_99-88B257.15443709012000@news.povray.org...
> In article <3878EA1A.7B5E34A7@pacbell.net>, lin### [at] povray org
> 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] yahoo com
> Web page: http://chrishuff.dhs.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <38791738@news.povray.org>, "omniVERSE" <inv### [at] aol com>
wrote:
> Not useful? Might be an understatement there. Imagine the one scene
> (call it
> an included scene) doing things while the main scene is rendering it in
> as a
> sphere or box or what have you and being dynamically linked, most useful
> in animation.
I meant that having it be a portal to a separate scene file wouldn't be
any more useful than being a portal to another part of the main scene.
You could make it "link" to a portion of the scene that is out of sight
instead.
> Not really pigment or texture anyway is this? I mean, could be a
> objectless entity right?
Well, it requires an object to define the area the portal occupies, and
making it a pigment type like image_map makes it a lot more
versatile(you can use it in texture_maps to make the portal irregularly
transparent, and turbulence might be interesting.
For my version I had been thinking of an "is_portal" attribute for
objects. This would have been a lot more limiting.
A couple more possibilities for the name:
ray_transform (This one is very precisely descriptive of the process,
but doesn't give a good idea of what it actually does. I don't care for
it much.)
magic_mirror
looking_glass
--
Chris Huff
e-mail: chr### [at] yahoo com
Web page: http://chrishuff.dhs.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Matthew Corey Brown - XenoArch <mcb### [at] xenoarch com> wrote...
> Its a new pigment (non pattern) that Transforms
> the ray and traces that to determine the color of the pigment.
> you would be able to make holograms, security monitors
> recursive images , surreal images etc.
>
There are two concepts here. One is the portal (hologram), the other is the
camera. They would have to work differently, I think.
-Nathan
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |