![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From
ftp://ftp.povray.org/pub/povray/Old-Versions/Official-3.0/news.3.01.txt
> There are other changes planed for 3.1 that we are sure you will
> appreciate and they will not hurt backward compatibility. We are not
> yet ready say what new features will be added for 3.1 but we will try
> to keep the list short for this minor upgrade. In parallel with 3.1
> work we are going to start development on 4.0 which will probably involve
> a total revision of the code from C to C++. Don't look for that release
> until 1998 or later.
Ahh, remember 3.0, back in the days of Halo and Atmosphere. Back when
POVRay still had a DOS release. Those were such optimistic times!
It seems like 3.7 has been in beta for years, but I read this paragraph
and chuckled a bit.
"Don't look for that release until 1998 or later."
LOL, it's been more than 10 years, and POV-Ray 4.0 is no where near even
existing!
Not slamming the team at all ;) But I found this amusing ...
--
~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Mike Raiford" <"m[raiford]!at"@gmail.com> wrote in message
news:4a8c27ec@news.povray.org...
> "Don't look for that release until 1998 or later."
>
> LOL, it's been more than 10 years, and POV-Ray 4.0 is no where near even
> existing!
>
> Not slamming the team at all ;) But I found this amusing ...
Duration of the time period between releases, which is constant with
commercial software, tends to follow arithmetic or even geometric,
exponential or divergent (which is to say, the project is abandoned)
progression for free/OS software.
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Mike Raiford schrieb:
> It seems like 3.7 has been in beta for years, but I read this paragraph
> and chuckled a bit.
That's not how it /seems/, that's how it /is/ :P
But they were right, weren't they? :P
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
clipka wrote:
> Mike Raiford schrieb:
>> It seems like 3.7 has been in beta for years, but I read this
>> paragraph and chuckled a bit.
>
> That's not how it /seems/, that's how it /is/ :P
>
> But they were right, weren't they? :P
Indeed. :)
--
~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Mike Raiford wrote:
> From
> ftp://ftp.povray.org/pub/povray/Old-Versions/Official-3.0/news.3.01.txt
>
>> There are other changes planed for 3.1 that we are sure you will
>> appreciate and they will not hurt backward compatibility. We are not
>> yet ready say what new features will be added for 3.1 but we will try
>> to keep the list short for this minor upgrade. In parallel with 3.1
>> work we are going to start development on 4.0 which will probably involve
>> a total revision of the code from C to C++. Don't look for that release
>> until 1998 or later.
>
> Ahh, remember 3.0, back in the days of Halo and Atmosphere. Back when
> POVRay still had a DOS release. Those were such optimistic times!
>
I found a website that archived old CD distributions of even older BBS
software sites. Digging through some of them, there was DKBTrace 2.12
and POV-Ray 1.0 for the A4000. The source code was so compact back then!
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Sabrina Kilian wrote:
> I found a website that archived old CD distributions of even older BBS
> software sites. Digging through some of them, there was DKBTrace 2.12
> and POV-Ray 1.0 for the A4000. The source code was so compact back then!
Hehe, my first encounter with Pov-Ray was when it was known as PVRay, it
was a beta version, 0.9b. It prompted me to write a program that would
basically stripe R G and B on the screen, so I could see the images in
their full color. I eventually found a paint program that would convert
TGA to GIF, then eventually begged my dad for an ET4000-based card with
24 bit color. I remember waiting hours on my 386-SX for sunset.pov to
complete, Suffice to say, SKYVASE took a loooong time to trace.
--
~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Mike Raiford <"m[raiford]!at"@gmail.com> wrote:
> I remember waiting hours on my 386-SX for sunset.pov to
> complete, Suffice to say, SKYVASE took a loooong time to trace.
I love this comment in scenes/advanced/piece3/piece3.pov:
// Due to the large number of objects, you will probably have to
// have a lot of memory to render this scene.
// Rendering time using a 25Mhz 386 w/Cyrix fpu is approximately 60 hours.
I don't know what resolution that's speaking about, but with my
current computer it only takes a few seconds to render at 1024x768
with antialiasing.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp wrote:
> I don't know what resolution that's speaking about, but with my
> current computer it only takes a few seconds to render at 1024x768
> with antialiasing.
>
I never owned a 386, but my 286 came with an CGA (320x200) monitor and
my 486 came with an SVGA (800x600) monitor.
-Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Remember the "Hold-and-Modify" mode of the Amiga? Remind me, did PovRay make
use of it, back then?
(For the young ones out here: http://en.wikipedia.org/wiki/Hold_And_Modify )
"Mike Raiford" <"m[raiford]!at"@gmail.com> schrieb im Newsbeitrag
news:4a8c57fb@news.povray.org...
> Sabrina Kilian wrote:
>
>> I found a website that archived old CD distributions of even older BBS
>> software sites. Digging through some of them, there was DKBTrace 2.12
>> and POV-Ray 1.0 for the A4000. The source code was so compact back then!
>
> Hehe, my first encounter with Pov-Ray was when it was known as PVRay, it
> was a beta version, 0.9b. It prompted me to write a program that would
> basically stripe R G and B on the screen, so I could see the images in
> their full color. I eventually found a paint program that would convert
> TGA to GIF, then eventually begged my dad for an ET4000-based card with 24
> bit color. I remember waiting hours on my 386-SX for sunset.pov to
> complete, Suffice to say, SKYVASE took a loooong time to trace.
>
> --
> ~Mike
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
TC wrote:
> Remember the "Hold-and-Modify" mode of the Amiga? Remind me, did PovRay make
> use of it, back then?
Off the top of my head... no.
I think it could show the preview in 256 colour mode, but all output
files were basically 24-bit colour, and you had to use a 3rd party
program to convert this to something the Amiga's hardware could display.
(DPaint will do it quite happily - except that I'm not 100% sure POV-Ray
supported IFF ILBM. Might have been only TARGA or something - in which
case you'd need PPaint.)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |