We uploaded our latest version of our unofficial compile for Macintosh.

New in this version: 
    -Upgraded the rendering engine with several patches. 
    -Photons (real caustics). 
    -Light & shadow controls with light groups. 
    -Improved sampling methods for media. 
    -Improved radiosity. 
    -Solid triangle mesh and new mesh type: mesh2. 
    -Smooth color triangle with different colors at each vertex. 
    -New object type: Isoblob. 
    -New patch type: rational bezier. 
    -Object controls 'no_image', 'no_reflection'. 
    -Colored attenuation in objects. 
    -Double_illuminate to illuminate both sides of the object's surface.
    -UV mapping. 
    -Reset child textures, so that transformations only affect the 
      parent texture. 
    -Slope dependent texture. 
    -Several new patterns (triangle, square,....). 
    -Added pigment function in Isosurface. 
    -Transform points with vtransform(). 
    -Trace function to find the intersection point with an object. 
    -New keywords 'image_height' and 'image_width' to use actual image 
      size in the scene. 
    -New keywords 'initial_frame', 'final_frame', 'initial_clock',
      'final_clock' and 'frame_number' to use actual clock
      values in the scene. 
    -Added a link in the camera template to call the normal template. 
    -Added links in the objects template to call pigment, normal and
      finish templates. 
    -Added a panel in the application prefs dialog to set four
      additional include paths. 
    -Added an indicator in the files & paths panel to show if 'use ini'
      is set. 

Fixes and changes in this version: 
    *Fixed a bug in the universal headers, that didn't allow to select
      text and pref files at the same time in the batch. 
    *Fixed several small syntax errors in the template dialogs. 
    *Using the edit button in the batch will also open text files
      (before only pref files). 
    *Fixed a triangle bug. 
    *Fixed number_of_waves bug. 
    *Fixed bug in gamma with focal_blur . 
    *Fixed a bug in movie and pict output. Caused problems when not
      opening the compression dialog. 
    *Adapted all templates for the new keywords (patches). Unofficial
      keywords are shown in blue or with an asterix. 
    *Rearanged layout for object templates. 

You can find all these lovely things at:
http://users.skynet.be/smellenbergh

Many thanks to all the authors of the patches, especially to Nathan Kopp
who we bothered a bit with our questions and bug reports :-)

Also many thanks to J. Grimbert who helped us getting the no-image and
no-refection patch to work.

Best regards, 

Smellenbergh

-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh

Post a reply to this message

smellenbergh wrote:

>     -New keywords 'image_height' and 'image_width' to use actual image
>       size in the scene.

I'm a little fuzzy on this one. What is the difference in this feature
compared to simply scaling the image ?

-- 
Ken Tyler -  1200+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/

Post a reply to this message

I'm guessing it is about gathering the render image resolution up and being
able to use that in the scene file somehow.  But just a guess.

Bob

Ken <tyl### [at] pacbellnet> wrote in message
news:3830513E.8D9D64D8@pacbell.net...
> smellenbergh wrote:
>
> >     -New keywords 'image_height' and 'image_width' to use actual image
> >       size in the scene.
>
> I'm a little fuzzy on this one. What is the difference in this feature
> compared to simply scaling the image ?
>
> --
> Ken Tyler -  1200+ Povray, Graphics, 3D Rendering, and Raytracing Links:
> http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/

Post a reply to this message

Ken <tyl### [at] pacbellnet> wrote:

> smellenbergh wrote:
> 
> >     -New keywords 'image_height' and 'image_width' to use actual image
> >       size in the scene.
> 
> I'm a little fuzzy on this one. What is the difference in this feature
> compared to simply scaling the image ?

It's easy:
camera {
    perspective 
    location <0.0, 0.0, -5>
    up y*image_height right x*image_width
    angle 60
    look_at <0.0, 0.0, 0.0>
}

and your image is right, no mather what size you use. We have found it
very usefull while messing :-) with all those patches. 
Image_height/width return the settings you use for the render.
It just makes things easier. There was already a patch but they used the
keywords screen_height and screen width, we think that talking about the
image is more accurate.


smellenbergh

-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh

Post a reply to this message

In povray.general smellenbergh <sme### [at] skynetbe> wrote:
: and your image is right, no mather what size you use.

... supposing that your screen pixels are square.

  Sometimes the distorted aspect ratio is intentional. For example when
making an image for the 320x400 resolution (eg. windows startup image).

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Well, I can finally stop working on MacUVPov. :-)

