- User Since
- Oct 15 2016, 12:35 AM (148 w, 6 d)
Sat, Aug 10
Thu, Aug 8
Hi, this is the author of the FLIP Fluids add-on. The bug that causes render crashes has been reported here: T60094
Tue, Aug 6
Tue, Jul 30
Thu, Jul 25
Note: render_pre and render_post handlers will not cause a crash in this issue since these are only called during render. I had tested the frame change and render handlers in issue T60094 which all resulted in a crash.
Jul 22 2019
I have recently received a few reports from users of the FLIP Fluids addon that this issue is now resulting in crashes rather than the static exported Alembic caches reported in the original post. I have just had a chance to test this on the most recent Blender 2.80 build (02c5c091dfd6) and have been able to confirm this crash using the .blend file and instructions in the original post.
Jul 16 2019
From FLIP Fluids user reports regarding this render crash issue in Blender 2.80, it seems that the Lock Interface workaround works for roughly half of the users. I have tested systems where locking the interface helps reduce render crashes and some systems where this does not work. In my experience, the render crash frequency increases as the amount of mesh geometry increases.
Jun 14 2019
I have encountered an issue similar to this in the FLIP Fluids addon using Blender 2.80 (hash 5e626e766459, June 13th 2019). The FLIP Fluids addon updates fluid mesh geometry in the frame_change_pre handler.
Jun 13 2019
I was testing the recent fix for T60136 and noticed that this issue will cause a crash when baking a rigid body cache. Here is a modified version of the .blend file in the original post to reproduce this issue:
May 17 2019
I am also experiencing this issue and am able to reproduce both crashes using the .blend file (Window 10 Home).
May 16 2019
Apr 30 2019
Mar 25 2019
Mar 4 2019
Developer of the FLIP Fluids addon here. I tested this .blend file, but was not able to reproduce the crash using build e5ab2b9c629e, blender2.8, 2019-04-01. The render result is just black images for me, so I am not sure if I am missing something in the .blend file.
Jan 4 2019
Jan 3 2019
Aug 30 2018
Here is the error message that I get when running from the command line:
Oct 5 2017
Thanks for the quick responses. I am able to reproduce this on Windows 10 (GTX 1070 8GB) with the same build, and also with using the 'Discombobulator' menu. I have attached a screencast of the issue: