Maniphest T63940

Unable to select faces, edges or vertices while in any solid shading mode. (wireframe selections are working for me)
Closed, Resolved

Assigned To
Germano Cavalcante (mano-wii)
Authored By
Bo Dodge (mgfxer)
Apr 27 2019, 5:59 PM
Tags
  • BF Blender
Subscribers
Bo Dodge (mgfxer)
Brecht Van Lommel (brecht)
Germano Cavalcante (mano-wii)
Jacques Lucke (JacquesLucke)
Zhiming Wang (wrongre)

Description

System Information
Operating system: Darwin-16.6.0-x86_64-i386-64bit 64 Bits
Graphics card: NVIDIA GeForce GTX TITAN X OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.18.5 378.05.05.15f01

Blender Version
Broken: version: 2.80 (sub 58), branch: blender2.7, commit date: 2019-04-21 20:30, hash: rB797539e76ccf
Worked: (optional)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

When I enter edit mode on any given mesh, I'm unable to select vertices faces or edges unless I am in wireframe mode. I'm testing it with all three context for edges, faces or vertices, and all the selection arrow tools, but nothing works. Eevee, lookdev, and workbench all behave the same. I'm unable to make any selection unless I use "select all", or as I mentioned once I switch to wireframe mode, selection behave normally.. It's working normally on other mac's I've tried it on, just this one has the problem I've seen some reports indicating it's the display driver, but I'm afraid this is the best existing driver for my system. Everything is working normally in other software like redshift, octane, cinema 4d, zbrush etc. . I've tried deleting preferences and resetting keyboard prefs to default 2.8, and also using "factory reset", but the problem persists. I'm not sure what else to include in this report.

Related Objects

Mentioned In
T67508: Selecting Vertices Edges and Faces not working in any solid shading mode/Constant Chrashes rendered mode (Evee and Cycles)
Mentioned Here
rBe0879517025f: Possible fix for T63685: macOS edit mode selection not working on second display

Event Timeline

Bo Dodge (mgfxer) created this task.Apr 27 2019, 5:59 PM
Bo Dodge (mgfxer) added a comment.Apr 27 2019, 7:23 PM

Just as a side note..all eevee viewport effects are working fine. Cycles is rendering Cuda with all of my gpus no problem. If it is the fault of the display driver, it's strange that everything else just works normally. I realize this problem will be hard to reproduce on a system that is already supported/working..Thanks for checking.

Jacques Lucke (JacquesLucke) lowered the priority of this task from 90 to 30.Apr 29 2019, 12:38 PM
Jacques Lucke (JacquesLucke) added a subscriber: Jacques Lucke (JacquesLucke).

Did this ever work in Blender 2.80 before, or is it a new problem?

Bo Dodge (mgfxer) added a comment.Apr 29 2019, 3:05 PM

I've only been testing blender 2.8 for the last couple of weeks. It has been the same problem in the 5 or 6 builds I've tested. I'd be willing to go back and try several much earlier builds if I had access to them, but I don't see or find links for them. Is there a link page sort of like this one for previous 2.8 beta builds? https://developer.blender.org/diffusion/B/tags/master/

Jacques Lucke (JacquesLucke) added a subscriber: Brecht Van Lommel (brecht).Apr 29 2019, 3:14 PM

Not sure if the builds are stored somewhere... (@Brecht Van Lommel (brecht) ?)

Zhiming Wang (wrongre) added a subscriber: Zhiming Wang (wrongre).May 7 2019, 9:04 AM

I have the same problem.

my Mac mini is connecting two monitor now, one is powered by Intel UHD Graphics 630, the other is powered by AMD Radeon RX590.
On AMD monitor, I have the same problem, but on the Intel monitor, all functions are working normally.

further more, on AMD monitor, the default Shading layout, I have two VERY BIG sample spheres on the screen.

Germano Cavalcante (mano-wii) added a subscriber: Germano Cavalcante (mano-wii).May 10 2019, 3:44 PM

It may seem unrelated, but the `Snap Utilities Line' addon uses a similar solution to the selection when it snaps.
Could you test this addon to see if the problem is seen there too?
The addon already comes along with Blender, just enable it and test the new Tool that appears in edit mode.
Snap points should be displayed when you move the cursor over an object.

Bo Dodge (mgfxer) added a comment.May 11 2019, 2:46 AM

@Germano Cavalcante (mano-wii) I tested the Snap Utilities Line as you suggested and everything appears to work normally, snap point verts appeared, the line tool was able to draw new lines, in short it works. Additionally I see the faces get highlighted as you hover over the object. I hope this means a solution is possible. Thank You

Germano Cavalcante (mano-wii) added a comment.May 12 2019, 12:58 AM
In T63940#676368, @Bo Dodge (mgfxer) wrote:

@Germano Cavalcante (mano-wii) I tested the Snap Utilities Line as you suggested and everything appears to work normally, snap point verts appeared, the line tool was able to draw new lines, in short it works. Additionally I see the faces get highlighted as you hover over the object. I hope this means a solution is possible. Thank You

Actually, I thought it would not work.
If it didn't work I would send some python scrypts to you test in the Blender text editor.
The fact that it works indicates however that the problem can be simple to solve. But a developer need to replicate the bug to investigate and understand better what is happening.

Zhiming Wang (wrongre) added a comment.May 13 2019, 3:29 AM
In T63940#676062, @Germano Cavalcante (mano-wii) wrote:

It may seem unrelated, but the `Snap Utilities Line' addon uses a similar solution to the selection when it snaps.
Could you test this addon to see if the problem is seen there too?
The addon already comes along with Blender, just enable it and test the new Tool that appears in edit mode.
Snap points should be displayed when you move the cursor over an object.

Hello,
I've tried the "Snap Utilities Line" addon, but nothing happened, the result is the same as before.
Thank you.

Philipp Oeser (lichtwerk) raised the priority of this task from 30 to 80.May 25 2019, 1:30 PM
Germano Cavalcante (mano-wii) added a comment.EditedJun 25 2019, 9:50 PM

Some changes have been made in this area, is this still a issue?

Bo Dodge (mgfxer) added a comment.Jun 26 2019, 12:47 AM

It's working! I tested all of the select arrow/box/circle/lasso tools in each context for vertex, edges, faces, and it's all working now on my system. I am very grateful to have the issue fixed. Thank You!!!

Germano Cavalcante (mano-wii) changed the task status from Unknown Status to Resolved.Jun 26 2019, 1:11 AM
Germano Cavalcante (mano-wii) claimed this task.

Good news :)
Probably fixed by rBe0879517025f