<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<br>Thanks for the reply. I see. Just thought that because the limit of the VRAM.<br><br>Cheers.<br><br><br><br><div><div id="SkyDrivePlaceholder"></div>> From: brechtvanlommel@pandora.be<br>> Date: Sun, 9 Dec 2012 15:30:01 +0100<br>> To: bf-cycles@blender.org<br>> Subject: Re: [Bf-cycles] GPU future<br>> <br>> Hi,<br>> <br>> On Sun, Dec 9, 2012 at 3:10 PM, Juan Pablo Scotto<br>> <juanpscotto@hotmail.com> wrote:<br>> > But is it posible to implement, one feature that gives you the posibility to<br>> > choose what objects in a scene can be rendered in CPU or GPU?.<br>> > For example if you are making a scene with grass with hair and other<br>> > objects. You can render the grass with cpu and the other objects in GPU.<br>> > That will be very usefull for the people that has a GPU with less Vram than<br>> > RAM.<br>> ><br>> > I'ts just and opinion. What do you think about? Is it totally crazy the<br>> > idea?<br>> <br>> Hybrid rendering where you split shading and ray intersection can be<br>> done as shown by Luxrender. Intersecting some objects and the GPU and<br>> some on the CPU is possible in principle, but it gets tricky and I'm<br>> not so sure about the advantages over just doing all intersections on<br>> the CPU then, speed gains might be minimal.<br>> <br>> For Cycles I don't see hybrid rendering as a priority, I think there's<br>> many other optimizations that should be tackled first.<br>> <br>> Brecht.<br>> _______________________________________________<br>> Bf-cycles mailing list<br>> Bf-cycles@blender.org<br>> http://lists.blender.org/mailman/listinfo/bf-cycles<br></div> </div></body>
</html>