I downloaded the documentation file that came with Plus 0.3.2, but there
is only Particle syntax
Is there any were I can get it for the glow.
none of the scene files I down loaded or the Demo's work, they give
error message
glow{1
      <------error
        error: No matching } in glow, float function 'float constant'
found

Thanks Brian
-- 
Southern Cross Akitas (SCA)
Lois & Brian Bivolcic
Pampa, Tx
http://www.centramedia.com/bivolcic

Post a reply to this message

hello!  anybody home?!?  read ALL of the document files.  there are
FOUR. 
this question has been asked and answered several times already.  you
can do searches in these newsgroups.  it's quite handy.  that's the
entire reason these messages are all kept.

Brian & Lois Bivolcic wrote:
> 
> I downloaded the documentation file that came with Plus 0.3.2, but there
> is only Particle syntax
> Is there any were I can get it for the glow.
> none of the scene files I down loaded or the Demo's work, they give
> error message
> glow{1
>       <------error
>         error: No matching } in glow, float function 'float constant'
> found
> 
> Thanks Brian
> --
> Southern Cross Akitas (SCA)
> Lois & Brian Bivolcic
> Pampa, Tx
> http://www.centramedia.com/bivolcic

Post a reply to this message

In article <39CC19F7.CE7BFEA2@popampa.com>, Brian & Lois Bivolcic 
<biv### [at] popampacom> wrote:

> I downloaded the documentation file that came with Plus 0.3.2, but there
> is only Particle syntax
> Is there any were I can get it for the glow.
> none of the scene files I down loaded or the Demo's work, they give
> error message

The syntax has changed in the more recent versions. The new syntax is 
explained in the documentation, but new files are not yet available(I am 
working on redesigning that portion of the web site).

-- 
Christopher James Huff
Personal: chr### [at] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/

<><

Post a reply to this message

> I downloaded the documentation file that came with Plus 0.3.2, but there
> is only Particle syntax

You need MegaPOVPlusDocs032.zip, there a file called 'Documentation' in
there that explains it. The demo scenes are currently for 0.3, not 0.3.2, so
the glow ones won't work because the syntax changed, and I think some of the
particle system ones had errors in them too.

Post a reply to this message

On Sat, 23 Sep 2000 06:06:42 -0500, Chris Huff wrote:
>In article <39CC19F7.CE7BFEA2@popampa.com>, Brian & Lois Bivolcic 
><biv### [at] popampacom> wrote:
>
>> I downloaded the documentation file that came with Plus 0.3.2, but there
>> is only Particle syntax
>> Is there any were I can get it for the glow.
>> none of the scene files I down loaded or the Demo's work, they give
>> error message
>
>The syntax has changed in the more recent versions. The new syntax is 
>explained in the documentation, but new files are not yet available(I am 
>working on redesigning that portion of the web site).

The file called 'Documentation' looks like this:

MacMegaPOV+ 0.5a mod 0.3.1^M^MNew directives:^M^M#set^M#set VAR_NAME = NEW_VALUE
|;|^MThis
 keyword modifies local or global variables, but produces an error if given a variable
nam
e that doesn't exist yet. It's purpose is to replace #declare and #local in those
areas wh
ere you are not creating a new variable, but modifying an existing one. The goal is to
inc
rease code readability and catch bugs due to typos in the name of the variable being
modif
ied.(since #set will produce an error, but #declare or #local would produce a new
variable
 with that name, with potentially disasterous results, like infinite loops). The rules
for
 when to use the trailing semicolon (;) are the same as for #declare and #local.^MI
have g
otten some strange results where under some conditions, using a macro will seem to put
"#"
 characters in the scene code. I am not sure this is the fault of the #set patch
though, a
nd I don't see how it could be the cause...it might be a problem with the fast macro
patch
. Fortunately, the only situation I encountered this in was quite easy to work
around.^M^M
New atmospheric effects:^M^MGlow effect:^Mglow {^M      location LOCATION^M     size
FLOAT
_SIZE^M radius FLOAT_RADIUS^M   color COLOR^M   fade_power FLOAT_POWER^M        type
|0|1|
2|3|^M  WARPS^M TRANSFORMS^M}^MThis makes a fast-rendering glow effect. It is based on
the
 light source glow effect from POV-AFX, written by Marcos Fajardo, but has been
heavily mo
dified. You can specify glows individually, or attached to a light_source. If crea

Thanks Chris,  so easy to read,  why doesn't all documentation come in this format?

And in the Demo Scenes zip all the filenames and directory names with spaces in them
were cool aswell.

Guess I'll be using my old version of Mega for some time yet. 

-- 
Cheers
Steve              email mailto:ste### [at] zeroppsuklinuxnet

%HAV-A-NICEDAY Error not enough coffee  0 pps. 

web http://www.zeropps.uklinux.net/

or  http://start.at/zero-pps

  3:14pm  up 53 days, 17:38,  2 users,  load average: 1.09, 1.04, 1.01

Post a reply to this message

On 3 Dec 2000 10:17:43 -0500, Steve wrote:

>Thanks Chris,  so easy to read,  why doesn't all documentation come in this format?
>
>And in the Demo Scenes zip all the filenames and directory names with spaces in them
>were cool aswell.

Actually I take some of that back, it's not to bad in emacs, but the lines
don't seem to have breaks, but I can wrap them.  

Maybe I'll have a go after all. 

-- 
Cheers
Steve              email mailto:ste### [at] zeroppsuklinuxnet

%HAV-A-NICEDAY Error not enough coffee  0 pps. 

web http://www.zeropps.uklinux.net/

or  http://start.at/zero-pps

  5:44pm  up 53 days, 20:08,  2 users,  load average: 1.15, 1.08, 1.02

Post a reply to this message

In article <slr### [at] zero-ppslocaldomain>, 
ste### [at] zeroppsuklinuxnet wrote:

> Actually I take some of that back, it's not to bad in emacs, but the 
> lines don't seem to have breaks, but I can wrap them.  

Looks like I forgot to convert the line-returns again...maybe I will 
just HTMLize the docs so I don't have to worry about it any more.
Actually, that's going to happen anyway...whenever I get to work on my 
web site.

-- 
Christopher James Huff
Personal: chr### [at] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/

<><

Post a reply to this message

Steve wrote:
> 
> 
> Actually I take some of that back, it's not to bad in emacs, but the lines
> don't seem to have breaks, but I can wrap them.
> 
> Maybe I'll have a go after all.
> 
	Try ccp to convert text files ( http://www.inp.nsk.su/~grozin/ccp/ )


-- 

* Abandon the search for truth, * mailto:ber### [at] inamecom
* Settle for a good fantasy.    * http://www.enst.fr/~jberger
*********************************

Post a reply to this message