[Bf-committers] Peach developer wishlist

[Brecht Van Lommel]

Well, it depends I think. First priority for Peach of course is that 
we can render a lot of hair and complex forest scenes, so that mostly 
requires rasterization/zbuffering/shadowmapping to improve, but I 
think we can also keep the long term evolution of the internal 
renderer in mind when making design decisions here. Depends how much 
work it all is to do more drastic changes to the renderer at this point.

Brecht.

Joe Eagar wrote:
> Afredo, I think the idea is for your renderer to basically act as a 
> zbufferer, probably with some simple built-in displacement shaders (one 
> for bump mapping and one for true displacement mapping I imagine, or 
> something like that) and support for processing subsurfs/nurbs 
> correctly.  So it might be worth it to work with brecht and ton on a 
> intermediary API for a zbuffer system that won't consume massive amounts 
> of RAM for things like hair.
> 
> A true renderman renderer we have the render API for; what peach needs 
> is an addition to the internal renderer, I think.
> 
> Joe
> 
> Alfredo de Greef wrote:
>> So I guess the peach team has given up hope to ever
>> see the micropolygon renderer? Not that it is no way
>> near a full solution to their problems of course. But
>> I haven't heard from anyone so I thought I could
>> stretch my time a bit more, I probably shouldn't have
>> done that I guess...
>> Of course, that I haven't shown myself ever since the
>> announcement probably didn't help either.
>>
>> In any case, if it still has a chance, one of the
>> things I just *had* to try to get working was the
>> shader compiler, which, at least in its current form
>> is probably even almost totally useless to Blender.
>> Anyway, that is sort of working now, but this means I
>> still have to tie up a few loose ends and do the
>> general clean up, then I can commit.
>>
>> (btw, about the HDR aliasing problem, as I mentioned
>> to broken some time ago, the way I dealt with that in
>> yafray is simply by clamping/tone mapping *before*
>> anti-aliasing, not afterwards. Of course, as broken
>> then remarked, I forgot about the compositor. If the
>> compositor had full access to all samples that would
>> solve that problem, but the data would then probably
>> be quite unmanagable, at least in its current form)
>>
>> Alfredo
>>
>>
>>        
>> ____________________________________________________________________________________
>> Sick sense of humor? Visit Yahoo! TV's 
>> Comedy with an Edge to see what's on, when. 
>> http://tv.yahoo.com/collections/222
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
>>   
> 
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
> 
>