I have an image map as an emblem on a figure.  How do I stop it from
showing up on the back, too?

Post a reply to this message

Greg, take a look at povray.newusers and my reply to Simon Adameit in the
thread 'image map' recently (today, June 16 11:06AM). subject line changed
to "image map (cylindrical warping)" which Warp suggested doing.

bob h

Post a reply to this message

Thanks but ugh.  So I'd need an image that itself is able to wraparound,
instead of just a tiny little "decal"?

bob h wrote:

> Greg, take a look at povray.newusers and my reply to Simon Adameit in the
> thread 'image map' recently (today, June 16 11:06AM). subject line changed
> to "image map (cylindrical warping)" which Warp suggested doing.
>
> bob h

Post a reply to this message

"Greg M. Johnson" <"gregj;-)56590\""@aol.c;-)om> wrote in message
news:3d0d4c72@news.povray.org...
> I have an image map as an emblem on a figure.  How do I stop it from
> showing up on the back, too?
>

I did a model of a ship a while back and to put the logos on I used an
image_map incorporated into an object pattern.  I think the object pattern
is one of my favourite new features of 3.5, very useful.

-tgq

Post a reply to this message

Try using a slope_map.

Greg M. Johnson wrote:

> I have an image map as an emblem on a figure.  How do I stop it from
> showing up on the back, too?
> 
> 


-- 
Samuel Benge

sbe### [at] caltelcom

Post a reply to this message

"Greg M. Johnson" <"gregj;-)56590\""@aol.c;-)om> wrote in message
news:3d0e8a75@news.povray.org...
> Thanks but ugh.  So I'd need an image that itself is able to wraparound,
> instead of just a tiny little "decal"?

I think scaling can be done to any size image but of course the aspect ratio
still matters. Just doesn't need to be wrappable.

bob h

Post a reply to this message

Samuel Benge <sbe### [at] caltelcom> wrote:
> Try using a slope_map.

  slope_map is related to normals, not pigments.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

> > Try using a slope_map.
>
>   slope_map is related to normals, not pigments.
>
I think he must be refering to the slope pattern from 3.5 and megaPOV.
Should be able to work though it wouldn't be my prefered method.

-tgq

Post a reply to this message

Thanks for all the conversation, but here's the application:

I have a blob human figure.  I want a little emblem on the chest (like the
"4" on Reed Richards or the "S" on Superman.)  A map_type 0 allows me to
nicely place a bitmap which is "just the emblem", a square, on the chest,
but also puts it on the back.  A map_type 2 (is that cylindrical?)  takes my
bitmap and wraps it around the hole perimeter of my object, while wildly
distorting it.

I want:
EMBLEM
EMBLEM
EMBLEM

I'm afraid map_type 2 would require a bitmap like this  below, with a huge
headache of trying to decide how much extra --- solid color to add:

------------------EMBLEM---------
------------------EMBLEM---------
------------------EMBLEM---------

I'm stuck with Mega 0.7 for now for personal reasons.  And I don't
understand a slope_map application for this problem.

Post a reply to this message

> nicely place a bitmap which is "just the emblem", a square, on the chest,
> but also puts it on the back.  A map_type 2 (is that cylindrical?)  takes
my
> bitmap and wraps it around the hole perimeter of my object, while wildly
> distorting it.
>
> I want:
> EMBLEM
> EMBLEM
> EMBLEM
>
> I'm afraid map_type 2 would require a bitmap like this  below, with a huge
> headache of trying to decide how much extra --- solid color to add:
>
> ------------------EMBLEM---------
> ------------------EMBLEM---------
> ------------------EMBLEM---------
>
> I'm stuck with Mega 0.7 for now for personal reasons.  And I don't
> understand a slope_map application for this problem.

(I think) megaPOV has the object pattern, though I'm not sure if the syntax
is exactly the same as in 3.5, but here is an example of how to use it in
3.5:


