12-31-2020, 06:42 AM
Hi Kresimir,
I think I've found something. I've noticed from the cache filedates, and hence recall, that I had stopped my default sim and continued it the next day at the same frame that it's crashing on during wt rendering. Possible with v4.x that something created a bug in the cache at the start/stop point that would cause it to have weird data in the first continued sim frame?
So to recap:
--default simmed from 1-116, stopped it properly in morning
--next evening, continued default sim up to around 250
--then ran wt simm over the course of several nights, starting and stopping
--then when rendering it always crashes at frame 116 of the wt cache, which was a stopping point for the default cache.
I think I've found something. I've noticed from the cache filedates, and hence recall, that I had stopped my default sim and continued it the next day at the same frame that it's crashing on during wt rendering. Possible with v4.x that something created a bug in the cache at the start/stop point that would cause it to have weird data in the first continued sim frame?
So to recap:
--default simmed from 1-116, stopped it properly in morning
--next evening, continued default sim up to around 250
--then ran wt simm over the course of several nights, starting and stopping
--then when rendering it always crashes at frame 116 of the wt cache, which was a stopping point for the default cache.