prepass to a separate color texture do alpha blending in screen space.
Still an issue here on Blender 2.81 beta from 2019-10-12. I'm glad I've found this task, I've disabled auto-depth and it is smooth as usual.
Added retopology panel
Removed hidden wire drawing code
Unable to redo this in 23b3b5bc76d0b250b1547bbb3fa991081fd6fe0f.
Maybe you could provide precise steps in text form? That is easier to follow than a video sometimes.
Please adjust your attitude. The report was set to Confirmed status. He just said he's checking the issue.
Really？But I can reproduce it here every single time!
Mon, Oct 14
Some excuses. In 2.79 it was a normal hide. Can you complete the task normally? It's 2019 year, and you say that it’s normally done, that's funny
More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
This is actually working in wireframe. It is X-Ray, where this starts behaving differently [X-Ray with alpha < 1 will not paint the overlays in the occluded areas]
I can confirm the issue.
Fri, Oct 11
Agree. We should disable clipping in these cases.
Thu, Oct 10
Wed, Oct 9
I enabled the warnings now for the most common problem, which is old Intel drivers. That's the case I consider most important for 2.81.
Tue, Oct 8
@steve miller (winnertakesteve) yes I also am using Edit Mode and Eevee together here. I will do further testing to see if the recent fix has affected this issue or not.
also having this issue. can't seem to make anything 100% reproducible, but the common factors seem to be eevee in edit mode, and trying to either perform vertex selections (such as clicking 'L' over a mesh) or connecting image nodes to a principled shader.
Mon, Oct 7
I am also experiencing the same issue, even after the above patch.
Since you are able to use Blender again I'm going to close this report. Please don't re-use this report for other bugs.
I haven't noticed it so far with my Intel laptop, but I'm not using Eevee much on it or it may be AMD driver specific.
Sat, Oct 5
Reverted that initial AMD test in rB4707f1982ddb: Fix T70568, T70570: wrong AMD driver warning dialog. Not sure if there is something wrong in that specification or the testing mechanism, we'll have to check next week.