//start
pigment{
  object{
    box{<-1,-1,0><1,1,0>} //where to place the square emblem on the man's
body (make sure this object only intersects the front half
    //This box assumes the man us upright in the y direction and faces the z
direction
    pigment{Pigment_Outside_The_Emblem} //pigment outside box
    ,
    pigment{  //pigment inside box
      image_map{sys "EmblemImage" interpolate 4}
      translate<-.5,-.5,0>
      scale <2,2,1>
    }
  }
}
//end

let me know if this of use or if you don't fully understand it.
g'luck

-tgq

Post a reply to this message

> //start
> pigment{
>   object{


oops.
    box{<-1,-1,0><1,1,0>}  should be:
    box{<-1,-1,0><1,1,z>} //where z is a distance that makes the box
intersect with the front of the man

//where to place the square emblem on the man's
> body (make sure this object only intersects the front half
>     //This box assumes the man us upright in the y direction and faces the
z
> direction
>     pigment{Pigment_Outside_The_Emblem} //pigment outside box
>     ,
>     pigment{  //pigment inside box
>       image_map{sys "EmblemImage" interpolate 4}
>       translate<-.5,-.5,0>
>       scale <2,2,1>
>     }
>   }
> }
> //end
>
> let me know if this of use or if you don't fully understand it.
> g'luck
>
> -tgq
>
>
>

Post a reply to this message

Thanks, but after I invested some time in a bitmap decal I'm really hooked
on it.
I suppose the solution is two type 0 maps.
One is the normal decal.
The other is the color of the "clothes fabric" but rotated 90*y and
translated to cover up the back.

feature request: one sided type 0 map.

Post a reply to this message

"Greg M. Johnson" <gregj:-)565### [at] aolcom> wrote in message
news:3d1080d8$1@news.povray.org...
> Thanks, but after I invested some time in a bitmap decal I'm really hooked
> on it.
> I suppose the solution is two type 0 maps.
> One is the normal decal.
> The other is the color of the "clothes fabric" but rotated 90*y and
> translated to cover up the back.
>
> feature request: one sided type 0 map.
>
Why do you think the solution I posted wouldn't do what you want?  Could you
explain exactly what you are you trying to do?

-tgq

Post a reply to this message

oops.  I guess I saw "object pattern" and my heart sunk, as I didn't want to
just place a text "M".

 *Now* I understand your solution and more sincerely thank you for it.

Post a reply to this message

Yeah, 'slope' was what I meant to write....

TinCanMan wrote:

>>>Try using a slope_map.
>>>
>>  slope_map is related to normals, not pigments.
>>
>>
> I think he must be refering to the slope pattern from 3.5 and megaPOV.
> Should be able to work though it wouldn't be my prefered method.
> 
> -tgq
> 
> 
> 


-- 
Samuel Benge

sbe### [at] caltelcom

Post a reply to this message

Sorry Greg, I meant to type 'slope', not slope_map. Slope would allow 
the emblem to only show up on the front of the model if you want. See 
the docs for a more detailed description of the slope pattern. Here's 
what it might look like in your scene if the model is facing -z:

pigment{
  slope z
  pigment_map{
   [0 my_emblem]
   [.25 rgb<.1 .2 .9>]
  }
}

Greg M. Johnson wrote:

> I'm stuck with Mega 0.7 for now for personal reasons.  And I don't
> understand a slope_map application for this problem.

-- 
Samuel Benge

sbe### [at] caltelcom

Post a reply to this message

"Samuel Benge" <sbe### [at] caltelcom> wrote in message
news:3D1### [at] caltelcom...
> Sorry Greg, I meant to type 'slope', not slope_map. Slope would allow
> the emblem to only show up on the front of the model if you want. See
> the docs for a more detailed description of the slope pattern. Here's
> what it might look like in your scene if the model is facing -z:
>
> pigment{
>   slope z
>   pigment_map{
>    [0 my_emblem]

    [0.25 my_emblem]

>    [.25 rgb<.1 .2 .9>]
>   }
> }
>


need to add that line otherwise the emblem will blend to the colour  (unless
the front of the man is perfectly flat of course).

-tgq

Post a reply to this message

Thanks, BUT I think that MegaPov 0.7 does not accept an image_map as one of the
colors in an object pattern.

TinCanMan wrote:

> > //start
> > pigment{
> >   object{
>
> oops.
>     box{<-1,-1,0><1,1,0>}  should be:
>     box{<-1,-1,0><1,1,z>} //where z is a distance that makes the box
> intersect with the front of the man
>
> //where to place the square emblem on the man's
> > body (make sure this object only intersects the front half
> >     //This box assumes the man us upright in the y direction and faces the
> z
> > direction
> >     pigment{Pigment_Outside_The_Emblem} //pigment outside box
> >     ,
> >     pigment{  //pigment inside box
> >       image_map{sys "EmblemImage" interpolate 4}
> >       translate<-.5,-.5,0>
> >       scale <2,2,1>
> >     }
> >   }
> > }
> > //end
> >
> > let me know if this of use or if you don't fully understand it.
> > g'luck
> >
> > -tgq
> >
> >
> >

Post a reply to this message

On Thu, 20 Jun 2002 21:12:49 -0500, Greg M. Johnson wrote:

> Thanks, BUT I think that MegaPov 0.7 does not accept an image_map as one
> of the colors in an object pattern.

Of course not, an image map isn't a color. Use pigments or textures.
Basically, anything you can do with checker, you can do with object.


-- 
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: <chr### [at] tagpovrayorg>
WWW: http://homepage.mac.com/chrishuff/

Post a reply to this message

I spent an hour trying it but it didn't work.
Can you give me an example of

pigment{object{foobar} ................

finish the line where one is a pigment{image_map{...  , please if you will.

Neither the html help for mega 0.7 nor my imagination could find a syntax mega
would accept.

Christopher James Huff wrote:

> On Thu, 20 Jun 2002 21:12:49 -0500, Greg M. Johnson wrote:
>
> > Thanks, BUT I think that MegaPov 0.7 does not accept an image_map as one
> > of the colors in an object pattern.
>
> Of course not, an image map isn't a color. Use pigments or textures.
> Basically, anything you can do with checker, you can do with object.
>
> --
> Christopher James Huff <chr### [at] maccom>
> POV-Ray TAG e-mail: <chr### [at] tagpovrayorg>
> WWW: http://homepage.mac.com/chrishuff/

Post a reply to this message

Greg M. Johnson <"gregj;-)56590\""@aol.c;-)om> wrote:
> Thanks, BUT I think that MegaPov 0.7 does not accept an image_map as one of the
> colors in an object pattern.

  A pattern does not take colors. color_maps do.

  Use the pattern with a pigment_map instead.


-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

> Can you give me an example of
>
> pigment{object{foobar} ................
>
> finish the line where one is a pigment{image_map{...  , please if you
will.
>
> Neither the html help for mega 0.7 nor my imagination could find a syntax
mega
> would accept.

I don't know if the megaPOV syntax works the same, but this works in 3.5:
(you need to wrap both parts in pigment wrappers)

//start
box{<-100,0,-10><100,200,10>
  pigment{
    object{
      box{<-30,80,0><30,140,-20>}
      pigment{rgb 1},
      pigment{
        image_map{png "BB2.png" interpolate 4}
        scale 60
        translate <-30,80,0>
      }
    }
  }
}
//end


-tgq

Post a reply to this message

"Warp" <war### [at] tagpovrayorg> wrote in message
news:3d129a40@news.povray.org...
> Greg M. Johnson <"gregj;-)56590\""@aol.c;-)om> wrote:
> > Thanks, BUT I think that MegaPov 0.7 does not accept an image_map as one
of the
> > colors in an object pattern.
>   A pattern does not take colors. color_maps do.
>

The object pattern IMHO does not take pigments either.   Colors were a last
ditch effort to make something work.

>
>   Use the pattern with a pigment_map instead.
>

Can you suggest a syntax for this?

Post a reply to this message

Greg M. Johnson <gregj:-)565### [at] aolcom> wrote:
>>   Use the pattern with a pigment_map instead.

> Can you suggest a syntax for this?

  I got confused. The object pattern cannot be used with a pigment_map
literally. However, it can take two pigments without problems:

camera { location -z*5 look_at 0 angle 35 }
light_source { -z*10, 1 }

#declare Object = sphere { 0,1 }
#declare Pigm1 = pigment { bozo color_map { [0 rgb 0][1 rgb 1] } }
#declare Pigm2 = pigment { granite color_map { [0 rgb x][1 rgb x+y] } }

plane
{ -z,0
  pigment
  { object
    { Object
      pigment { Pigm1 }
      pigment { Pigm2 }
    }
  }
}


-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

"Greg M. Johnson" <gregj:-)565### [at] aolcom> wrote in message
news:3d131911$1@news.povray.org...
> "Warp" <war### [at] tagpovrayorg> wrote in message
> news:3d129a40@news.povray.org...
> > Greg M. Johnson <"gregj;-)56590\""@aol.c;-)om> wrote:
> > > Thanks, BUT I think that MegaPov 0.7 does not accept an image_map as
one
> of the
> > > colors in an object pattern.
> >   A pattern does not take colors. color_maps do.
> >
>
> The object pattern IMHO does not take pigments either.   Colors were a
last
> ditch effort to make something work.
>
> >
> >   Use the pattern with a pigment_map instead.
> >
>
> Can you suggest a syntax for this?


I do believe the object pattern (like checker, brick, hexagon, etc.) don't
use pigment_maps since they are blocked patterns without smooth transitions.
They expect a specific number of colours or pigment or whatever to work
(pigment_maps can be used within each of these pigments however), i.e.
checker expects 2, hexagon expects 3, object expects 2.  The trick in syntax
is that the elements need to be of the same type, either all colours, all
pigments, etc.  You can't mix n match.  Therefore if you wnat to use an
image map for one element and a colour for the other, since the image_map is
gonna need a pigment wrapper, you need to wrap the colour in a pigment
wrapper as well.  At least the is how it appears to perform in 3.5.
See my previous post for an example that works in 3.5, I can post the source
and image if so required.

-tgq

Post a reply to this message

On Fri, 21 Jun 2002 08:15:19 -0500, Greg M. Johnson wrote:

> The object pattern IMHO does not take pigments either.   Colors were a
> last ditch effort to make something work.

That is not true. It worked the first time I compiled it, and it worked
for everything automatically, there is no need to write special code to
handle each case...this is how it is for any pattern, there was no "last
ditch effort". The syntax is analogous to that for any other block pattern:

texture {object {OBJECT texture {...}, texture {...}}

pigment {object {OBJECT pigment {...}, pigment {...}}

There is even a demo file demonstrating this: object_pattern.pov.


-- 
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: <chr### [at] tagpovrayorg>
WWW: http://homepage.mac.com/chrishuff/

Post a reply to this message

"Christopher James Huff" <chr### [at] maccom> wrote in message
news:pan### [at] maccom...
> That is not true. It worked the first time I compiled it,

Your code is quite logical. It's what 0.7a IIRC refused. I'll try it in 0.7a
again "later"...

Post a reply to this message

"Greg M. Johnson" <gregj:-)565### [at] aolcom> wrote in message
news:3d1326ab$1@news.povray.org...
> "Christopher James Huff" <chr### [at] maccom> wrote in message
> news:pan### [at] maccom...
> > That is not true. It worked the first time I compiled it,
>
> Your code is quite logical. It's what 0.7a IIRC refused. I'll try it in
0.7a
> again "later"...
>
An update here for you.  I don't have megaPOV installed but I downloaded the
help and had a look.  The problem I see (and I don't know which is correct)
is that in 3.5, the pigments are wrapped in the object wrapper, whereas the
megaPOV docs place them after the object wrapper so either megaPOV acts
slightly differently or the docs are wrong.

ie.
3.5 says:

pigment{
  object{
    my_object
    pigment{pig1},
    pigment{pig2}
  }
}

megaPOV says:

pigment{
  object{my_object}
  pigment{pig1},
  pigment{pig2}
}

so you might want to find out which is correct.

-tgq

Post a reply to this message

The following code is accepted:

#declare pigobj=box{-1,1}
#declare clothtexti=texture{pigment{object{pigobj color Blue, color Red}} }

The following code is rejected:

#declare pigobj=box{-1,1}
#declare clothtexti=texture{pigment{object{pigobj shirtpig, objectpig}} }

where shirtpig and object pig are called out earlier.

The error is:
"No matching } in pigment, pigment identifier found instead."


> > "Christopher James Huff" <chr### [at] maccom> wrote in message
> > news:pan### [at] maccom...
> > > That is not true. It worked the first time I compiled it,

Post a reply to this message

Wasn't it Greg M. Johnson who wrote:
>The following code is accepted:
>
>#declare pigobj=box{-1,1}
>#declare clothtexti=texture{pigment{object{pigobj color Blue, color Red}} }
>
>The following code is rejected:
>
>#declare pigobj=box{-1,1}
>#declare clothtexti=texture{pigment{object{pigobj shirtpig, objectpig}} }
>
>where shirtpig and object pig are called out earlier.
>
>The error is:
>"No matching } in pigment, pigment identifier found instead."

The correct syntax is

#declare clothtexti=texture{pigment{object{pigobj pigment{shirtpig},
pigment {objectpig}}} }


-- 
Mike Williams
Gentleman of Leisure

Post a reply to this message

Mike Williams wrote:

> The correct syntax is
> #declare clothtexti=
> texture{
> pigment{object{pigobj
> pigment{shirtpig},
> pigment {objectpig}}} }
>

<weeps maniacally>   Thank you.

Post a reply to this message

On Sat, 22 Jun 2002 21:55:47 -0400, "Greg M. Johnson"
<"gregj;-)56590\""@aol.c;-)om> wrote:
> The following code is accepted:

This is already explained, but just a note, Greg. You probably missed MegaPOV
is _unofficial_ patch.

ABX

Post a reply to this message

If I'm using spheres or torii  in 0.7 and I have a question about the
syntax, should I post to p.u.-p.?

Post a reply to this message

On Mon, 24 Jun 2002 08:18:06 -0400, "Greg M. Johnson" <gregj:-)565### [at] aolcom>
wrote:
> If I'm using spheres or torii  in 0.7 and I have a question about the
> syntax, should I post to p.u.-p.?

Isn't syntax of box or torii already explained in documentation ? Are you
asking about syntax or bug ? Chris Huff already pointed You that there is
example file of object pattern - have You checked this ?
http://users.skynet.be/smellenbergh/demopictures/obj_patternb.jpg
http://users.skynet.be/smellenbergh/demopictures/obj_pattern.zip

ABX

Post a reply to this message

Restating,

While using MegaPov 0.7  I ran into an undesirable (IMHO and yet unbuggy)
aspect of using image_maps, an aspect most likely in existence as far back
as 3.02.   I asked if there were a way around this and someone suggested the
object pattern. (an off-topic suggestion???)  It was a very useful idea, but
the suggestion did not (IIRC) contain the proper syntax for 0.7.   So I
suppose the topicality-hawks would have me stop the thread right there and
move it to p.u.p.,  but I think that's quite absurd.   I have respect for
the topicality of p.g. such that I would never ask, for example,  about
0.7's proximity pattern here, but contempt for topicality if the above
scenario is against server policy........



"W³odzimierz ABX Skiba" <abx### [at] babilonorg> wrote in message
news:om3ehug5fcmv929mar0ql8foialdpp5ud7@4ax.com...
> On Mon, 24 Jun 2002 08:18:06 -0400, "Greg M. Johnson"
<gregj:-)565### [at] aolcom>
> wrote:
> > If I'm using spheres or torii  in 0.7 and I have a question about the
> > syntax, should I post to p.u.-p.?
>
> Isn't syntax of box or torii already explained in documentation ? Are you
> asking about syntax or bug ? Chris Huff already pointed You that there is
> example file of object pattern - have You checked this ?
> http://users.skynet.be/smellenbergh/demopictures/obj_patternb.jpg
> http://users.skynet.be/smellenbergh/demopictures/obj_pattern.zip
>
> ABX

