Hi Steven!

So I guess I have to elaborate, sorry for my short post the first time...
But really, actually I think the post wasn't too bad, because I think you
did everything right, only that you probably ran into a bug in Moray:

>At first I just assigned the halo and got nothing but a black
>sphere when i previewed it. I then added a solid color (white) pigment
>to it and made it 100% tranparent (I don't want to see the cylinder just
>the halo)

Correct, I forgot to mention that.

>and I get nothing at all when rendered. I've played around
>with the type, function, mapping and all the other attributes and so far
>can't even get a hint of a halo.


I guess you didn't change the density function. It seems that there is a bug
in Moray (I will notify Lutz anyway): The "constant" keyword does not get
exported to POV-Ray. If you define a halo with a density function other than
constant, you get your halo! If you need to use "constant", then it seems
that you have to hand-edit your code after export (I tried that and it
worked).

Hope this helps a little bit more!

Johannes.

Post a reply to this message

Thanks Johannes,

It works like a champ now. I thought I had tried everything but I guess I missed
that part.
Your help is GREATLY appreciated.

Thanks again, Steve.

Post a reply to this message

This thread is yet another that showes the great need for enhanced documentation.
Some of us need more examples, and more tips and tricks. Thank god we have Johannes
for now. Maby he could expand the docs and get a free registration! :)
Allan

Steven Kroeger wrote:

> Thanks Johannes,
>
> It works like a champ now. I thought I had tried everything but I guess I missed
> that part.
> Your help is GREATLY appreciated.
>
> Thanks again, Steve.

Post a reply to this message

Allan Middleton wrote in message <352B8033.26DA56CB@sonetis.com>...

>Maby he could expand the docs and get a free registration! :)

Too late :-) I have sent my registration to Munich even before the beta-test
was finished!

Anyway, I would have to dissapoint any hopes of me adding to the Moray docs,
because all my spare time is taken up with my own TreeDesigner project.

Greetings, Johannes.

Post a reply to this message

Hi Allan Middleton, you recently wrote in moray.win:

> This thread is yet another that showes the great need for enhanced documentation.
Well, part of the problem is to seperate where is it a POV-Ray problem
and where is it a Moray problem. Apart from the bug about constant not
being exported, it isn't really part of Moray's job to document how
halos work. But I do agree that a simple tutorial about creating one
would help here. Unfortunately there are only so many hours to a day
and so many things to do.

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

Post a reply to this message

Hello!

> > This thread is yet another that showes the great need for enhanced documentation.
> Well, part of the problem is to seperate where is it a POV-Ray problem
> and where is it a Moray problem. Apart from the bug about constant not
> being exported, it isn't really part of Moray's job to document how
> halos work.

100 % agree. Would be the same to force any company producing a compiler for a special
programming language to add a 'new user quick learn' tutorial to the language too.If
someone knows how to handle *.POV files by hand (or brain) and is able to read the PoV
docs, he/she will (of course) find some features not implemented in Moray, but never
ask for a good documentation.

> But I do agree that a simple tutorial about creating one
> would help here. Unfortunately there are only so many hours to a day
> and so many things to do.

:)Keep working on the next version.
The ones complaining about the missing docs are (most probably) not the ones buying
the

next update... ;)

BTW: Thanx for this one...

Post a reply to this message

Ingo Guenther wrote: <CUT>

> Would be the same to force any company producing a compiler for a special
> programming language to add a 'new user quick learn' tutorial to the language too.If
> someone knows how to handle *.POV files by hand (or brain) and is able to read the
PoV
> docs, he/she will (of course) find some features not implemented in Moray, but never
> ask for a good documentation.



> Some of us find the scripting language of POV counter-intuitive and are not
programmers
> but budding artists. This is where Moray comes in. It provides a 3D GUI that is much
more
> intuitive. I think that all great software deserves great documentation.

A note to Lutz: I realize that you are very busy right now and I would not hold up
progress
but please keep the docs in mind over the next few months/years.

>
>
>
>
> The ones complaining about the missing docs are (most probably) not the ones buying
the
>
> next update... ;)

I paid for version 2.5 , I paid for this version and I will pay for future upgrades.
Good
work deserves reward.

>
>
> BTW: Thanx for this one...

Right on!

Allan

Post a reply to this message

Learn something new every day, I do...!   And I always thought you programmer types
worked 24hrs a day, and only on software.  Don't tell me you *need* sleep!   :-)   
<g>

...larry




Lutz Kretzschmar wrote:

> (snip)
>  Unfortunately there are only so many hours to a day
> and so many things to do.
>

Post a reply to this message

Attachments:
Download 'us-ascii' (1 KB)

Hi Larry Bourdillon, you recently wrote in moray.win:

> Learn something new every day, I do...!   And I always thought 
> you programmer types worked 24hrs a day, and only on software. 
Well, we do program a lot, but unfortunately on 'real' contracts that
run on a deadline, not on Moray. I wish I could work full-time on
Moray, but it's not do-able.

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

Post a reply to this message

On Thu, 09 Apr 1998 20:09:40 -0400, Allan Middleton
<ami### [at] sonetiscom> wrote:

>
>
>Ingo Guenther wrote: <CUT>
>
>> Would be the same to force any company producing a compiler for a special
>> programming language to add a 'new user quick learn' tutorial to the language
too.If
>> someone knows how to handle *.POV files by hand (or brain) and is able to read the
PoV
>> docs, he/she will (of course) find some features not implemented in Moray, but
never
>> ask for a good documentation.
>

Hi Allan! Correct, Ingo Guenther wrote that.

>
>
>> Some of us find the scripting language of POV counter-intuitive and are not
programmers
>> but budding artists. This is where Moray comes in. It provides a 3D GUI that is
much more
>> intuitive. I think that all great software deserves great documentation.

Uhm, not correct, Ingo Guenther never wrote that. Look, if I had not
read Ingo Guenther's message, I would think now, he finds the
scripting language of POV counter-intuitive. But he will probably
strongly disagree on that assertion. So, if you cite more than one
person in a message, you should make it known, in that there are
a differnet number of preceding signs, like >>>. If you use Free Agent
for instance, this is done automatically, as the thread develops from
one message to the next. I find this habit, to cut and paste different
stages of a thread disturbing and misleading, it is a violation of
netiquette. If you must do it at all, precede cites from other persons
with a 'And xxx yyy said:' or something similar, and everything is
clear.

>
>A note to Lutz: I realize that you are very busy right now and I would not hold up
progress
>but please keep the docs in mind over the next few months/years.
>

snipped for bravity

>Allan
>
>

steff

Post a reply to this message