Treewarden opened this issue on Feb 24, 2004 ยท 25 posts
layingback posted Fri, 27 February 2004 at 11:29 AM
Just a guess, but perhaps it's related to this fix: "Shadow map memory is now properly freed after calculating each frame." If it was previously effectively using a fresh copy of the "Shadow map memory" each time, then it wouldn't have matter whether it was cleared or not... Now it does.