Post a reply to this message

On Mon, 24 Jun 2002 13:16:32 -0400, "Greg M. Johnson" <gregj:-)565### [at] aolcom>
wrote:
> I think that's quite absurd

I consider this just the opposite. I understand documentation of MegaPOV was
not as good as current 3.5 documentation (respect to the Ingo and all
cooperators). There were sample files with (usually) proper syntax. But You
quickly called your syntax problem as bug in tool. That's too much of
simplification and/or laziness. Moreover since it was no longer connected with
image_map problem at all it was NTG. I expressed my protest becouse I always
considered You very experienced user. I'm not the owner of the server or
member of any team but I don't like such customs when specialized groups are
designed. How new users can learn proper behaviours if experienced one starts
messing?

followup to off-topic

ABX

Post a reply to this message

On Mon, 24 Jun 2002 13:16:32 -0500, Greg M. Johnson wrote:


> While using MegaPov 0.7  I ran into an undesirable (IMHO and yet
> unbuggy) aspect of using image_maps, an aspect most likely in existence
> as far back as 3.02.   I asked if there were a way around this and
> someone suggested the object pattern. (an off-topic suggestion???)  It
> was a very useful idea, but the suggestion did not (IIRC) contain the
> proper syntax for 0.7.

The original suggestion by TinCanMan used the correct syntax, though it
had a separate typo that he immediately corrected. You tried using an
image_map as a color instead of a pigment, and kept dropping out the
necessary pigment{} blocks when using declared pigments, despite every
example using them. I even pointed you to an existing sample file...

Warp did mention pigment_map, but he was confused, and there were plenty
of other working examples given. I count 5 examples by the time you
declared that MegaPOV had a bug.

This whole thing has gone on too long, lets just end it here, please?


-- 
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: <chr### [at] tagpovrayorg>
WWW: http://homepage.mac.com/chrishuff/

Post a reply to this message