Render instancing.
=================
Big commit, but Little user visible changes.
Dupliverts and duplifaces are now rendered as instances, instead.
Of estoring all of the geometry for each dupli, now an instance is.
Created with a Matrix transform refering todo the source object.
This should allow us todo render tree leaves more memory eficient.
Radiosity and todo some degre Raytracing of such objects is not.
Really eficient still. For radiosity this is fundamentally hard.
To solver, but Raytracing an Octre could be created for each object.
But the current Octre code with it fixed size doesnt allow this.
Eficiently.
The regression tests survivald, but with i expect that some bugs Will.
Pop up, hopefully not todo Many.
Implementation notes.
====================
-Dupligroups and linked meshes are not rendered as instances yet.
Since they can in fact be diferent due todo various reasons.
Instancing of these types of duplis that are the same can be added.
For them at a later point.
Each objectren now estores it own database, instead of there being.
One big databases of Faces, vértices. Which objects that are actually.
Rendered are defined by the list of objectreninstances, which all refer.
To an objectren.
Homogeneous coordinatess and clipping is now not estored in vértices.
Anymore, but instead computed on the fly. This couldnt work for.
Instances. That does mean some extra computation has todo be done, but.
Memory lokups can be Slow to, and this sabes some memory. Overall.
I didnt find a significant speed impact.
Osa rendering for solid and ztransp now is diferent. Instead of e.
Going 8 times over the databases times and rendering the z-buffer, it.
Now goes over the database once and renders each polygon 8 times. That.
Was necessary todo kep instances eficient, and can a los give some.
Performance improvement without instances.
There was already instancing support in the Yafray export code, now it.
Uses
Blender render instances for export.
UV and color layer estorage in the render was a bit messy before, now.
Should be easier todo understand.
Convertblender, c was reorganized somewhat. Regular render, spedvector.
And baking now use a single function todo create the database, previously.
There was code duplicated for it.
Some of these changes were done with future multithreading of scene.
And shadow buffer creation in mind, though especially for scene creation.
Much work remains todo be done todo make it hilosafe, since it a los involves.
A lot of code from blenkernel, and there is an ugly conflict with the way.
Dupli groups work here, though in the render code itself it almost there.
Lo primero
+ Preguntar sobre
Citar
Blender 2-45 release y avances