The yuqk fork does this and more in the next release.

The global_settings{} noise_generator option was removed. It was never 
truly global! The old set up added overhead for all patterns. It left a 
situation where sharing SDL was exposed to differences in behavior, any 
time the user sharing did not lock all the noise generator use. It 
limited flexibility with options like fog{} and irid{}.

Created a new 'ip_noise_generator' keyword for the patterns / 
perturbations: agate, bozo, bumps, dents, granite, marble, noise_cubed, 
spiral1, spiral2 and wrinkles. Made changes so the two remaining uses of 
'noise_generator' now set values local to 'fog{}' and 'irid{}'. The 
patterns and features mentioned here are the only ones ever affected by 
'noise_generator' settings, global and not

The attached image is a bit contrived, but does show the updated 
capability with fog{} and irid{}.

In the top row changing the irid{} noise generators with 
'noise_generator' keyword. Left to right, 1, 2 and 3.

In the bottom row playing with fog{}'s new 'noise_generator' setting as 
follows left to right. Maybe a Holiday fog on the right...

// Left
//fog { Fog01_wTurb color <0.9,0.9,0.9>}

// Middle
//fog { Fog01_wTurb color <0.9,0.0,0.0> noise_generator 2}
//fog { Fog01_wTurb color <0.0,0.9,0.0> noise_generator 2}
//fog { Fog01_wTurb color <0.0,0.0,0.9> noise_generator 2}

// Right
fog { Fog01_wTurb color <0.9,0.0,0.0> noise_generator 3}
fog { Fog01_wTurb color <0.0,0.9,0.0> noise_generator 2}
fog { Fog01_wTurb color <0.0,0.0,0.9> noise_generator 3}

Bill P.

Post a reply to this message

Attachments:
Download 'ng_yuqk_changes.png' (506 KB)

Preview of image 'ng_yuqk_changes.png'

William F Pokorny <ano### [at] anonymousorg> wrote:
> The yuqk fork does this and more in the next release.
>
> The global_settings{} noise_generator option was removed. It was never
> truly global! The old set up added overhead for all patterns. It left a
> situation where sharing SDL was exposed to differences in behavior, any
> time the user sharing did not lock all the noise generator use. It
> limited flexibility with options like fog{} and irid{}.
>
> Created a new 'ip_noise_generator' keyword for the patterns /
> perturbations: agate, bozo, bumps, dents, granite, marble, noise_cubed,
> spiral1, spiral2 and wrinkles. Made changes so the two remaining uses of
> 'noise_generator' now set values local to 'fog{}' and 'irid{}'. The
> patterns and features mentioned here are the only ones ever affected by
> 'noise_generator' settings, global and not

Sounds reasonable.  I presume there will be a default 'ip_noise_generator'
value, and a warning for pre-4.0 scenes that use the global_settings()?

Post a reply to this message

On 11/8/24 19:45, Cousin Ricky wrote:
>> Created a new 'ip_noise_generator' keyword for the patterns /
>> perturbations: agate, bozo, bumps, dents, granite, marble, noise_cubed,
>> spiral1, spiral2 and wrinkles. Made changes so the two remaining uses of
>> 'noise_generator' now set values local to 'fog{}' and 'irid{}'. The
>> patterns and features mentioned here are the only ones ever affected by
>> 'noise_generator' settings, global and not

> Sounds reasonable.  I presume there will be a default 'ip_noise_generator'
> value, and a warning for pre-4.0 scenes that use the global_settings()?

The 'ip_noise_generator' internal pattern settings are defaulted in yuqk 
- the effective noise generator defaulting(2) is unchanged from v3.8 
beta 2. The pre-yuqk (4.0 playpen) scenes see an error on invalid use of 
'noise_generator' in global_settings{}.

I believe a v4.0 release of POV-Ray should be something new. The yuqk 
fork - as my playpen for v4.0 changes / ideas - is breaking away from 
official POV-Ray v3.8 over time.

Aside: The maintenance of v3.8 and/or v3.7 versions can be continued 
indefinitely - if there is someone to do what would be tedious work over 
time, keeping those versions compiling as environmental stuff changes.

We can maintain the bridge to our old scenes with an officially 
maintained pre-v4.0 version - without crippling v4.0 development with 
the need to stay backward compatible with the old scenes.

Bill P.

Post a reply to this message