Welcome back, Nathan,

Nathan Kopp wrote:
> The default should be 3.1.  Do you have Version=3.0 in an ini file
> somewhere?  Otherwise, it might be a round-off error.

Ok, it seems the general consensus is round-off error. Just
to confirm: I've looked in all the INI files and found no older 
"Version=" statements, including the "root" POVRAY.INI (which 
contains no Version statement at all), so effectively if I pull 
the Version=3.1 out of my INI file, it should be the equivalent
of telling POV nothing at all about version.

> Just "#version 3.1;" will work.  The word "official" will disable the
> unofficial features, but if you don't use the word "official", then the
> unofficial features will remain activated.

Aha! I wondered what was up with the new keywords in the #version.
Not sure why anyone would want to disable the unofficial features
when the whole point of having an unoffical compile is playing with 
the unofficial features <vbg> but I see what you're getting at. :)
Thanks.

Charles

Post a reply to this message

Charles Fusner <cfu### [at] enternet> wrote...
>
> Aha! I wondered what was up with the new keywords in the #version.
> Not sure why anyone would want to disable the unofficial features
> when the whole point of having an unoffical compile is playing with
> the unofficial features <vbg> but I see what you're getting at. :)
> Thanks.

Sometimes people want to temporarily disable some changes, such as changes
to layered textures and normals.

-Nathan

Post a reply to this message

Chris Huff wrote in message ...
>In article <3897068A.7984E169@my-dejanews.com>,
>gre### [at] my-dejanewscom wrote:
>
>> I have used noise3d, however, in 0.3.  Was there some kind of change to
>> this function?
>
>I wrote a patch which allows it to be used in normal POV-Ray script,
>instead of only in isosurface functions.
>


Is there an example of that somewhere. It sounds really neat.

Gail
*******************************************************************
* gsh### [at] monotixcoza              * ERROR: COFFEE.COM not found  *
* http://www.rucus.ru.ac.za/~gail/ * Insert cup and press any key *
*******************************************************************
* Definition of an upgrade: Take the old bugs out, put new ones in*
*******************************************************************

Post a reply to this message

Hello Nathan,

I would be happy if you had the time to look into my problem with MegaPov
0.4. I was a little vague: I get the following message:
=================
  Warning Stream to console.......On
      translate 1000*x

      warp {turbulence Vary octaves 1}
      warp {planar z 0}
      warp {reset_children <----ERROR

C:\Program Files\POV-Ray\Include\\vloer.inc:15: error: This feature requires
MegaPov 0.3.
Specify '#version unofficial MegaPov 0.4;' IN THIS FILE to enable this
feature.


Returned from renderer (non-zero return value)
=================
The "vloer.inc" has the Ron Parker's inc with the irregular floor tiles. It
does OK in the 0.3 version.

I tried several #-statements in several places, but I am very unsure as how
this works and what to do.

0.3 suits me well, but why not use 0.4 if I can? (I have to include the
#version 3.1 at a certain spot to get my textures right: that I gathered
from earlier answers I got on the subject.

Thank you in advance,

--
Regards,
Sander


Nathan Kopp <Nat### [at] Koppcom> schreef in berichtnieuws
389745a7@news.povray.org...
>
> Sander <san### [at] stolscom> wrote...
> > Maybe I forget something, but the 'reset-children' feature doesn't work
> even
> > after adding the #version etc. line. What do I do wrong??
>
> What does 'not work' mean?  Do you get a #version-related error message,
or
> does it parse and then not function.
>
> -Nathan
>
>

Post a reply to this message

Nathan,

I was too quick for once! I just added "#version unofficial MegaPov 0.4" at
the beginning of the vloer.inc and it works!
But I don't understand it... What does it do? Why didn't I have to add
anything in MegaPov 0.3?

--
Regards,
Sander


Sander <san### [at] stolscom> schreef in berichtnieuws
389810d0@news.povray.org...
> Hello Nathan,
>
> I would be happy if you had the time to look into my problem with MegaPov
> 0.4. I was a little vague: I get the following message:
> =================
>   Warning Stream to console.......On
>       translate 1000*x
>
>       warp {turbulence Vary octaves 1}
>       warp {planar z 0}
>       warp {reset_children <----ERROR
<snip>

Post a reply to this message

In article <3898259f@news.povray.org> , "Sander" <san### [at] stolscom> wrote:

> But I don't understand it... What does it do? Why didn't I have to add
> anything in MegaPov 0.3?

The reason is simple: There have been several occasions when (new) users
tried to use unofficial features in the official version (i.e. isosurfaces)
from some POV scene code they got on the web or here in the newsgroups.
In general it is hard for (new) users who do not know which feature is
official and which is part of an unofficial version only to identify such a
problem.  Adding "#version unofficial" will on the one hand make the current
official version issue an error that "unofficial" is an undeclared
identifier with "#version unofficial <----ERROR", and future official
versions will issue a more helpful and explicit error message.


     Thorsten


____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

In article <qqm### [at] schlattfmiuni-konstanzde>, Thomas 
Willhalm <tho### [at] willhalmde> wrote:

> In frame.h it says:
>     #define CLOCKDIVIDER CLK_TCK /*provided by standard c? */	
> and as far as I know the answer is "No". According to the documentation
> available to me, you should use CLOCK_PER_SEC instead and include 
> <time.h>.

Actually, it is CLOCKS_PER_SEC. :-)
I don't know about whether it is standard or not, but I had to modify my 
compile to use it instead of CLK_TCK. It took a bit of searching through 
headers to find out about that annoying little "S".

-- 
Chris Huff
e-mail: chr### [at] yahoocom
Web page: http://chrishuff.dhs.org/

Post a reply to this message

Chris Huff <chr### [at] yahoocom> writes:

> In article <qqm### [at] schlattfmiuni-konstanzde>, Thomas 
> Willhalm <tho### [at] willhalmde> wrote:
> 
> > In frame.h it says:
> >     #define CLOCKDIVIDER CLK_TCK /*provided by standard c? */	
> > and as far as I know the answer is "No". According to the documentation
> > available to me, you should use CLOCK_PER_SEC instead and include 
> > <time.h>.
> 
> Actually, it is CLOCKS_PER_SEC. :-)
> I don't know about whether it is standard or not, but I had to modify my 
> compile to use it instead of CLK_TCK. It took a bit of searching through 
> headers to find out about that annoying little "S".

I'm sorry about wasting your time. I should have used copy'n'paste instead
of typing.

According to Plauger/Brodie "Standard C" CLOCKS_PER_SEC is standard. 
(Yes, I know that this book is from Microsoft Press, but let's assume
that their books contain less errors than their software.)

Thomas

-- 
http://thomas.willhalm.de/ (includes pgp key)

Post a reply to this message

In article <qqm### [at] schlattfmiuni-konstanzde>, Thomas 
Willhalm <tho### [at] willhalmde> wrote:

> I'm sorry about wasting your time. I should have used copy'n'paste 
> instead of typing.

No problem, it took me much less time to find that little typo than it 
would have taken for me to figure out why CLK_TCK wasn't defined 
anywhere.

-- 
Chris Huff
e-mail: chr### [at] yahoocom
Web page: http://chrishuff.dhs.org/

Post a reply to this message

Thomas Willhalm wrote:

> Chris Huff <chr### [at] yahoocom> writes:
>
> > In article <qqm### [at] schlattfmiuni-konstanzde>, Thomas
> > Willhalm <tho### [at] willhalmde> wrote:
> >
> > > In frame.h it says:
> > >     #define CLOCKDIVIDER CLK_TCK /*provided by standard c? */
> > > and as far as I know the answer is "No". According to the documentation
> > > available to me, you should use CLOCK_PER_SEC instead and include
> > > <time.h>.
> >
> > Actually, it is CLOCKS_PER_SEC. :-)
> > I don't know about whether it is standard or not, but I had to modify my
> > compile to use it instead of CLK_TCK. It took a bit of searching through
> > headers to find out about that annoying little "S".
>
> I'm sorry about wasting your time. I should have used copy'n'paste instead
> of typing.
>
> According to Plauger/Brodie "Standard C" CLOCKS_PER_SEC is standard.
> (Yes, I know that this book is from Microsoft Press, but let's assume
> that their books contain less errors than their software.)

According to the gcc time.h file, "CLK_TCK"  is "the obsolete POSIX.1-1988
name for the same constant" for "CLOCKS_PER_SEC"

And here's the bit of code they use:

/* This defines CLOCKS_PER_SEC, which is the number of processor clock
   ticks per second.  */
# include <bits/time.h>

/* This is the obsolete POSIX.1-1988 name for the same constant.  */
# ifdef __USE_POSIX
#  ifndef CLK_TCK
#   define CLK_TCK CLOCKS_PER_SEC
#  endif
# endif


--
"My new computer's got the clocks, it rocks
But it was obsolete before I opened the box" - W.A.Y.

Post a reply to this message