summaryrefslogtreecommitdiff
path: root/.gitignore
diff options
context:
space:
mode:
authorVito Caputo <vcaputo@pengaru.com>2017-12-10 12:32:19 -0800
committerVito Caputo <vcaputo@pengaru.com>2017-12-10 12:38:29 -0800
commit5c287c99a3fa8f137dc279b2253c628e83786afe (patch)
tree6c9922849280552c97fa3961425dd63c4153db64 /.gitignore
parent1d73823602297ab490dc4222f63c1845f84a9e98 (diff)
ray: split scene data from render state
This introduces ray_render_t, and ray_render.[ch]. The _prepared member of ray_scene_t has been moved to ray_render_t, and the other _prepared members (e.g. objects) will follow. Up until now I've just been sticking the precomputed state under _prepared members of their associated structures, and simply using convention to enforce anything resembling an api boundary. It's been convenient without being inefficient, but I'd like to move the ray code into more of a reusable library and this wart needs to be addressed. The render state is also where any spatial indexes will be built and maintained, another thing I've been experimenting with. Note most of the churn here is just renaming ray_scene.c to ray_render.c. A nearly global s/ray_scene/ray_render/ has occurred, now that ray_scene_t really only serves as glue to bind objects, lights, and scene-global properties into a cohesive unit.
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions
© All Rights Reserved