POV-Ray : Newsgroups : povray.general : POVRAY 3.6 features Server Time
2 Nov 2024 17:19:59 EDT (-0400)
  POVRAY 3.6 features (Message 1 to 6 of 6)  
From: laurent artaud[AT]free fr
Subject: POVRAY 3.6 features
Date: 25 Jan 2004 10:47:07
Message: <4013e4fb$1@news.povray.org>
Hello.

I was looking for POVRay 3.6 features but I can't find any.

Drolling before the characteristics this new version will offer may help 
me wait for it... (I hope...)

Can anyone tell me where to find them?

Thanks.


Post a reply to this message

From: Ken
Subject: Re: POVRAY 3.6 features
Date: 25 Jan 2004 11:07:01
Message: <4013E9C5.EB8B05D6@pacbell.net>
"laurent.artaud[AT]free.fr" wrote:
> 
> Hello.
> 
> I was looking for POVRay 3.6 features but I can't find any.
> 
> Drolling before the characteristics this new version will offer may help
> me wait for it... (I hope...)
> 
> Can anyone tell me where to find them?

They have not yet been made publically available. The vast majority of
changes are internal and will not be visible to the user. In fact, the
only major feature upgrade is added support for UV mapping. The rest are
bug fixes, speed improvements, image handling and major changes in the
generation of the documentation which will allow printing. A full change
list will not be released. A list of changes effecting the users of
POV-Ray will be made available as soon as we get time to compile it
and all supported platform beta versions are ready for release.

Hope I don't get in trouble for saying this much...

-- 
Ken Tyler


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: POVRAY 3.6 features
Date: 25 Jan 2004 11:17:31
Message: <4013ec1b@news.povray.org>
In article <4013e4fb$1@news.povray.org> , "laurent.artaud[AT]free.fr" 
<"laurent.artaud[AT]free.fr"> wrote:

> Drolling before the characteristics this new version will offer may help
> me wait for it... (I hope...)
>
> Can anyone tell me where to find them?

Read the status update, it tells you that you cannot find them because they
are not available at this time.

    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

From: Tim Cook
Subject: Re: POVRAY 3.6 features
Date: 25 Jan 2004 12:18:02
Message: <4013fa4a@news.povray.org>
laurent.artaud[AT]free.fr wrote:
> I was looking for POVRay 3.6 features but I can't find any.

Actually, there aren't any changes, it's just a marketing ploy.
All they did was change internal variable names.  ;)


Post a reply to this message

From: ABX
Subject: Re: POVRAY 3.6 features
Date: 26 Jan 2004 03:38:55
Message: <b6k910900b84proaau6g9l94qocd5o4vh8@4ax.com>
On Sun, 25 Jan 2004 12:18:14 -0500, Tim Cook <z99### [at] bellsouthnet> wrote:
> > I was looking for POVRay 3.6 features but I can't find any.
>
> Actually, there aren't any changes, it's just a marketing ploy.
> All they did was change internal variable names.  ;)

Of course, profits are doubled thanks to releasing the same product with
different version number ;) Next, sixth edition of PDF documentation will be
released to those who subscribed with working credit card numbers ;) ;)

ABX


Post a reply to this message

From: Patrick Elliott
Subject: Re: POVRAY 3.6 features
Date: 26 Jan 2004 14:05:14
Message: <MPG.1a7f1211a177c0ff989982@news.povray.org>
In article <b6k910900b84proaau6g9l94qocd5o4vh8@4ax.com>, abx### [at] abxartpl 
says...
> On Sun, 25 Jan 2004 12:18:14 -0500, Tim Cook <z99### [at] bellsouthnet> wrote:
> > > I was looking for POVRay 3.6 features but I can't find any.
> >
> > Actually, there aren't any changes, it's just a marketing ploy.
> > All they did was change internal variable names.  ;)
> 
> Of course, profits are doubled thanks to releasing the same product with
> different version number ;) Next, sixth edition of PDF documentation will be
> released to those who subscribed with working credit card numbers ;) ;)
> 
> ABX
> 
Hmm.. So, which version is going to be the one that rearranges all the 
page boundaries and entry points so it breaks integration with most 
plugins and stops all user designed patches from working correctly with 
the new version? (like with Windows 95 and OS/2) ;)

-- 
void main () {

    call functional_code()
  else
    call crash_windows();
}


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.