|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <cfsakv$2u2$1@chho.imagico.de> , Christoph Hormann
<chr### [at] gmxde> wrote:
> This of course not quite correct, the criterias which patches are
> included in MegaPOV are quite elaborate and the question if the author
> thinks the patch is ready has not much importance.
In old version of MegaPOV this certainly was a main criteria. Good to know
that it no longer is an important one.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
----- Original Message -----
From: "Christoph Hormann" <chr### [at] gmxde>
Newsgroups: povray.unofficial.patches,povray.general
Sent: Monday, August 16, 2004 11:06 PM
Subject: MegaPOV 1.1 beta
> You will see we also updated the website with a new sample scene gallery
> and some other useful information.
Thanks for the great stuff, I'm testing it right now (mingw Windows
version).
A couple of things I noticed after running most of the sample scenes:
- the post processing demos require missing "pprocess.inc"
- the hdr_environment.pov gives a parse error on clip_colors (undeclared
identifier)
G.
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Gilles Tran wrote:
>
> Thanks for the great stuff, I'm testing it right now (mingw Windows
> version).
>
> A couple of things I noticed after running most of the sample scenes:
> - the post processing demos require missing "pprocess.inc"
That seems to be only missing in the Windows package, i put it on:
http://megapov.inetart.net/pprocess.inc
> - the hdr_environment.pov gives a parse error on clip_colors (undeclared
> identifier)
I missed that, can be removed.
Thanks for mentioning.
Christoph
--
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 06 Jul. 2004 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 18 Aug 2004 00:36:24 +0200, "Gilles Tran" <gitran_nospam_@wanadoo.fr>
wrote:
> - the post processing demos require missing "pprocess.inc"
This file is in my copy of zip. It is a standard include file regarding
MegaPOV. This is something like functions.inc - definitions of the effects and
internal functions. So, do you have it?
> - the hdr_environment.pov gives a parse error on clip_colors (undeclared
> identifier)
Comment it temporary.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 18 Aug 2004 08:02:59 +0200, Christoph Hormann <chr### [at] gmxde>
wrote:
> > A couple of things I noticed after running most of the sample scenes:
> > - the post processing demos require missing "pprocess.inc"
>
> That seems to be only missing in the Windows package, i put it on:
> http://megapov.inetart.net/pprocess.inc
Thanks Chris but fresh download shows me that include\pprocess.inc is on it's
place.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
news:g1s5i0d9q33cqpoqa8csutp4fjiqe6b9lv@4ax.com...
> This file is in my copy of zip. It is a standard include file regarding
> MegaPOV. This is something like functions.inc - definitions of the effects
and
> internal functions. So, do you have it?
Sorry, my bad. It's indeed there but it's just that my povray.ini file had a
pointer to the 3.5 directory (and not 3.6)...
G.
--
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> ...And as a preventive answer to the FAQ "why was patch xxx not included in
> this version":
>
> Patch xxx was:
>
> - buggy
> - incomplete
> - published too late to be included
> - incompatible to POV-Ray 3.6
> - no one found the time to add it
> - did not appear useful
>
> (Of course not all together - select what you think fits best).
>
> Christoph
It's an excellent news ! I found megapov very impressive but... Where is the
finish_map patch that was included in mlpov 0.83 ? I don't think that patch
was:
- buggy
- incomplete
- published too late to be included
- incompatible to POV-Ray 3.6 (I don't really know)
- no one found the time to add it (Really ;-) or in beta 2 ??)
- did not appear useful (I don't think so...)
Also, you really made good job to maintain megapov (You and the "patchers")
I Hope megapov will continue to evolution like this trough the years... ;-))
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Wed, 18 Aug 2004 06:43:33 EDT, "LightBeam" <s.f### [at] tiscalifr> wrote:
> included in mlpov 0.83
AFAIK, mlpov was based on POV-Ray 3.5. Evolution from POV-Ray 3.5 to 3.6 was
mainly related to internal changes usually invisible to the end-user.
ABX
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
LightBeam wrote:
>
> It's an excellent news ! I found megapov very impressive but... Where is the
> finish_map patch that was included in mlpov 0.83 ? I don't think that patch
> was:
>
> - buggy
> - incomplete
> - published too late to be included
> - incompatible to POV-Ray 3.6 (I don't really know)
> - no one found the time to add it (Really ;-) or in beta 2 ??)
> - did not appear useful (I don't think so...)
Well - that one is difficult. When i had a look at it i found it quite
badly designed (or at least unusual). The syntax was not easy to use
and misleading - specifying functions instead of floats without a
wrapping function{} is not a good idea (*). Also i think Mael
considered it incomplete - he wanted to add support for anisotropic
finishes IIRC.
In fact 'finish map' is a misleading name - a finish map would be
something like:
texture {
pigment { ... }
finish {
bozo
finish_map {
[0 Fin_1][1 Fin_2]
}
}
}
(*) if it is nor clear what i mean imagine the following variation of
the sample in the MlPOV manual:
#declare fct = function { pigment { checker color rgb 0 color rgb 1
scale .1 } }
sphere { ...
finish {
uv_mapping
reflection { fct (1) }
}
Should that be an incorrect call to function fct() or a function based
reflection minimum and a constant reflection maximum?
Christoph
--
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 06 Jul. 2004 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
First of all, the new features are really nice!
Thanks to the MegaPOV-Team for this release.
Especially the easy interface of the custom-radiosity-samples-patch gave me
an impulse to play around with candidates with good cos-theta-distributions.
At the moment i'm making test-renderings to compare them with the internal
sample-set. I think they are promising and i will make them available on a
webpage soon to get feedback from you.
Additionally, i have two questions:
POV-Ray creates a 'memory.log'-file when i render an image, which grows
quite rapidly and contains many lines like:
File:source/blob.cpp Line:2212 Size:4
File:source/blob.cpp Line:3445 Size:64
File:source/blob.cpp Line:2212 Size:4
File:source/blob.cpp Line:2273 Size:4
Are these memory-leaks, or just some kind of 'routine' logging?
And, the documentation (2.7.2.2.2.) says:
'A number of sample direction sets is coming with MegaPOV as include files.'
I'm just curious if they aren't ready yet in the beta or if they were
forgotten?
Greetings,
Thies Heidecke
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |