Hi Chris..and all..
You might already done this..
but I mention it again..
Instead of setting Bumpheight value just to a positive range..
Like this -> 0 to 0.2
Have the Bumpheight value in the material(s) evenly spread around 0...
Like this -> -0.1 to 0.1 and then set your Displacement value in the
object(s) to 0.1 (As you notice you only now need half the value for the
Disp Val..and this should in most cases then at LEAST cut the render times
into 1/2 =)
Take Care
Best Regards
Stefan Gustafsson ( Beg-inner )
A Proud Owner and User of Real3D and Realsoft3D..
Yes, this was my first error when I started using displacements, however
it
is not the problem I now face. The whole process just seems to be very
slow,
unless there is something else I am missing
Thanks,
Chris
My first guess is to make sure, that the amount of the displacement
(as defined in the property tag) is set to the appropriate size.
Meaning, if you displace a surface by a centimeter, the max
displacement value should be set to that amount as well, and not
higher.. that will conserve resources.
Hope that helps.
Daniel
On 3/21/07, Chris Sellars <[EMAIL PROTECTED]> wrote:
> In a reasonably complex scene which has quite a lot of displacement
mapping,
> I am currently getting render times of over 7hrs for a single frame. If
I
> disable diplacement mapping, I am getting render times of just 17
minutes.
>
> Does anyone know of an efficient method of getting these huge render
times
> down, without impacting on the visual effect of the displacement maps ?
>
> Question for Vesa perhaps.........are there any plans to improve the
> rendering speed of diplacement mapping in the near future ?
>
> Thanks,
>
> Chris Sellars
> Morsel Animation
>
>
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.446 / Virus Database: 268.18.15/728 - Release Date:
20/03/2007 08:07
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.18.14/727 - Release Date: 3/19/2007
11:49 AM
