- User Since
- Jul 22 2008, 10:04 AM (551 w, 4 d)
Dec 10 2018
Just chiming in here as the OP: renaming is_dirty_xxx to recalculate_xxx without negating the value would seem to just as confusing to me (e.g. moving a camera would trigger with recalculate_geom set to True). But maybe I'm misunderstanding what exactly the flags are supposed to signal to downstream users of depsgraph updates (e.g. a render engine script). I originally expected the flags to indicate for which objects the local (downstream) copy of the scene needs to be updated to match the current depsgraph. But it seems that that is a secondary usage, as the flags actually specify which parts of the depsgraph itself need updating. Which is surprising, because what if the downstream script does not handle the updated depsgraph part and therefore doesn't take any action on them to update?
Dec 9 2018
well, no shading at all, but that's to be expected since you don't seem to have implemented any drawing in view_draw yet.
This is the conventional terminology in computing. Read "is dirty" as meaning "needs cleanup" or in this case, "needs updated".
Hmm, more weird behaviour:
Dec 5 2018
Dec 3 2018
@LazyDodo (LazyDodo) So just to get some clearity, the known CUDA bug you mentioned only applies to 2.80 (while 2.79 used different CUDA code and isn't affected)? And it's now up to NVIDIA to fix this? How does that go together with Blender's apparent policy of trying to keep the used CUDA version low, so older GPUs can still be used? NVIDIA won't release any fix in CUDA 9.x anymore, I suspect.
Feb 5 2018
(Ahum, submitted too soon :))