Visually broken/stepped wireframe in object mode (regression) #77130

New Issue

Vyacheslav Kobozev · 2020-05-28T16:12:26+02:00

2020-05-28 16:12:26 +02:00

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87

Blender Version
Broken: version:
2.83 (sub 17), branch: master, commit date: 2020-05-27 16:03, hash: 79e529c5ec
2.90 (sub 4), branch: master, commit date: 2020-05-27 18:04, hash: d7282537f0
Worked:
blender-2.83-e8dd8c2829f3-windows64

Short description of error
Edit mode looks properly. But object mode have stair on circle mesh

without antialiasing it looks worse

previous builds:

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87 **Blender Version** Broken: version: 2.83 (sub 17), branch: master, commit date: 2020-05-27 16:03, hash: `79e529c5ec` 2.90 (sub 4), branch: master, commit date: 2020-05-27 18:04, hash: `d7282537f0` Worked: blender-2.83-e8dd8c2829f3-windows64 **Short description of error** Edit mode looks properly. But object mode have stair on circle mesh ![39601106.jpg](https://archive.blender.org/developer/F8560162/39601106.jpg) without antialiasing it looks worse ![39633310.jpg](https://archive.blender.org/developer/F8560174/39633310.jpg) previous builds: ![39611606.jpg](https://archive.blender.org/developer/F8560161/39611606.jpg)

Vyacheslav Kobozev commented

2020-05-28 16:12:26 +02:00

Added subscriber: @Vyach

Alaska commented

2020-05-29 03:49:51 +02:00

Added subscriber: @Alaska

Alaska commented

2020-05-29 03:49:51 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Alaska commented

2020-05-29 03:49:51 +02:00

Can confirm while testing with these Blender versions:
2.83 f772a4b8fa (2020-05-26 22:42)
2.83 79e529c5ec (2020-05-27 16:03)
2.83 ff1040c6fe (2020-05-28 11:42)
2.90 2deb6c5177 (2020-05-28 18:34)
On Windows 10 with a GTX 1050Ti with driver 445.87.

I will update the task description along with look at recent commits to see if I can pin point the commit that caused the issue. At the moment I haven't figured out how to bi-sect builds.

Can confirm while testing with these Blender versions: 2.83 `f772a4b8fa` (2020-05-26 22:42) 2.83 `79e529c5ec` (2020-05-27 16:03) 2.83 `ff1040c6fe` (2020-05-28 11:42) 2.90 `2deb6c5177` (2020-05-28 18:34) On Windows 10 with a GTX 1050Ti with driver 445.87. I will update the task description along with look at recent commits to see if I can pin point the commit that caused the issue. At the moment I haven't figured out how to bi-sect builds.

Alaska commented

2020-05-29 03:58:52 +02:00

39aa122a0e is most likely the cause. The commit says

HACK: to avoid loosing sub pixel object in selections, we add a bit of randomness to the wire to at least create one fragment that will pass the occlusion query.
TODO(fclem) Limit this workaround to selection. It's not very noticeable but still...

39aa122a0e is most likely the cause. The commit says ``` HACK: to avoid loosing sub pixel object in selections, we add a bit of randomness to the wire to at least create one fragment that will pass the occlusion query. TODO(fclem) Limit this workaround to selection. It's not very noticeable but still... ```

Alaska commented

2020-05-29 03:59:55 +02:00

Added subscriber: @fclem

Alaska commented

2020-05-29 03:59:55 +02:00

@fclem Are you able to comment on this?
Is the cause actually this commit?
If it is the commit, what's the plan going forward? Temporarily revert the commit or leave it in there and fix it at a later date?

@fclem Are you able to comment on this? Is the cause actually this commit? If it is the commit, what's the plan going forward? Temporarily revert the commit or leave it in there and fix it at a later date?

Chingiz Jumagulov commented

2020-05-29 04:37:37 +02:00

Added subscriber: @MeshVoid