Post a reply to this message

Did you do something to the basic render method? I have been working on a
file with the previous release, and grabbedthis one right away. It uses
nothing but standard primitives, and when I render it in the new version it
includes a large shadow, a bunch of red spheres now have blue edges,
andwhile cylinders have light blue "auras". Plus the shadow has some
distinctive blocks in it.

Any ideas? I can post some examples if it'd help?

Josh English

(ps, when I went back to the old version, the Editor Prefs were all messed
up, syntatic coloring was messed up real bad.. I know, I should have
seperated my pref files...)

smellenbergh wrote:

> We uploaded our latest version of our unofficial compile for Macintosh.
>
> New in this version:
>     -Upgraded the rendering engine with several patches.
>     -Photons (real caustics).
>     -Light & shadow controls with light groups.
>     -Improved sampling methods for media.
>     -Improved radiosity.
>     -Solid triangle mesh and new mesh type: mesh2.
>     -Smooth color triangle with different colors at each vertex.
>     -New object type: Isoblob.
>     -New patch type: rational bezier.
>     -Object controls 'no_image', 'no_reflection'.
>     -Colored attenuation in objects.
>     -Double_illuminate to illuminate both sides of the object's surface.
>     -UV mapping.
>     -Reset child textures, so that transformations only affect the
>       parent texture.
>     -Slope dependent texture.
>     -Several new patterns (triangle, square,....).
>     -Added pigment function in Isosurface.
>     -Transform points with vtransform().
>     -Trace function to find the intersection point with an object.
>     -New keywords 'image_height' and 'image_width' to use actual image
>       size in the scene.
>     -New keywords 'initial_frame', 'final_frame', 'initial_clock',
>       'final_clock' and 'frame_number' to use actual clock
>       values in the scene.
>     -Added a link in the camera template to call the normal template.
>     -Added links in the objects template to call pigment, normal and
>       finish templates.
>     -Added a panel in the application prefs dialog to set four
>       additional include paths.
>     -Added an indicator in the files & paths panel to show if 'use ini'
>       is set.
>
> Fixes and changes in this version:
>     *Fixed a bug in the universal headers, that didn't allow to select
>       text and pref files at the same time in the batch.
>     *Fixed several small syntax errors in the template dialogs.
>     *Using the edit button in the batch will also open text files
>       (before only pref files).
>     *Fixed a triangle bug.
>     *Fixed number_of_waves bug.
>     *Fixed bug in gamma with focal_blur .
>     *Fixed a bug in movie and pict output. Caused problems when not
>       opening the compression dialog.
>     *Adapted all templates for the new keywords (patches). Unofficial
>       keywords are shown in blue or with an asterix.
>     *Rearanged layout for object templates.
>
> You can find all these lovely things at:
> http://users.skynet.be/smellenbergh
>
> Many thanks to all the authors of the patches, especially to Nathan Kopp
> who we bothered a bit with our questions and bug reports :-)
>
> Also many thanks to J. Grimbert who helped us getting the no-image and
> no-refection patch to work.
>
> Best regards,
>
> Smellenbergh
>
> --
> e-mail:sme### [at] skynetbe
>
> http://users.skynet.be/smellenbergh

Post a reply to this message

Chris Huff <Chr### [at] compuservecom> wrote:

> Well, I can finally stop working on MacUVPov. :-)

Yes, but don't stop working on your patches. As you might have noticed,
one of them already made it, we added it in our compile. The other ones
are promissing but.....
We will contact you for the other ones. There just wasn't time enough to
fully test them and add them. There comes a time you have to stop adding
features and release things, that thime was nov 15 1999 :-)


smellenbergh
-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh

Post a reply to this message

Josh English <eng### [at] spiritonecom> wrote:

> Did you do something to the basic render method? I have been working on a
> file with the previous release, and grabbedthis one right away. It uses
> nothing but standard primitives, and when I render it in the new version it
> includes a large shadow, a bunch of red spheres now have blue edges,
> andwhile cylinders have light blue "auras". Plus the shadow has some
> distinctive blocks in it.
We carefully watched that renders are the same as when using the
official version. However, we use the uv_patch 6.1+ as a base and there
are still some little bugs in it (harmless and we were sure  we avoided
them)

> Any ideas? I can post some examples if it'd help?
Please do, that is the only way to find out what is going on. Just mail
them to us and we will check it out.
 
