High!

On 06/10/2010 01:16 PM, Dave Blandston wrote:

> I used version 3.7 37a. But, the difference is probably caused by the different
> view/time of day.

Yes, you should set the y value of Rot_Ghurghusht (line 552) to 150!

See you in Khyberspace!

Yadgar

Now playing: Magnetic Fields Part III, live 1982 Shanghai (Jean-Michel 
Jarre)

Post a reply to this message

> High!
>
> On 06/10/2010 02:10 AM, clipka wrote:
>
>> What settings do you use for media sampling (method,
>
> 3
>
>> and possibly
>> variance & confidence
>
> Default values
>
>> or aa_level && aa_threshold
>
> No anti-aliasing
>
>> and/or jitter)?
>
> No jitter

Do use anti-aliasing for the media, and also by all means do use jitter 
- it should help a lot to break up the banding (introducing some random 
noise instead); something like 0.5 should be ok I guess.

Post a reply to this message

High!

On 06/10/2010 02:05 PM, clipka wrote:

> Do use anti-aliasing for the media, and also by all means do use jitter

So this means that I have to use an area_light instead of a simple point 
light? But then it would render dead slow, several hours per frame, so I 
probably won't get any animation ready during my lifetime...

See you in Khyberspace!

Yadgar

Post a reply to this message

High!

On 06/10/2010 02:05 PM, clipka wrote:

> Do use anti-aliasing for the media, and also by all means do use jitter
> - it should help a lot to break up the banding (introducing some random
> noise instead); something like 0.5 should be ok I guess.

I'm using version 3.6, so jitter doesn't accept any parameters!

See you in Khyberspace!

Yadgar

Post a reply to this message

> so I probably won't get any animation ready during my lifetime...

You'll just have to resolve to live forever in that case.



-- 

Best Regards,
	Stephen

Post a reply to this message

>> Do use anti-aliasing for the media, and also by all means do use jitter
>
> So this means that I have to use an area_light instead of a simple point
> light? But then it would render dead slow, several hours per frame, so I
> probably won't get any animation ready during my lifetime...

No, not jittered light sources, but jittered media samples; someone 
forget to put that one into the syntax overview of media, but it's 
mentioned in the inbuilt help, section 3.6.2.2, "Sampling Parameters & 
Methods" (last paragraph).

Post a reply to this message

My honest response was, "Is there dust on my screen?"  I don't mean to be cruel,
but I think it's ultimately a problem with trying to portray stars on small
pixel size images.   IMO, the eye will be more tolerant of stars are a little
bit more stylized and let one perceive them as circles,  than stars that look
like "noise".

Post a reply to this message

> #declare TP_ATMO_INTERVALS = 3; // Necessary for good integration
> #declare TP_ATMO_SAMPLES = 10;
> #declare TP_ATMO_METHOD = 3; // Adaptive
>
intervals must stay at 1, default value.
Increase the samples to 30 to 50 instead.

intervals 1 samples 60 is faster than intervals 3 samples 10, for twice 
the samples.


Alain

Post a reply to this message

On 06/10/2010 12:04 PM, clipka wrote:

> 
>>> Do use anti-aliasing for the media, and also by all means do use jitter
>>
>> So this means that I have to use an area_light instead of a simple point
>> light? But then it would render dead slow, several hours per frame, so I
>> probably won't get any animation ready during my lifetime...
> 
> No, not jittered light sources, but jittered media samples; someone
> forget to put that one into the syntax overview of media, but it's
> mentioned in the inbuilt help, section 3.6.2.2, "Sampling Parameters &
> Methods" (last paragraph).

default value = 0?

Post a reply to this message

=?ISO-8859-1?Q?J=F6rg_=27Yadgar=27_Bleimann?= <yaz### [at] gmxde> wrote:
> Yes, you should set the y value of Rot_Ghurghusht (line 552) to 150!

Nope, that wasn't it...

Post a reply to this message