Here is info on the latest version of UVPov, my unofficial version of POV
that includes UV (surface) mapping among other things.  Many of the features
(such as double_illuminate) are highly experimental, but it should be fun
to play with.  This unofficial version is based on POV-Ray 3.1.

Features:
  Surface Mapping  (also part of the SuperPatch)
  Image Pattern    (also part of the SuperPatch)
  New mesh syntax  (also part of the SuperPatch)
  reset_children warp
  double_illuminate flag
  solid triangle meshes (not very well tested yet)

Source code for the POV-Ray core files, as well as a Windows binary are
available for download.

Website:
http://nathan.kopp.com/patched.htm

This release is called "beta 2", but I have a feeling that it will always
be in beta (that makes it more fun and exciting).

I will continue to expand the number objects that support UV mapping, and
if anyone wants to help, they can let me know.

-Nathan Kopp

Post a reply to this message

The UV stuff is really nice.  I've succesfully converted Poser3 figures to POV
with full textures using Thomas Baier's win3dspov and the superpatch, which is
really, really wild.  I'll probably post an example to binaries.images in a week
or two.

-Mike

Nathan Kopp wrote:

> Here is info on the latest version of UVPov, my unofficial version of POV
> that includes UV (surface) mapping among other things.  Many of the features
> (such as double_illuminate) are highly experimental, but it should be fun
> to play with.  This unofficial version is based on POV-Ray 3.1.
>
> Features:
>   Surface Mapping  (also part of the SuperPatch)
>   Image Pattern    (also part of the SuperPatch)
>   New mesh syntax  (also part of the SuperPatch)
>   reset_children warp
>   double_illuminate flag
>   solid triangle meshes (not very well tested yet)
>
> Source code for the POV-Ray core files, as well as a Windows binary are
> available for download.
>
> Website:
> http://nathan.kopp.com/patched.htm
>
> This release is called "beta 2", but I have a feeling that it will always
> be in beta (that makes it more fun and exciting).
>
> I will continue to expand the number objects that support UV mapping, and
> if anyone wants to help, they can let me know.
>
> -Nathan Kopp

Post a reply to this message

Nathan Kopp wrote:

> Here is info on the latest version of UVPov, my unofficial version of POV
> that includes UV (surface) mapping among other things.  Many of the features
> (such as double_illuminate) are highly experimental, but it should be fun
> to play with.  This unofficial version is based on POV-Ray 3.1.
>
> Features:
>   Surface Mapping  (also part of the SuperPatch)
>   Image Pattern    (also part of the SuperPatch)
>   New mesh syntax  (also part of the SuperPatch)
>   reset_children warp
>   double_illuminate flag
>   solid triangle meshes (not very well tested yet)
>
> Source code for the POV-Ray core files, as well as a Windows binary are
> available for download.
>
> Website:
> http://nathan.kopp.com/patched.htm
>
> This release is called "beta 2", but I have a feeling that it will always
> be in beta (that makes it more fun and exciting).
>
> I will continue to expand the number objects that support UV mapping, and
> if anyone wants to help, they can let me know.
>
> -Nathan Kopp

 Is 'reset_children warp' the same function like the 'WARP MAP ONLY' - Patch
from PatchStation from Daren Scot Wilson ?

I think, this is the same function or are there differences between both
patches??

Zan Trajkov

Post a reply to this message

The "reset_children" warp provides the same functionality that the Daren's
warp_map_only patch was trying to do.  In fact, the concept for this feature
came in part from Daren's patch.  However, his patch has some bugs.
You see, POV translates, scales, and rotates textures by using warps.
So, if you say "warp_map_only", then the sub-textures do not get
transformed at all.  This is not good, because when you transform an
object, POV also transforms the object's textures (using warps) to make
the textures follow the object.  Example:
object{
  MyObject
  texture { MyTex }
  translate 10   // this translate becomes a warp in the texture
}

Well, if you don't warp the sub-textures at all, they will not get
translated with the object.  :(

My patch only stops some of the warping of the children, and maintains
all of the warps that are associated with object transformations.  I have
emailed Daren Scot Wilson about this, although I should give him some
credit on my web page.

-Nathan Kopp

Zan Trajkov wrote:
> 
>  Is 'reset_children warp' the same function like the 'WARP MAP ONLY' - Patch
> from PatchStation from Daren Scot Wilson ?
> 
> I think, this is the same function or are there differences between both
> patches??
> 
> Zan Trajkov

Post a reply to this message

Nathan Kopp wrote:
> 
> Here is info on the latest version of UVPov, my unofficial version of POV
> that includes UV (surface) mapping among other things.

Nathan:

Do you plan to merge your upgraded patch into SuperPatch?


Dan

-- 
http://www.flash.net/~djconnel/

Post a reply to this message

Dan Connelly wrote:
> 
> Do you plan to merge your upgraded patch into SuperPatch?
> 

This is up to Ron Parker, who is in charge of the SuperPatch.  I gave him
permission to use my code earlier.  Ron, if you're reading this, you still
have permission to use my code in the SuperPatch.

-Nathan Kopp

Post a reply to this message

On Mon, 02 Nov 1998 23:07:21 -0500, Nathan Kopp <Nat### [at] Koppcom> wrote:
>Dan Connelly wrote:
>> 
>> Do you plan to merge your upgraded patch into SuperPatch?
>> 
>
>This is up to Ron Parker, who is in charge of the SuperPatch.  I gave him
>permission to use my code earlier.  Ron, if you're reading this, you still
>have permission to use my code in the SuperPatch.

I know.  I'm trying to write documentation for what I have now, then I'm 
going to start a new round of patches including yours, a bunch of new
warps I received yesterday, and the updates to wyzpov.

Post a reply to this message

Ron Parker wrote:
> 
> On Mon, 02 Nov 1998 23:07:21 -0500, Nathan Kopp <Nat### [at] Koppcom> wrote:
> >Dan Connelly wrote:
> >>
> >> Do you plan to merge your upgraded patch into SuperPatch?
> >>
> >
> >This is up to Ron Parker, who is in charge of the SuperPatch.  I gave him
> >permission to use my code earlier.  Ron, if you're reading this, you still
> >have permission to use my code in the SuperPatch.
> 
> I know.  I'm trying to write documentation for what I have now, then I'm
> going to start a new round of patches including yours, a bunch of new
> warps I received yesterday, and the updates to wyzpov.


The reason I ask is I know I am a lot less willing to download a number of
individual pvengine.exe's than I would a revised version of SuperPatch --
I suspect many others feel the same way.  It avoids the problem of having
a superproliferation of binaries and of having to choose between feature
sets on individual images.

The SuperPatch is really a wonderful contribution -- it really expands
POV capabilities.  I only regret I haven't had the time in the near-year-
end rush at work to look into all the features as yet.

Dan

-- 
http://www.flash.net/~djconnel/

Post a reply to this message

On Wed, 04 Nov 1998 18:29:20 -0600, Dan Connelly <djc### [at] flashnet>
wrote:

>The reason I ask is I know I am a lot less willing to download a number of
>individual pvengine.exe's than I would a revised version of SuperPatch --
>I suspect many others feel the same way.  It avoids the problem of having
>a superproliferation of binaries and of having to choose between feature
>sets on individual images.

I agree.  That's why I've put so much time into this thing.  I'm
working on docs this very minute, in fact, so hopefully it'll be even
more usable.

>The SuperPatch is really a wonderful contribution -- it really expands
>POV capabilities.  I only regret I haven't had the time in the near-year-
>end rush at work to look into all the features as yet.

I regret to inform you that I'm adding still more features, as
mentioned above. :)  Three that are already implemented but not
mentioned above are:

o #ifdef(array[index])
o transparency works in a pattern statement now
o You can specify hf_gray_16 as the first parameter to a pattern    
  statement to generate a 16-bit heightfield.

Post a reply to this message