Hello,

Sorry for lack of updates recently; got a new GF...and you know how 
consuming those can be. :-)

Before I proceed with the currently nonexistent waters.inc and 
waterSurfaces.inc, I have a few questions that I wish to pose to the 
community.

1) how should I handle materials? Those weren't typically used in the .inc 
files before, and it could be confusing to users calling textures when 
confronted with a surprise material.

2) there have been a few suggestions as to the method of handling radiosity 
compatibility. How should I do this? I had intended on zeroing ambient, but 
there was a thread in which an emissive (needs new keyword due to media 
conflict) property was defined. Though a good idea, can this be implemented? 
If not, then I think I should just zero ambient as planned. Another method 
from Christian F. defined a macro on/off for ambient. Is there a consensus? 
Should I post a survey to my site or something?

That's about it for now.

I'm going to proceed with waters.inc under a new post, and I thank all 
members who submitted metal textures. If you have more, go for it and post 
them under the metals.inc thread.

As a side note I am writing a simple prog to store textures in an xml file 
with pre rendered pictures displayed on demand. This might progress to 
integration with povray, who knows...right now its just meant to organize 
submitted textures and dump them to include files. If I end up adding much 
more to this and it becomes useful, I just may open source it and post it as 
a utility. A HDD search feature would be nice but I'm not likely to 
implement that...I'd hate to have to write that regex.. O_o'

ian

Post a reply to this message

Am Sun, 12 Apr 2009 05:45:11 -0400 schrieb [GDS|Entropy]:

> Hello,
> [...]
> 
> Before I proceed with the currently nonexistent waters.inc and
> waterSurfaces.inc, I have a few questions that I wish to pose to the
> community.
> [...]

What kind of objects would go into waterSurfaces.inc? If meshes are ok I 
will see if I can contribute some tileable ocean waves. I once wrote a 
patch for POV-Ray that generated such meshes using "The Aqua Library" by 
Jocelyn Frechot but could not publish it due to libaqua's licence. I 
think I posted some images on this group though.
Although I'm not sure whether I can distribute a standalone program that 
generates meshes using libaqua I think I'm allowed to at least make the 
meshes themselves available.

Post a reply to this message

"Lukas Winter" <web### [at] geloeschtremovethisandthedotbeforenet> wrote in 
message news:49e1e476@news.povray.org...
> Am Sun, 12 Apr 2009 05:45:11 -0400 schrieb [GDS|Entropy]:
>
>> Hello,
>> [...]
>>
>> Before I proceed with the currently nonexistent waters.inc and
>> waterSurfaces.inc, I have a few questions that I wish to pose to the
>> community.
>> [...]
>
> What kind of objects would go into waterSurfaces.inc? If meshes are ok I
> will see if I can contribute some tileable ocean waves. I once wrote a
> patch for POV-Ray that generated such meshes using "The Aqua Library" by
> Jocelyn Frechot but could not publish it due to libaqua's licence. I
> think I posted some images on this group though.
> Although I'm not sure whether I can distribute a standalone program that
> generates meshes using libaqua I think I'm allowed to at least make the
> meshes themselves available.

Well I'm surface agnostic, so long as they can be invoked as an object which 
accepts any viable texture.
I will be contributing a few isosurfaces, but those render slowly...so there 
IS a need for fast rendering surfaces as well.

My mailbox can take 20mb I think. So if your file is larger post it to 
rapidshare or something and post the link.
I doubt the pov team will accept huge files though, as the size of the 
distro may be significant to some users.

ian

Post a reply to this message

"[GDS|Entropy]" <gds-entropy AT hotmail DOT com> wrote in message 
news:49e1b829@news.povray.org...
> 2) there have been a few suggestions as to the method of handling radiosity 
> compatibility. How should I do this? I had intended on zeroing ambient, but 
> there was a thread in which an emissive (needs new keyword due to media 
> conflict) property was defined. Though a good idea, can this be implemented? 
> If not, then I think I should just zero ambient as planned. Another method 
> from Christian F. defined a macro on/off for ambient. Is there a consensus? 
> Should I post a survey to my site or something?

I really don't see a need for a new keyword, certainly not if it has the exact 
same effect as ambient.  Just omit ambient in the finish.  If people don't like 
the default ambient, they should change it with the keyword that's meant to do 
just that:
#default {finish {ambient 0}}
(it might be a good idea to add that line to radiosity.inc)

cu!
-- 
#macro G(b,e)b+(e-b)*C/50#end#macro _(b,e,k,l)#local C=0;#while(C<50)
sphere{G(b,e)+3*z.1pigment{rgb G(k,l)}finish{ambient 1}}#local C=C+1;
#end#end _(y-x,y,x,x+y)_(y,-x-y,x+y,y)_(-x-y,-y,y,y+z)_(-y,y,y+z,x+y)
_(0x+y.5+y/2x)_(0x-y.5+y/2x)            // ZK http://www.povplace.com

Post a reply to this message

[GDS|Entropy] nous illumina en ce 2009-04-12 05:45 -->
> Hello,
> 
> Sorry for lack of updates recently; got a new GF...and you know how 
> consuming those can be. :-)
> 
> Before I proceed with the currently nonexistent waters.inc and 
> waterSurfaces.inc, I have a few questions that I wish to pose to the 
> community.
> 
> 1) how should I handle materials? Those weren't typically used in the .inc 
> files before, and it could be confusing to users calling textures when 
> confronted with a surprise material.
> 
> 2) there have been a few suggestions as to the method of handling radiosity 
> compatibility. How should I do this? I had intended on zeroing ambient, but 
> there was a thread in which an emissive (needs new keyword due to media 
> conflict) property was defined. Though a good idea, can this be implemented? 
> If not, then I think I should just zero ambient as planned. Another method 
> from Christian F. defined a macro on/off for ambient. Is there a consensus? 
> Should I post a survey to my site or something?
> 
> That's about it for now.
> 
> I'm going to proceed with waters.inc under a new post, and I thank all 
> members who submitted metal textures. If you have more, go for it and post 
> them under the metals.inc thread.
> 
> As a side note I am writing a simple prog to store textures in an xml file 
> with pre rendered pictures displayed on demand. This might progress to 
> integration with povray, who knows...right now its just meant to organize 
> submitted textures and dump them to include files. If I end up adding much 
> more to this and it becomes useful, I just may open source it and post it as 
> a utility. A HDD search feature would be nice but I'm not likely to 
> implement that...I'd hate to have to write that regex.. O_o'
> 
> ian 
> 
> 
It's easy to have a material AND a texture.
If someone want a texture, he use the texture. If he want a material, then, he 
use the material.
You can diferiensate them with a prefix:
"P_" for pigments.
"T_" for textures. You also can have no prefix for the texture.
"M_" for materials.
"I_" for interiors.
"F_" for finishes.

As long as you are self concistent, it should be OK.

-- 
Alain
-------------------------------------------------
For here we are not afraid to follow truth wherever it may lead.
Thomas Jefferson

Post a reply to this message