Jim Charter wrote:

> Now my personal sentiments are more aligned with Warp's.  There is an 
> intuitive purity to drawing the line at single-pass rendering with a ray 
> tracer, using the ray tracer only, with no post-processing.

Despite everything I posted to the contrary, I fully agree
with that. But I think that's the viewpoint of us people drawn
in from the technical side. If I wanted to make a great digital
image I would buy a camera ;) the fascinating part for me is
that you get results from some code snippets. But it would
just hamper the artists.

Maybe the IRTC should allow tagging a submission as "purist".
That would be restricted to images created using an officially
released version of a raytracer, using pure code, no modeller,
no external data files, no image maps, no multipass renders, and
of course absolutely no post-processing except jpg conversion.
Source code would be mandatory for purist images and the highest
ranking purist image gets an honorable mention ;)

Post a reply to this message

Hildur K. wrote:
> The bottom line is that people using Povray should be very eager to change the

> many of advanced processes almost demand you to have a supercomputer.  Give


You don't need a supercomputer, you just need a few spare weeks to render :)

-- 
Chambers

Post a reply to this message

"Christian Froeschlin" <chr### [at] chrfrde> schreef in bericht 
news:4a396d14$1@news.povray.org...
> Maybe the IRTC should allow tagging a submission as "purist".
> That would be restricted to images created using an officially
> released version of a raytracer, using pure code, no modeller,
> no external data files, no image maps, no multipass renders, and
> of course absolutely no post-processing except jpg conversion.
> Source code would be mandatory for purist images and the highest
> ranking purist image gets an honorable mention ;)

LOL!

Thomas

Post a reply to this message

Christian Froeschlin <chr### [at] chrfrde> wrote:
> Maybe the IRTC should allow tagging a submission as "purist".
> That would be restricted to images created using an officially
> released version of a raytracer, using pure code, no modeller,
> no external data files, no image maps, no multipass renders, and
> of course absolutely no post-processing except jpg conversion.
> Source code would be mandatory for purist images and the highest
> ranking purist image gets an honorable mention ;)

Now that's an idea I like! I too have always been most enthused by the idea of
'pure' code generating a beautiful image, and I often design scenes with this
philosophy. (I wonder, could my meshrelief macros be used to generate .inc
files for this scenario? It is a multi-parse, if not a multi-pass render...)

I don't necessarily think this idea should be implemented, but I like it ;-)

Post a reply to this message

"Gilles Tran" <gil### [at] gmailcom> wrote in message 
news:4a39217e@news.povray.org...

| news:4a391791@news.povray.org...
| > Gilles,
| >
| > Which 'open source'/freeware renderers best represent your 
description
| > of  a post ray tracing software ?
|
| Indigo, Kerkythea, LuxRender for instance. There's also Yafaray, which 
is a
| "reboot" of Yafray. It's described as a raytracer but supports other
| rendering algorithms. Of course POV-Ray itself is also "post 
raytracing"
| since it supports GI and photon mapping.
|
| G.
|

Indigo went commercial after 1.18
Can't see the price as their 'buy' link fails.

Kerkythea probably won't get much attention as the
develioers niw have a commercial business.
Looks like October 2008 was the last update.


LuxRender seems fairly young along the development
road.

Isn't Yafaray part of Blender now?

Post a reply to this message

Christian Froeschlin <chr### [at] chrfrde> wrote:
> Maybe the IRTC should allow tagging a submission as "purist".
> That would be restricted to images created using an officially
> released version of a raytracer, using pure code, no modeller,

Hmm... what if that particular raytracer had an integrated modeller??

And what would stop me from modelling a mesh in Wings3D, exporting it,
reformating it, and claiming that I'd hacked That Mesh2 Code up myself? Who the
* could tell (or rather, prove)?


> no external data files, no image maps, no multipass renders, and
> of course absolutely no post-processing except jpg conversion.
> Source code would be mandatory for purist images and the highest
> ranking purist image gets an honorable mention ;)

Yeah, but bloody likely nothing more than that :P

Post a reply to this message

"clipka" <nomail@nomail> wrote:

> > no external data files, no image maps, no multipass renders, and
> > of course absolutely no post-processing except jpg conversion.
> > Source code would be mandatory for purist images and the highest
> > ranking purist image gets an honorable mention ;)
>
> Yeah, but bloody likely nothing more than that :P

Couple of days ago I took a quick took: the top 10 winners of the IRTC used
various tools to generate their images in their many submissions. Here is a
list of the main software used by these successful participants (macros are not
listed here).

Povray
BMRT
3ds Max
Mental Ray
Arboretum Forester
Blender
MakeHuman
Plant Studio
Megapov
mlPov
Hamapatch
Leveller
Poser
Amapi
Autocad
Texture Magic
Terragen
Win 3d
Crossroads
Wings 3D
Rhino 3D
Spatch
Paintshop Pro
DazStudio
Photoshop
World Machine
3d studio
Moray
Illustrator
bCad
Gforge
Blob Sculptor
HF-Lab
ZBrush
The Gimp
UniMegaPov
Poseray
Xfrog
Tree Professional
Quick 3D
Clothray
Corel Photo Paint
Corel Draw
PovMan
RibTickler
Picture Publisher
Pov tree
UV mapper
Meshcomp
Arbaro
Kwrite

I only checked ten people, there is probably much more.



Hildur

Post a reply to this message

Christian Froeschlin <chr### [at] chrfrde> wrote:
> Allow change C:Image->Image if there exists f:RGB->RGB
> with f(I(x,y))) = C(I)(x,y) for each location (x,y)?

  You could do anything with such a function, such as draw lines, etc.

-- 
                                                          - Warp

Post a reply to this message

Christian Froeschlin wrote:

> Maybe the IRTC should allow tagging a submission as "purist".
> That would be restricted to images created using an officially
> released version of a raytracer, using pure code, no modeller,
> no external data files, no image maps, no multipass renders, and
> of course absolutely no post-processing except jpg conversion.
> Source code would be mandatory for purist images and the highest
> ranking purist image gets an honorable mention ;)

What if the image maps are generated by the ray tracer?

What if the external data files are likewise generated?

What if the post-processing is done by the renderer?

I don't see how combining the results of several POV-Ray renders into 
one final image is less nearly "pure" POV-Ray than the alternative you 
suggest.  I would argue that it is more nearly pure, and not less, 
because it uses POV-Ray to do what is ordinarily done by other applications.

Regards,
John

Post a reply to this message

John VanSickle wrote:

> What if the image maps are generated by the ray tracer?

well, the "no multipass" rule was basically indended to prevent
2d-ish after-effects. Any such effect could be implemented by loading
the image from the first pass, evaluating its pixels one-by-one,
performing any image processing on the pixel array,  recreating
a pigment and applying it to a plane.

 > What if the external data files are likewise generated?

No objections and can be done at the beginning of a single
pass render without problems (at least in POV-Ray). Also, as
long as the scene is capable of render in a single pass, I
don't think there would be objections to also include a
flag to reuse the data file for efficiency when
tweaking renders, as with photon map data.

 > What if the post-processing is done by the renderer?

Not sure what kind of post-processing is supported by raytracers
out there. But I suppose most likely candidates interested in the
"purist" category would be POV-Ray users anyway ;) And MegaPOV's
post-processing features were the reason I suggested "purist"
images should use an *official* release.

Post a reply to this message