hi,

Thomas de Groot <tho### [at] degrootorg> wrote:
> Op 20/04/2021 om 20:06 schreef Bald Eagle:
> > ...
> > that the user could address and select them _numerically_.
> yes indeed.

but how will a numpty like self know how to select?  I do hope that there will a
few introductory paragraphs discussing, and a small table laying out, the
principal (POV-Ray) components making "granite"; their role and useful parameter
ranges, etc.


regards, jr.

Post a reply to this message

Bald Eagle wrote on 19/04/2021 12:33:
> Paolo Gibellini <p.g### [at] gmailcom> wrote:
>> Thomas de Groot wrote on 16/04/2021 08:46:
>>> [snip]>
>>
>> Regarding marbles, in my area it was often used marble containing
>> ammonites, does this seem an interesting challenge to you?
>> See the picture as reference.
>>
>> Paolo
> 
> :D   Way to raise the bar, Paolo.
> 
> 
> Maybe something akin to Ingo's blob pattern could be used for the ammonites, and
> then a repeat warp added in...
> 

I agree with Thomas: we could try to do a challenge, and you could make 
these ideas /concrete/...

Paolo

Post a reply to this message

Thomas de Groot wrote on 19/04/2021 13:56:
> Op 19-4-2021 om 11:57 schreef Paolo Gibellini:
>> Thomas de Groot wrote on 16/04/2021 08:46:
>>> [snip]>
>>
>> Regarding marbles, in my area it was often used marble containing 
>> ammonites, does this seem an interesting challenge to you?
>> See the picture as reference.
>>
>> Paolo
> 
> A challenge? It would be a very interesting to do indeed. Not 
> immediately as I want to complete the granites first, but it is /an 
> offer I cannot refuse/ ;-)
> 

Honestly I used the word challenge in a generic way, but a real 
challenge could be interesting, it would add more content to the inc files.

When you are done...

;-)
Paolo

Post a reply to this message

Thomas de Groot <tho### [at] degrootorg> wrote:
> I realise that I have taken
> on a major investigation :-) and that is ok.

So did I while writing this!


> Imo, the white represents the quartz veins that cut through the
> granites. In the original code they came out as mere "clouds" of grey; I
> brought them back at least as something looking like veins (the top
> texture). See the examples I provided.

IIRC, the marble pattern is just a series of repeating lines that attains a
marble look due to the turbulence.   Maybe make a material_map using turbulated
marble and have the granite and quartz materials be the entries.

Post a reply to this message

"jr" <cre### [at] gmailcom> wrote:

> but how will a numpty like self know how to select?

You won't.  It will be one those fun mystery things, like a grab-bag, an egg
hunt, voting.  Or dating.

Actually, part of the idea I had, which is somewhat demonstrated in the stuff I
posted for TdG, is that, while not self-documenting, the code can be made to be
"self-documentable" - in that, the verbose feature embedded into all of the
macros could be turned on by such an array instantiation macro, and then you'd
generate a list of entries upon execution.  Really, the idea was to have them
available for random selection...

> I do hope that there will a
> few introductory paragraphs discussing, and a small table laying out, the
> principal (POV-Ray) components making "granite"; their role and useful parameter
> ranges, etc.

Could do that, or issue a #warning depending on values of macro parameters.
Might just imply correct values by using min/max in macro definition, or
comments.

I agree, but I can see the line between "include file" and "geology textbook"
becoming rapidly blurred.

Post a reply to this message

Op 21-4-2021 om 12:51 schreef Bald Eagle:
> Thomas de Groot <tho### [at] degrootorg> wrote:
>> I realise that I have taken
>> on a major investigation :-) and that is ok.
> 
> So did I while writing this!
> 
> 
>> Imo, the white represents the quartz veins that cut through the
>> granites. In the original code they came out as mere "clouds" of grey; I
>> brought them back at least as something looking like veins (the top
>> texture). See the examples I provided.
> 
> IIRC, the marble pattern is just a series of repeating lines that attains a
> marble look due to the turbulence.   Maybe make a material_map using turbulated
> marble and have the granite and quartz materials be the entries.
> 
Turbulence is the keyword assuredly. In the latest version (in examples 
shown above) the quartz veins are partly controlled by warp {turbulence 
...}. Which reminds me: warp {} is another one of those things 
"learned". The use of marble (or agate maybe?) may be useful; 
investigation required.

[Tonight, I am going to browse my old textbooks to get some more useful 
info about granites. Feels like old times; I didn't specialise in hard 
rock geology but rather in sedimentary environments. However, those 
stony things were part of the curriculum and, I think I mentioned it, 
the penultimate ice age conveniently brought Scandinavian granites to 
this region, and I have some of them in my backyard. I wouldn't be 
surprised if they were also related to the North American granites of 
the east coast of US and Canada through the action of plate tectonics. 
But that is a completely different story.]

