Ok, I'm getting some strange things happening with UDO/INC files.

(yes, I know how UDOs work.. )

I use Elefont to make bevelled text, and now, in moray, the wireframe is
wrong. The bevel is an indentation sideways like so:  (excuse the crappy
ascii art)
_____
)____(

instead of
 _____
(_____)

and here's the real stumper...

the RENDERED image MATCHES this. The rendered text is indented in the SAME
way.

Note: Elefont doesn't do indentation...

If you like, I can send a sample set that does this..

Twyst

Post a reply to this message

As well as several other UDO/INC problems. I have done several tests, now
posted on comp.graphics.rendering.raytracing, and they problem, oddly enough,
seems to be that of a normal map or something.

Twyst wrote:

> Ok, I'm getting some strange things happening with UDO/INC files.
>
> (yes, I know how UDOs work.. )
>
> I use Elefont to make bevelled text, and now, in moray, the wireframe is
> wrong. The bevel is an indentation sideways like so:  (excuse the crappy
> ascii art)
> _____
> )____(
>
> instead of
>  _____
> (_____)
>
> and here's the real stumper...
>
> the RENDERED image MATCHES this. The rendered text is indented in the SAME
> way.
>
> Note: Elefont doesn't do indentation...
>
> If you like, I can send a sample set that does this..
>
> Twyst



--
"Only after the last tree has been cut down. Only after the last river has
been poisoned. Only after the last fish has been caught. Only then will you
find that money cannot be eaten."- Cree Indian Prophecy

Post a reply to this message

Hi Alex Magidow, you recently wrote in moray.win:

> As well as several other UDO/INC problems. I have done several tests, now
> posted on comp.graphics.rendering.raytracing, and they problem, oddly enough,
> seems to be that of a normal map or something.
A Normal map? That can't possibly be influencing the wireframe
display. Are you texturing the UDO objects or are you using the
default texture? Unfortunately the release contains a MORAYPOV.INC
that defines the default texture to be red and bumpy.

- Lutz
  email : lut### [at] stmuccom
  Web   : http://www.stmuc.com/moray

Post a reply to this message

Lutz Kretzschmar wrote in message <368### [at] 194174214110>...
>Hi Alex Magidow, you recently wrote in moray.win:

<snip>
>default texture? Unfortunately the release contains a MORAYPOV.INC
>that defines the default texture to be red and bumpy.
<snip>


Yeah, it took me ages to figure out why my checker-board was bumpy ;)

Matt

Post a reply to this message

I couldn't tell anything about the wireframe- too many triangles. But the image is
textured with teh aluminum texture from the libraries, which has no normal mapping.
However, the effect is much like that of a normal map.

In response to the comma thingy, would that make it so that the object was
enormouse when imported into moray? Because, just to make the helixes a mangable
size, I had to u-scale them down to .35 of their normal size.

Lutz Kretzschmar wrote:

> Hi Alex Magidow, you recently wrote in moray.win:
>
> > As well as several other UDO/INC problems. I have done several tests, now
> > posted on comp.graphics.rendering.raytracing, and they problem, oddly enough,
> > seems to be that of a normal map or something.
> A Normal map? That can't possibly be influencing the wireframe
> display. Are you texturing the UDO objects or are you using the
> default texture? Unfortunately the release contains a MORAYPOV.INC
> that defines the default texture to be red and bumpy.
>
> - Lutz
>   email : lut### [at] stmuccom
>   Web   : http://www.stmuc.com/moray



--
"Only after the last tree has been cut down. Only after the last river has
been poisoned. Only after the last fish has been caught. Only then will you
find that money cannot be eaten."- Cree Indian Prophecy

Post a reply to this message

Hi Alex Magidow, you recently wrote in moray.win:

> I couldn't tell anything about the wireframe- too many triangles. But the image is
> textured with teh aluminum texture from the libraries, which has no normal mapping.
> However, the effect is much like that of a normal map.
Maybe try texturing it with a new texture that has a Solid Color
Pigment.

> In response to the comma thingy, would that make it so that the object was
> enormouse when imported into moray? 
No, the basic size shouldn't change.

> Because, just to make the helixes a mangable size, 
> I had to u-scale them down to .35 of their normal size.
Well, there really isn't such a thing as 'normal size'. You can create
huge objects and tiny objects.
 
- Lutz
  email : lut### [at] stmuccom
  Web   : http://www.stmuc.com/moray

Post a reply to this message

Twyst wrote:

> Ok, I'm getting some strange things happening with UDO/INC files.
>
> (yes, I know how UDOs work.. )
>
> I use Elefont to make bevelled text, and now, in moray, the wireframe is
> wrong. The bevel is an indentation sideways like so:  (excuse the crappy
> ascii art)
> _____
> )____(
>
> instead of
>  _____
> (_____)
>
> and here's the real stumper...
>
> the RENDERED image MATCHES this. The rendered text is indented in the SAME
> way.
>
> Note: Elefont doesn't do indentation...

I've gotton the exact same problem, many times. (I do a lot of text graphics
:)

I think it is a problem in Elefont, not necessarily Moray, but I don't know
what the problem is, or how to reproduce it. Usually, though, if I go back
into Elefont, start from scratch, and re-export, the result is fine. It's an
oddity for sure, though....

Simon
http://home.istar.ca/~sdevet

Post a reply to this message

Simon de Vet wrote:

> I've gotton the exact same problem, many times. (I do a lot of text graphics
> :)
>
> I think it is a problem in Elefont, not necessarily Moray, but I don't know
> what the problem is, or how to reproduce it. Usually, though, if I go back
> into Elefont, start from scratch, and re-export, the result is fine. It's an
> oddity for sure, though....
>
> Simon
> http://home.istar.ca/~sdevet

I remember a discussion some time ago concerning problems
with the way elepont exports. There is a recognized bug in
the program and the next build promises to fix this. I just can't
seem to remember what the bug was. I do seem to recall that
Dan Connely was involved in this discussion if that helps.
--
Ken Tyler

tyl### [at] pacbellnet

Post a reply to this message