[Bf-committers] Radiosity Engine

[Ton Roosendaal]

Hi,

It was written in '94 according the latest tech specs then (siggraph  
proceedings) as a separate tool. In '98 cleaned up and added to  
Blender. In these days realtime textures where not a feature to expect  
at the desktop... vertex colors were the way to go.

Although I agree it is outdated, it's also one of the code parts I'm  
really satisfied with. It is relatively clean code, and well  
structured. The conversion from regular mesh to radiosity-ready meshes  
is complex and handled pretty good. ("crappyfying" = adaptive  
hierarchical subdivision)
Integration with Blender itself could be improved quite some... just a  
lack of time, plus the original design of Meshes in Blender don't fit  
this, something we suffer from in more ways.

-Ton-




On Saturday, Jun 7, 2003, at 00:21 Europe/Amsterdam, instinctive new  
media wrote:

>
>
> Hello!
>
> I've been working with Radiosity quite a lot recently, and one
> incredibly obvious question came to mind:
>
> Why does the radiosity engine not SIMPLY use 'Add' textures instead
> of crappifying the mesh and then using vertex colors?
>
> You could continue to use your normal meshes, no complex  
> layer-switching,
> copying, replacing meshes, plus you could _ANIMATE_ (yes, that's right)
> the radiosity light by simply animating the texture.
>
> I don't get this! Why did it get coded this way? :)
>
>
> | alexander ewering           instinctive new media
> | ae@instinctive.de       http://www.instinctive.de
> |
> | fon: +49-2393-220558         fax: +49-2393-220559
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton@blender.org  
http://www.blender.org