POV-Ray : Newsgroups : povray.binaries.utilities : Cylindrical Height Field include file for Tmpov Server Time
7 May 2024 15:07:32 EDT (-0400)
  Cylindrical Height Field include file for Tmpov (Message 1 to 6 of 6)  
From: Jerry Anning
Subject: Cylindrical Height Field include file for Tmpov
Date: 29 Aug 1998 20:18:32
Message: <35E88C48.94A83F03@dhol.com>
I have attached an include file (it requires Tmpov) that allows you to
wrap a height field around all or part of a horizontal or vertical
cylinder, with many options.  Among other things, the height field can
stick out of the cylinder, cut into it, or do a combination of both. 
Expanded forms of water_level are also implemented.  Documentation is in
the include file.  Some (fairly lame) sample pictures are posted at
povray.binaries.images.  I plan to make this work under 3.1, and also to
add support for wrapping spheres, tori and other things.  I would
appreciate bug reports.

Jerry Anning
cle### [at] dholcom


Post a reply to this message


Attachments:
Download 'hfwrap.inc.txt' (22 KB)

From: Peter Popov
Subject: Re: Cylindrical Height Field include file for Tmpov
Date: 3 Sep 1998 11:58:53
Message: <35eeaead.0@news.povray.org>
Is there a way you can code this using 3.1's file functions?

Peter


Post a reply to this message

From: Jerry Anning
Subject: Re: Cylindrical Height Field include file for Tmpov
Date: 3 Sep 1998 13:06:50
Message: <35EEBE9A.145BC915@dhol.com>
Peter Popov wrote:
> 
> Is there a way you can code this using 3.1's file functions?

I would like to do so, but the 3.1 file read function requires a comma
delimited ascii file with strings quote delimited.  AFAIK, there is no
binary read.  I may have a trick to get around that.  I am experimenting
now.  If not, I will have to write a little preprocessor to feed such a
file to 3.1.  Or maybe Tmpov for 3.1 will come on line before I
succeed.  Perhaps the POV-Team will even add a binary read, although I
wouldn't hold my breath.  One way or another, I intend to make it
happen.  If for no other reason, 3.1 macros will make my code much
cleaner.

Jerry Anning
cle### [at] dholcom


Post a reply to this message

From: Peter Popov
Subject: Re: Cylindrical Height Field include file for Tmpov
Date: 3 Sep 1998 15:42:05
Message: <35eee2fd.0@news.povray.org>
Well, I used #write for the first time today and noticed it can't output
hex... Well, you can always uu-encode the .tga and pass that to POV :)

Peter


Post a reply to this message

From: Dan Connelly
Subject: Re: Cylindrical Height Field include file for Tmpov
Date: 9 Sep 1998 21:33:30
Message: <35F71E6D.1B09648A@flash.net>
This should be a very easy patch to write.

Unfortunately this will need to await the source
code release.

Dan

Peter Popov wrote:
> 
> Well, I used #write for the first time today and noticed it can't output
> hex... Well, you can always uu-encode the .tga and pass that to POV :)
> 
> Peter

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


Post a reply to this message

From: jko
Subject: Re: Cylindrical Height Field include file for Tmpov
Date: 14 Nov 1998 13:05:32
Message: <364DC62A.ED8EBB66@home.com>
I would love to see that feature (cylindrical and spherical
heightfields) added to POV-ray. As you know, you can already do this
with Polyray, but I'm not experienced with Polyray (or TmPov for that
matter).

If you write some 3.1 code I'd sure appreciate you letting me know. 
I'll even compile and test your code if you'd like.

Kevin Odhner
jko### [at] homecom
 
Jerry Anning wrote:
> 
> Peter Popov wrote:
> >
> > Is there a way you can code this using 3.1's file functions?
> 
> I would like to do so, but the 3.1 file read function requires a comma
> delimited ascii file with strings quote delimited.  AFAIK, there is no
> binary read.  I may have a trick to get around that.  I am experimenting
> now.  If not, I will have to write a little preprocessor to feed such a
> file to 3.1.  Or maybe Tmpov for 3.1 will come on line before I
> succeed.  Perhaps the POV-Team will even add a binary read, although I
> wouldn't hold my breath.  One way or another, I intend to make it
> happen.  If for no other reason, 3.1 macros will make my code much
> cleaner.
> 
> Jerry Anning
> cle### [at] dholcom


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.