Hi Greg,
Thanks for the tip, and sorry for the late reply.
Setting -dt to 0 actually sorted the issue (although, as expected,
rendering time went up a lot!)
The scene I am rendering is an interior scene with a lot of artificial
lights, no sun or sky (yet).
The rif file looks something like:
scene= Materials.rad Geometry.rad
AMBFILE= test.amb
OCTREE= test.oct
RESOLUTION= 1195 761
DETAIL= MEDIUM
VARIABILITY = MEDIUM
QUALITY= LOW
INDIRECT= 2
REPORT=2
render= -ad 2048 -as 1024 -dt 0.05 -dc 0.15 -ds 0.02 -dj 0 -av 0 0 0
view= View10 -vtv -vp -220.898262 490.000427 9.770000 -vd -0.310859
2636.535561 0.000000 -vu 0 0 1 -vh 71 -vv 51 -vs 0 -vl 0 -vo 0 -va 0
Best,
Giovanni
···
From: Greg Ward [mailto:[email protected]]
Sent: 24 May 2012 15:55
To: Radiance general discussion
Subject: Re: [Radiance-general] running radiance on multiple cores
You need to tell us more about your scene and rendering parameters.
Sometimes, the direct calculation can cause variances. Try setting -dt
0.
-Greg
From: "Giovanni Betti" <[email protected]>
Date: May 24, 2012 7:10:52 AM PDT
Thanks everybody for the many replies.
Contrary to what Greg suggests, the error (varying brightness)
happens with an ambient file specified.
When I am trying different -av values, a triplet of 0s seems to
give the best results.
I haven't tried yet the combination of vwrays and rtrace
suggested below, will let you know how it goes on with that,
Thanks,
Giovanni
From: Greg Ward [mailto:[email protected]]
Sent: 23 May 2012 22:17
To: Radiance general discussion
Subject: Re: [Radiance-general] running radiance on multiple
cores
Another workaround is to use vwrays and rtrace instead of
rpiece, like so:
set vargs=`rad -s -n -V -v $vw $rif OPTF=render.opt`
vwrays -ff -x $xr -y $yr $vargs | rtrace -n $nprocs -ffc `vwrays
-d -x $xr -y $yr $vargs` @render.opt $octree > render.hdr
The first command sets the view and puts rendering options in a
file for rtrace. The side-effect is that every pixel gets rendered, and
of course you will want to run pfilt on the output in most cases. (You
can of course add it to the command with "| pfilt -1 -x /3 -y /3 -r .6"
after rtrace.)
-Greg
From: "Jack de Valpine"<[email protected]>
Date: May 23, 2012 2:01:30 PM PDT
Unfortunately, I suspect you are correct...
Sent from my Verizon Wireless 4G LTE DROID
-----Original message-----
From: "Randolph M. Fritz" <[email protected]>
To: [email protected]
On 2012-05-23 16:15:36 +0000, Greg Ward said:
> Some people have complained about misplaced or
incomplete tiles using
> rpiece, but I haven't been able to reproduce or find
the problem.
The problem seems--I say cautiously--to occur on Linux
systems and not
BSD systems. I think I'm going to run a test.
Randolph
> As for varying tile brightness, this is usually caused
by forgetting to
> specify an ambient file (rad AMBFILE variable),
causing redundant and
> wasteful as well as inconsistent calculations.
>
> -Greg
>
>> From: "Giovanni Betti"
>>
>> Date: May 23, 2012 8:50:40 AM PDT
>>
>> Dear List,
>>
>> I am running into some issues while running radiance
on multiple cores.
>> I have radiance running on a Linux virtual machine
and I am using the
>> rad -N option.
>> Sometimes though, I happen to notice in the final
image tiles of
>> varying brightness or even misplaced tiles.
>> I thought it had to do with poor synchronization
because of reading and
>> writing on the network, but it seem to happen also
when I have all the
>> files on my local drive.
>> Has anyone run into a similar problem and/or knows a
solution for it?
>>
>> Thanks in advance,
>>
>> Giovanni
--
Randolph M. Fritz
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general