> Josh English
> 
> (ps, when I went back to the old version, the Editor Prefs were all messed
> up, syntatic coloring was messed up real bad.. I know, I should have
> seperated my pref files...)
Yes, that seems to be a problem. We changed a lot in the prefs and the
old version can't handle it. You will have to throw the prefs away in
the system folder or move them every time you use a differend version.
It's an old mistake that keeps following  us :-(

smellenbergh

> 

-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh

Post a reply to this message

>Yes, but don't stop working on your patches. As you might have noticed,

one of them already made it, we added it in our compile. The other ones
are promissing but.....
We will contact you for the other ones. There just wasn't time enough to

fully test them and add them. There comes a time you have to stop adding

features and release things, that thime was nov 15 1999 :-)<

No immediate danger of me stopping my patch work. It will slow down a
bit, though. If anyone has any suggestions or ideas for new features, I
would like to hear them. :-)
And yes, I did notice that vtransform() made it. I am glad to find out
someone else is interested in my work. :-)

I had a bit of trouble downloading the new version, though. The server
kept dropping the connection. I eventually did get it, though, and will
probably be using it for most of my work.

Post a reply to this message

>No immediate danger of me stopping my patch work. It will slow down a
>bit, though. If anyone has any suggestions or ideas for new features, I
>would like to hear them. :-)

Wish list, for now: anisotropics, blinn shading, and subsurface scattering.
I'll think of more things as they come...

Thanks for all you have done so far. Believe me, I do appreciate it and I'm
very greatful. Please keep it up. =)

Post a reply to this message

Could you explain what anisotropics, blinn shading, and subsurface
scattering are? I have no idea what they do, I never even heard of
them.(except anisotropics, I have heard of those. I don't know what they
do, though.) :-)

Post a reply to this message

On Tue, 16 Nov 1999 07:14:38 -0500, Chris Huff wrote:
>Could you explain what anisotropics, blinn shading, and subsurface
>scattering are? I have no idea what they do, I never even heard of
>them.(except anisotropics, I have heard of those. I don't know what they
>do, though.) :-)

An anisotropic shader would have different effects depending on not just
the local "elevation" of the incident ray, as is usual, but also the local 
"azimuth." Think of one of those Christmas ornaments that's wrapped with 
fine fiber and thus has a ring-shaped highlight.  I'm thinking such a thing
would require UV mapping as a prerequisite.

-- 
These are my opinions.  I do NOT speak for the POV-Team.
The superpatch: http://www2.fwi.com/~parkerr/superpatch/
My other stuff: http://www2.fwi.com/~parkerr/traces.html

Post a reply to this message

Blinn is a type of shading like phong that is good for simulating cloth
materials (I saw it in Max). Subsurface scattering is a rendering concept
that considers all objects partially transparent and renders the light and
its interactions just a little below the surface. If also seems to help in
wetting or dampening surfaces.

Post a reply to this message

These sound interesting, know of any web sites with more info?

Post a reply to this message

About blinn shading, no, not really. Perhaps somewhere on Kinetix's site, or
you can look around. About the subsurf scat, someone recently posted a link
to the original inspiration to Nathan Kopp's photon mapping and it's in
there.

Post a reply to this message

There seems to be a problem with filtering objects, filter is treated
like transmit. I haven't downloaded the bug-fixed version yet, but this
seems to be unrelated to that bug.
For example, this:
sphere {< 0, 0, 0>, 1
  pigment {color Green filter 1}
 translate < 0, 1.0001, 0>
}
is invisible when placed on a ground plane, when it should show up as a
green transparent sphere.
This happens with #version 3.1 but not with #version 3.14159, I don't
know if it happens in UVPov.

Post a reply to this message

Chris Huff wrote:
> 
> There seems to be a problem with filtering objects, filter is treated
> like transmit. I haven't downloaded the bug-fixed version yet, but this
> seems to be unrelated to that bug.
> For example, this:
> sphere {< 0, 0, 0>, 1
>   pigment {color Green filter 1}
>  translate < 0, 1.0001, 0>
> }
> is invisible when placed on a ground plane, when it should show up as a
> green transparent sphere.
> This happens with #version 3.1 but not with #version 3.14159, I don't
> know if it happens in UVPov.

I recall that Warp mentioned something about a dissapearing filtered sphere
problem with UVPov v6.0 that Nathan was going to fix for UVPov v6.1. That
may explain the difference.

-- 
Ken Tyler -  1200+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/

