POV-Ray : Newsgroups : moray.win : POV errors out of Moray : Re: POV errors out of Moray Server Time
28 Jul 2024 18:25:56 EDT (-0400)
  Re: POV errors out of Moray  
From: Charles Fusner
Date: 13 Mar 2000 20:52:39
Message: <38CD9BCE.D3953FB1@enter.net>
Pascal Golay wrote:
> 
> On Mon, 13 Mar 2000 03:14:40 GMT, lut### [at] stmuccom (Lutz Kretzschmar) wrote:
> > Hi Pascal Golay, you recently wrote in moray.win:
> >
> > > Objects built by me in Rhino and exported as obj
> > > and then 3dWin-ed into Moray 3.2 seem to work fine so far.
> > Rhino can export directly to Moray via the UDO/INC export option.
> >
> Yes indeedy, but since I mostly render with NuGraf (at least until I get the hang of
this Moray/POV  approach) I send the geometry out as obj and this way I can use either

Regardless of what you render in, POV-Ray still doesn't import OBJ files
directly so whether you export them directly from Rhino in UDO/INC or
export them as OBJ and use 3DWin to convert them to UDO/INC you'll have
the same number of files laying around. Nothing saved there. And
meanwhile, I have had ocassions where 3DWin kind of mangles names
of components during the conversion process: I looked in the UDO
and corresponding INC files and found it had numerous naming errors
that had to be hand corrected. Looked like the conversion process
wasn't properly clearing the string that held the name before 
readinging in the next section.  You should at least try exporting 
directly from Rhino (same model) and see if it solves the problem, 
because it does seem to be an intermittant problem with 3DWin sometimes. 
I had the most trouble with 3DS files, actually, and OBJ files worked 
fine for me but... who knows? That could be the problem.

Another, simpler thing to check is to make sure your INC file is in 
the same directory with your scene source. I don't believe the 
references in the UDO include a pathname, so if the INC file isn't 
where POV knows to look for it, the problem could also be that it
never actually defined the object "Legs" before the UDO export 
attempted to reference it. 

>The second thing I'd like to get straight is how Moray/POV uses image mapping-  So
far it
>looks as though POV cuts off anything on an object that is not covered by the image 
>map- if I scale it for example on the face of an imported cube, only the part of the
cube
>under the scaled image shows, even with another layer of plain solid color below the 
>image map. How would one, for example, pace a rectangular label on the middle of a
face of a
>box? Could noe move it around to see how it looks in different places? Sorry if i'm 
>being dense, thanks for any info...

Yes, if you have "Once" checked off (as you would if you wanted it to
look like a label) you'll find that everything that isn't under 
the label has no texture, therefore, of course you don't see it.
To make a layered texture with the image map on top, make sure your
texture listing (on the left hand side of the material editor) 
looks something like this in structure...

Material
  |
  Layered Texture
    |
    Standard Texture
    |  |
    |  pigment
    |    |
    |    solid color (and make sure the solid color you pick doesn't
    |                 match your background color, of course)
    |                 
    |
    Standard Texture
       |
       pigment
         |
         image_map


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.