-- 
Thomas

Post a reply to this message

hi,

"Bald Eagle" <cre### [at] netscapenet> wrote:
> "jr" <cre### [at] gmailcom> wrote:
>
> > but how will a numpty like self know how to select?
>
> You won't.  It will be one those fun mystery things, like a grab-bag, an egg
> hunt, voting.  Or dating.

fun, huh?


> Actually, part of the idea I had, which is somewhat demonstrated in the stuff I
> posted for TdG, is that, while not self-documenting, the code can be made to be
> "self-documentable" - in that, the verbose feature embedded into all of the
> macros could be turned on by such an array instantiation macro, and then you'd
> generate a list of entries upon execution.  Really, the idea was to have them
> available for random selection...

for supplementary info perhaps.  but before the parser can spit out info, I
already need to have a scene, no?  so, I would need (some) information up front.


> > I do hope that there will a
> > few introductory paragraphs discussing, and a small table laying out, the
> > principal (POV-Ray) components making "granite"; their role and useful parameter
> > ranges, etc.
>
> Could do that, or issue a #warning depending on values of macro parameters.
> Might just imply correct values by using min/max in macro definition, or
> comments.
>
> I agree, but I can see the line between "include file" and "geology textbook"
> becoming rapidly blurred.

maybe you misread, maybe I put it poorly.  "geology textbook" -- I'm sure that
some "background" info for each variant would be nice to have, to help
contextualise.  what I tried to say is I'd like to read "why we fake granite in
POV the way we do, how do we work around the limitations of the tools in the
box, this POV-Ray feature is used because ..." etc.

note to Thomas: _please_ correct the spelling to 'mahogany'.


regards, jr.

Post a reply to this message

Op 21-4-2021 om 13:56 schreef jr:
> note to Thomas: _please_ correct the spelling to 'mahogany'.

I have been wondering about the spelling. After (again) assessing the 
occurrence of both spellings on the net, it seems indeed that "Mahogany" 
is the correct one.

I followed Daniel Mecklenburg's original (wrong) spelling from the start.

Additional Names: Dakota Mahagony,Dakota Mahogany,Mahogany 
Dakota,Mahogany Dakota America,Rushmore Mahogany,Select Mahogany,Sunset 
Mahogany,Brown Velvet Mahogany,Whetstone Mahogany,American 
Bouquet,Carnelian Granite    :-)

see: https://www.stonecontact.com/dakota-red-granite/s618

I shall correct but I wonder if I am not going to name it: "Dakota Red 
Granite" instead.

-- 
Thomas

Post a reply to this message

in news:web.608012f064981f5c79819d986cde94f1@news.povray.org jr wrote:

> "fake granite

've been looking at this thread with half an eye only. I worked in the 
graphics industry for quite a while and one of my jobs was pattern 
designer & colorist. The one thing I learnt,

People want what they think looks like the real thing. Not what the real 
thing actually looks like.

I have a colorised concrete floor in my house. The top layer has been 
ground off into the "grain". "What a nice marble floor" ... it looks more 
like a coarse granite ... it is closest to man made terazzo .... But still 
"a nice marble floor" ;)

https://ingoogni.nl/stuff/IMG_2021_04_21_0277_s.jpg with a nice line of 
light.

Ingo

Post a reply to this message

hi,

Thomas de Groot <tho### [at] degrootorg> wrote:
> Op 21-4-2021 om 13:56 schreef jr:
> > note to Thomas: _please_ correct the spelling to 'mahogany'.
>
> I have been wondering about the spelling. After (again) assessing the
> occurrence of both spellings on the net, it seems indeed that "Mahogany"
> is the correct one.

perhaps also to do with accessing the net from the Netherlands vs the UK?  both
Google and Wiktionary don't think much -- anything! -- of 'mohogany'.


> I followed Daniel Mecklenburg's original (wrong) spelling from the start.
>
> Additional Names: Dakota Mahagony,Dakota Mahogany,Mahogany
> Dakota,Mahogany Dakota America,Rushmore Mahogany,Select Mahogany,Sunset
> Mahogany,Brown Velvet Mahogany,Whetstone Mahogany,American
> Bouquet,Carnelian Granite    :-)
>
> see: {...}
>
> I shall correct but I wonder if I am not going to name it: "Dakota Red
> Granite" instead.

do "mahogany granites" occur in places other than the Dakotas? if yes, I'd put
the "Dakota Red" plus latin nomenclature with the by-variant "background" info.

(and thanks for making change to spelling)


regards, jr.

Post a reply to this message