Post a reply to this message

Oh, and the sphere_sweep template form produces b-spline_sphere_sweep
instead of b_spline_sphere_sweep, I thought this was fixed before?

Still using the Nov 15 version, I lost the connection in the middle of
downloading the new version. :-(

Post a reply to this message

Chris Huff <Chr### [at] compuservecom> wrote:

> Oh, and the sphere_sweep template form produces b-spline_sphere_sweep
> instead of b_spline_sphere_sweep, I thought this was fixed before?
We almost had a hardattack while reading this mail! :-)
Keeping cool was the way to go... yes, it was fixed and still is but
there were two spots in the source producing this text. We cleaned up
the sources and guess what: we kept the code producing the wrong test.
It is harmless, and we will fix it for a next version.
Thanks for taking a few year of of our lives. :-) :-)

> Still using the Nov 15 version, I lost the connection in the middle of
> downloading the new version. :-(
We know that feeling, we had the same problem if we wanted to download
from the US. We must admid that this didn't happen for a long time now.
We do know that we have a good server, located here in Belgium, and
perhaps you have to solve it like we did: download after rush hours.

Smellenbergh

-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh

Post a reply to this message

Chris Huff <Chr### [at] compuservecom> wrote:

> There seems to be a problem with filtering objects, filter is treated
> like transmit. I haven't downloaded the bug-fixed version yet, but this
> seems to be unrelated to that bug.
> For example, this:
> sphere {< 0, 0, 0>, 1
>   pigment {color Green filter 1}
>  translate < 0, 1.0001, 0>
> }
> is invisible when placed on a ground plane, when it should show up as a
> green transparent sphere.
> This happens with #version 3.1 but not with #version 3.14159, I don't
> know if it happens in UVPov.

We tried it and we always get a correct image. The whole scene file we
used is included in this mail.
 
A little note:
if you set the version in the source, the setting in the prefs dialog
will be overwritten. Thaugt we could better tell you, we have been
looking for a bug that wasn't there. ;-)

There was a problem but that has been fixed by Nathan in 6.1, we waited
for v6.1 to release our version. 
Are you sure you weren't working with a version you compiled yourself?

If you can reproduce it again with the nov 17 version, please e-mail us
the complete source and a prefs file. 

A little advice: if you have questions about any patch we included,
please post your message in a group where you are more likely to get an
answer (patches, general,..) and give it an appropriate 'Subject'.

Smellenbergh

// Persistence of Vision Ray Tracer Scene Description File
// File: ?.pov
// Vers: 3.1
// Desc: Checkered Floor Example
// Date: mm/dd/yy
// Auth: ?
//

#include "colors.inc"
//#version 3.1;

global_settings
{
  assumed_gamma 1.0
}

// ----------------------------------------
camera {
    perspective 
    location <0.0, 1.5, -5>
    up y*image_height right x*image_width
    angle 60
    look_at <0.0, 0.0, 0.0>
}


sky_sphere
{
  pigment
  {
    gradient y
    color_map { [0.0 color blue 0.6] [1.0 color rgb 1] }
  }
}

light_source
{
  0*x // light's position (translated below)
  color red 1.0  green 1.0  blue 1.0  // light's color
  translate <-30, 30, -30>
}
sphere {< 0, 0, 0>, 1
  pigment {color Green filter 1}
 translate < 0, 1.0001, 0>
}

// ----------------------------------------
plane
{
  y, -1
pigment {
    checker 
    rgbft <1.0, 1.0, 1.0, 0.0, 0.0>,
    rgbft <0.6, 0.6, 0.6, 0.0, 0.0>
}

}



-- 
e-mail:sme### [at] skynetbe

http://users.skynet.be/smellenbergh

Post a reply to this message

>A little advice: if you have questions about any patch we included,
please post your message in a group where you are more likely to get an
answer (patches, general,..) and give it an appropriate 'Subject'.<

Ok, discussion continued under povray.unofficial.patches, in a message
titled "Unofficial MultiPatch filter bug?".

Post a reply to this message

For subsurf scat check out:

http://graphics.stanford.EDU/~henrik/

for a first start point....

hope, this is useful...

v
Zan

TonyB wrote:

> About blinn shading, no, not really. Perhaps somewhere on Kinetix's site, or
> you can look around. About the subsurf scat, someone recently posted a link
> to the original inspiration to Nathan Kopp's photon mapping and it's in
> there.

Post a reply to this message