Lutz Kretzschmar <lut### [at] stmuccom> wrote:
> Hi ryan constantine, you recently wrote in moray.win:

>> and a udo only has to be an approximation of the actual inc object,
>> right?  so if one made an isosurface planet, a udo of a sphere would
>> suffice.
> Yes. You can define anything in a UDO. It doesn't need to have
> anything to do with the actual thing that POV-Ray will render.

Hmm, speaking of which, I've noticed a bug.  When I create a UDO that I
built by hand (I don't know if this is a problem with machine generated
UDOs), the *first* one (which I create using the toolbar) is fine.  When I
copy it, the vectors between points get munged, connecting the wrong points. 
It renders fine, of course, so this hasn't been a big problem (actually been
helpful, since the munged udo are easier to work around without changing the
screen detail level).  Is there someone who can look at my .udo file and
tell me what's wrong with it, or if the problem is in Moray?

Geoff

-- File Below ---

Name 'Rail'

;Specify the file that should be included to access this object
IncludeFile 'Rail.INC'


[Rail:Vertices]
8
 0.2,  0.2,  0.0
-0.2,  0.2,  0.0
-0.2, -0.2,  0.0
 0.2, -0.2,  0.0
 0.2,  0.2,  3.0
-0.2,  0.2,  3.0
-0.2, -0.2,  3.0
 0.2, -0.2,  3.0


[Rail:Edges]
12
0 1
1 2
2 3
3 0
4 5
5 6
6 7
7 4
0 4
1 5
2 6
3 7

[End]

Post a reply to this message