Timeline for Crashing with a cached simulation nodes setup
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 20 at 11:06 | vote | accept | Nickh129 | ||
| May 20 at 9:50 | answer | added | Nickh129 | timeline score: 1 | |
| Apr 10 at 13:47 | comment | added | Nickh129 | I should mention that overall I'd rather use Eevee to render a final version as it's obviously much faster, and I have ~5500 frames to output | |
| Apr 10 at 13:42 | comment | added | Nickh129 | So fwiw I've done some more tests. I went back to an earlier version of this file, which was set up to render in Cycles, and uses Set Point Radius to render the points as spheres, rather than Instance on Points as I've done in the above Eevee setup. The original file has about 1.9m points, and the cached .blobs are ~160Mb per frame. This doesn't crash, and displays pretty much in realtime in the viewport. The Eevee version, instancing spheres on a point cloud of ~160k points, won't even load the cache without crashing Blender. How can I render out points directly in Eevee? | |
| Apr 10 at 9:15 | comment | added | Nickh129 | Thanks. Is this a CPU issue though? It averages about 1-2 seconds per frame it's simulating, and it only crashes when trying to retrieve the baked data from the cache. Plenty of free space on the cache ssd too | |
| Apr 9 at 19:15 | review | Close votes | |||
| Apr 10 at 9:16 | |||||
| Apr 9 at 18:52 | comment | added | Emir | Probably this is the answer but not a positive one blender.stackexchange.com/questions/102149/… | |
| Apr 9 at 18:30 | history | asked | Nickh129 | CC BY-SA 4.0 |