After rBb9febb54a492, the evaluated mesh from a curve is now presented
to render engines as a separate mesh object. This code still assumed that a
curve object itself could have an evaluated mesh. That is still true for
surface objects and metaballs, which don't use geometry sets yet.
Details
Details
Diff Detail
Diff Detail
- Repository
- rB Blender
- Branch
- fix-eevee-motion-blur-crash (branched from master)
- Build Status
Buildable 18761 Build 18761: arc lint + arc unit
Event Timeline
Comment Actions
There are two other tests like this, I think all can be changed?
source/blender/draw/engines/eevee/eevee_engine.c: if (ELEM(ob->type, OB_MESH, OB_CURVE, OB_SURF, OB_FONT, OB_MBALL)) {
source/blender/draw/engines/eevee/eevee_render.c: if (ELEM(ob->type, OB_MESH, OB_CURVE, OB_SURF, OB_FONT, OB_MBALL)) {
source/blender/draw/engines/eevee/eevee_materials.c: if (ELEM(ob->type, OB_MESH, OB_CURVE, OB_SURF, OB_FONT, OB_MBALL)) {Comment Actions
Also perhaps this one?
source/blender/draw/engines/workbench/workbench_engine.c: if (ELEM(ob->type, OB_MESH, OB_CURVE, OB_SURF, OB_FONT, OB_MBALL, OB_POINTCLOUD)) {Comment Actions
- Fix more assumptions that curve objects have meshes
Thanks, I found a more too, by searching OB_CURVE in eevee* and workbench* files.
I'll say, this was easier to fix in Cycles, the distance from Blender code probably helped.
EDIT: Oops, I only saw an email from your second comment. Thanks for finding those.