Mon, Feb 18
Thu, Feb 14
Weird. Was looking for quite some time =\ Thanks!
There will be more optimizations.
@Sergey Sharybin (sergey): file was there in the report (made this more visible now...)
Please always attach .blend file which demonstrates the issue.
At the moment my demo scene with some modifiers is at 5 fps in version 2.8.
In v2.79 its faster and runs at about 8 fps.
Wed, Feb 13
Thank you for your effort. It works now.
@Sergey Sharybin (sergey), can you review this?
This appears to be solved in the latest builds.
@Campbell Barton (campbellbarton) : is this OK to stay on your desk?
AddressSanitizer: heap-use-after-free P911
Can reproduce here
Also I don't know if I should write here or create another task, but I can't even insert keyframe on viewport visibility, while I can insert one for render visibility. It will show an error as shown in the screenshot:
If some people with earlier build can insert keyframe on viewport visibility, even if they don't update correctly, is this one more regression from earlier build or intended to prevent crash? I've tried this on few builds that I still have, with the earliest build on 552b2287db86 (01/02/2019) and the latest build blender-2.80-d3870471edd7-win64 (12/02/2019).
I've just discovered this problem. I don't really understand the script workaround, but I know it's something with the internal code not updating. Because if I **move** a keyframe of Disable Render channel from the object, it will be updated, but then stays like the last render until I move any keyframe of Disable Render channel again.
Tue, Feb 12
There were few things wrong in dependency graph and instancing code. Should be fixed now. Thanks for the report, closing.
BLI_assert failed: /blender/blenkernel/intern/DerivedMesh.c:2181, mesh_get_eval_final(), at 'DEG_debug_is_evaluating(depsgraph) == 0'
Mon, Feb 11
doh! thats a facepalm on my side... thx @Bastien Montagne (mont29)
BKE_modifier_get_evaluated_mesh_from_evaluated_object() is doing plain rubbish in EditMode case… That was probably true at the time it was written, but we do have valid final and deformed (aka cage) evaluated meshes in BMEditMesh, nowadays. So fix is actually quite simple. ;)
I've the same problem.
I believe that being able to control visibility on viewport is very important.
This was indeed working fine in 2.79.
In 2.8 it updates fine if you go back to objectmode.
Once you enter editmode on the plane, I am getting this here:
ERROR (bke.modifier): /blender/source/blender/blenkernel/intern/modifier.c:385 modifier_setError: Cage verts changed from 162 to 81
So looks like BKE_modifier_get_evaluated_mesh_from_evaluated_object doesnt really give us fully evaluated mesh (at least not for objects with generative modifiers in editmode)?
Sat, Feb 9
Tue, Feb 5
Fri, Feb 1
Thu, Jan 31
Wed, Jan 30
@Sergey Sharybin (sergey): mind sharing your wisdom?
Tue, Jan 29
I allready had this problem in a view projects.
Thank you @Fletcher Graham (fletchgraham) for your suggestion on forcing blender to update through python.
To get around the issues with keyframing visibility in 2.80, I used a script instead.
Mon, Jan 28
Fri, Jan 25
Can no longer reproduce the issue. Considering it solved by all the recent changes.
If the issue is still happening make a new report with updates file and steps to reproduce the issue.
Thu, Jan 24
I agree, we need better docs for this.
Brecht, your suggestion works. Thanks for the input!
Jan 24 2019
Well that's good that it's not a bug. This should be mentioned in the Python API section of the release notes. For addon devs like me there is no mention that you need to use the engine to set the frame now instead of the scene. Then I waste you guys' time posting reports on bugs that aren't bugs.
For rendering, use engine.frame_set() instead of scene.frame_set() to change the frame.
Here's a stripped down version of the render plugin. Instead of exporting items it just prints matrix_world
Jan 23 2019
Thanks Philipp. I’ll get a scene and mock-up to you later today
Just to make this a little simpler for everyone looking at this:
Jan 22 2019
note: to get it to crash easier, lower the number of particles to 100 in the file provided with this report.