Hiding edited object has never been allowed, no bug here, this is expected behavior.
I can confirm that in 2.79 official release 64bit that's is the behaviour. In Edit Mode you cannot hide the object currently being edited but you can hide other objects in the scene while you're in Edit Mode. It was the same in 2.78 and previous versions.
i attached video related to this error
please check if this is a bug above,in other programs,i can hide objects in layer in edit mode.
To add to what Yury included above, if the models use Weight Paint Groups to determine the values for width and segments then multiple objects with different settings can be joined together.
Tue, Sep 19
I want to drop a few cents here about the related proposal I don't see mentioned here.
I remember cédric's proposal in rightclickselect for adding Bevel Segments value for Edges Data. It could be s great feature for non-destructive modeling with a better bevel modifier.
Thanks, can confirm that that happens now.
Mon, Sep 18
Hm, going back and retesting there seems to be a difference between enabling the debug option or not.
I agree it is weird, though sometimes things like this happen because it is impossible to simultaneously set the bevels for all edges to what they should be mathematically (due to interactions with the bevels at other edges, and the code tries to "compromise" in cases like that). But I need to investigate more to see if that's what is going on here.
Sat, Sep 16
This is fixed by rB892d304dedb60891d9e0b3091eceecb163644215
Thu, Sep 14
Closing since the near clip here is such an extreme value, the file doesn't even show properly in 2.8x.
Strange, it works fine for me on Linux. I will try on Windows when I get a chance and see if I can reproduce there.
Assigning to @Howard Trickey (howardt)
Note this file has a cyclic dependency, loading the file doesn't calculate booleans because of this.
Documenting this as a known limitation:
Wed, Sep 13
Yes sorry. I was really tired when I wrote this post, still am. Don't know how I managed to confuse the two. Sorry again.
Just for info. I opened one of my older files created in 2.78. Bevel in percent mode worked fine. It seems there's an issue with new edition of the file format?
The issue is with Bevel not Boolean.
please tell other people about this workaround and let other people know about it.
thank you very much! - this setting which is to do with viewport clipping solved my issue with knife tool.
@Howard Trickey (howardt) Thanks for such a quick reply! I agree with @michael knubben (michaelknubben). The only thing that really need to be as much centre is the edge seam. as that way it would be really easy to just reunwrap the mesh and avoid any issues with those unwanted tears. The ideal would be that the UVs wouldn't tear in the first place but it's not a big deal to just reunwrap the mesh with the new seams at the centre of the bevels. I wonder it it would at all be possible to have an option within the modifier on how it would handle edge data. That would be perfect act avoid any worries about being consistent with how edge data is treated, just let the user decide whether edge seam is split or center, perhaps add an offset so that if the bevel has a segment of 1 the user could offset which side the seam would move to. Just an idea, in reality i would be very happy with just a change that put seams in the centre.
Maybe it could be usefull to clean bevel weight when applying the bevel modifier to avoid this kind of result ?
Glad to see this being discussed here. I agree with @Jac Rossiter (Jakro) that you'd want UV seams in the middle of the bevel whenever possible. Now ofcourse that's not the case with an odd number of edges, but it's still an ideal to strive for in my opinion.
As for other edge attributes, it seems to me that hard edges & bevel weight make sense being on the outside of the bevel, so as to avoid compromising the bevel's curvature (either by bevel the middle of it, or by having a sudden gap in normal continuity there).
Thanks for your suggestion, Jac. And thanks for the clear examples in your rightclickselect post. While it seems strange to me to have a different treatment of seams for odd and even numbers of segments, I can understand your argument. What about other edge attributes (e.g., smoothness; bevel weight; ...). In your opinion, which edge attributes should go exclusively to the middle edge, which should go to all of the edges, and which should go to the outer edges of a beveled edge?
@Campbell Barton (campbellbarton), mind having a look here? Thanks! :)
Hi Howard, I've been running into some trouble with the bevel modifier over the last week as I move more towards VFX. I am using the Bevel modifier to produce my control loops for Subd modelling and UV as I go, ensuring that the bevel modifier has an even number of segments so that any seams I have defined will remain. But the seams don't remain when the modifier is applied. I have written up a post about this on rightclickselect to argue for a change in behaviour but have since realised I would be much better off voicing my thoughts here.
Regardless here is the post: https://rightclickselect.com/p/general/Xvbbbc/preserve-uv-seams-when-applying-a-bevel-modifier-with-an-even-number-of-segments
It looks like it is relative to View Clipping.
Start value is at 0.001. If you increase it or switch to an orthographic view, knife is working correctly.
please see my video,about this issue,i recorded my work by cam studio,to make it easy for you to see what happens when i cut along polygon edge.
Tue, Sep 12
I opened your file and used the knife to cut across faces on the mesh.
Please give an exact list of steps that fail - even if those steps seem obvious to you.
Campbell Barton - what can i do in this case? - What did you do that blender was working without any issues,when you used knife tool.I used and it was creating duplicated vertexes.
Mon, Sep 11
The report has no steps to redo the error, this is needed to investigate.
The file with the problem is not enough.
Sat, Sep 9
i have problem with knife tool,when i try to cut polygonal object from one edge to vertex or face of polygon.Knife tool creates duplicated vertices and it does not always create new edge.
Tue, Sep 5
Thu, Aug 31
Confirmed also in current master, looks like only some modes fail here, weird bug. ;)
Aug 20 2017
This can be resolved by zooming in with the scroll wheel as far as possible.
Aug 18 2017
I can confirm this fixes the clamp function in all bevel modes except for 'percent' - in that case the bevel still sometimes stops short.
Aug 14 2017
The problem with inconcistancy when the selected face have an ended sharp edge is solved from what I can see :-D Thank you!