My bad! Gonna wait till the daily build updates
Wed, Aug 19
The latest master c65c66320fc8 doesn't solve this for me. Still having this issue
Aug 16 2020
Aug 1 2020
Jul 9 2020
The strange thing is that if you have an array modifier on the plane, it will render the instanced object in the viewport in edit mode.
Jun 5 2020
May 21 2020
It seems that it's tied to clipping values. You can play around with those and it resolves the issue
Mar 2 2020
Jan 28 2020
Oh well, i liked the visual indication of the mode you were in (and the crosshair itself)
Jan 2 2020
Oct 29 2019
Sep 18 2019
Sep 10 2019
Hello! So i created another task like this, but it was for meshes. https://developer.blender.org/T65893
Sep 9 2019
Sep 3 2019
Guys, can this get fixed? It's been in for a very long while already.
Jul 12 2019
Good time of day, @Jeroen Bakker (jbakker)!
This bug is still persistent for curves in edit mode with same conditions, but it is indeed fixed for meshes. Maybe it's gonna be as easy for curves to fix?
Jun 17 2019
May 24 2019
May 23 2019
@Brecht Van Lommel (brecht)
I thought it would be easier to show all of it in 1 file because it all seems related. So there's a problem with CTRL+A, curves with modifiers on them, and linked curves with modifiers on them. Do you think this covers it all or should i create another bug report?
May 22 2019
This is still broken, check out the sample file:
This is broken again
I'll tell you even more, nothing happens even if you use visual geometry to mesh on a mesh with modifiers.
May 20 2019
Here's a better sample file:
May 10 2019
Guys, i think you broke something with this fix :D check this thread out
May 9 2019
May 7 2019
May 4 2019
There's also something strange going on with linked curves (that share the same data), check this thread out https://developer.blender.org/T61184
May 3 2019
Should this be reopened, do you think? This problem is pretty huge i think (at least for my jewelry modeling workflow)
Apr 25 2019
You can find one file here https://developer.blender.org/T63871 (i created a new task for a new problem, this is related i think)
This still isn't fully resolved, even though curves are now behaving correctly with mirror/array modifiers, try link copying a curve (using Alt+D) which has a curve modifier on it and you'll see what i mean. The outline is drawn correctly but the mesh data itself is not, i think it's a depsgraph thing.
Apr 10 2019
Apr 5 2019
Feb 12 2019
There's also a problem with curve drawing with modifiers. For example, create a curve and add a mirror modifier to it, it's not drawn in the viewport
Feb 7 2019
Feb 4 2019
Jan 31 2019
Jan 30 2019
This is what i rather meant. The objects disappear from arrayed planes in edit mode (Plus try moving the plane, the instanced object isn't following it real time, updates only if you exit edit mode. 2.79 was realtime plus the objects are shown on modifiers)
Jan 29 2019
Mar 13 2018
Okay, guys, sorry, i think i found the problem. That's the Curve Tools addon, if you have the addon ribbon (named "Curve tools 2") rolled open in Tools panel (T), blender crashes. If you roll that scroll down (or close the tools panel), you can undo as much as you want, just as long as you don't see curve tools opened in tools panel.
Mar 5 2018
Mar 2 2018
Feb 12 2018
It's not only failing in coplanar geometry, obviously. For example, i needed to boolean that part, bmesh fails any way i try it, carve solves it with 0 non-manifold edges. Take it as an example (in this particular case i wanted to fatten the prongs), i have lots more of those. I'm using blender for jewelry production
this is quite a change for me, actually, and i'm sure i'm not alone on this
Is there an easy way to let carve solver stay as it was? Keep bmesh as a main target, but have carve as a backup? Or is it too much a job maintaining the code?