MacOS: Edit Mode - vertex/edge/face selection is missing #79811

System Information
Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 580X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.15

Blender Version
Broken: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-14 20:53, hash: 199e308670
Worked: cb2565195e
Bisected to efc97b3919 as the breaking commit

Short description of error
Switching to edit mode - there is nothing to select. No vertices, edges or faces are displayed selected / unselected. Even with box select and move (G), nothing is happening.

Wire

Solid

Tested with Load Factory default.

Added subscriber: @FilipMond

#80021 was marked as duplicate of this issue

#80053 was marked as duplicate of this issue

#79927 was marked as duplicate of this issue

#79911 was marked as duplicate of this issue

#79904 was marked as duplicate of this issue

#79902 was marked as duplicate of this issue

#79863 was marked as duplicate of this issue

Added subscriber: @blenderrocket

I can confirm this, also on MacOS.

Added subscriber: @johjakob-3

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

Added subscriber: @ankitm

Added subscriber: @kostex

Have this issue on MAC as well but on LINUX the edit mode is also having issues I guess coming from the same origin.
On a cylinder making loop cuts for instance looks like this (made a photo.. using screenshot key refreshes the screen to image 2)

Added subscriber: @AnadinX

Added subscriber: @howardt

I confirm this happens on my Macbook Pro, MacOs version 10.15.6, graphics is Intel 630.
The breaking commit is e8dfe91767

Added subscriber: @JulianEisel

The last commit from 2.90 that was merged in the breaking commit was Fix constant lighting change in VR view when rotating head b3c08a3a0a9b·Julian Eisel (Severin) on Fri, Aug 14, 11:03 AM. I tried 2.90
at that commit and it worked. So something about the merge broke it; perhaps the interaction with all the changes to the CPU area by Clement in master on Thursday.

I didn't see how the merge commit could cause this, so I ran my own bisect. For me the first bad commit is efc97b3919 which makes much more sense to me.

b3c08a3a0a is a 2.90 branch commit. So the GPU changes from master are not included if you checkout this specific hash.

Added subscribers: @ChuckOcheret, @lichtwerk

Added subscriber: @fclem

Since there was chat about different bad commits, here's the tie breaker ;) : efc97b3919.
Intel HD 6000, macOS Mojave.
CC @fclem

Added subscribers: @FloridaJo, @RC12

Added subscribers: @headhacker, @Jewls

Added subscriber: @dfelinto

@JulianEisel can you re-confirm with latest master? There are plenty of artifacts that were fixed recently.

at my end.. latest master does nothing for the issue..

Yup, same for me, still not working with latest master

Added subscriber: @kuzey

Added subscriber: @WilliamReynish

Added subscriber: @ugosantana

Added subscribers: @cabada, @HooglyBoogly

Added subscriber: @brecht

Please fix this kind of regression as soon as possible before continuing with more refactoring.

This crashes for me on Linux in efc97b3919, but not in the commit before.

diff --git a/source/blender/gpu/intern/gpu_extensions.cc b/source/blender/gpu/intern/gpu_extensions.cc
index 8074e4b..d1f0adc 100644
--- a/source/blender/gpu/intern/gpu_extensions.cc
+++ b/source/blender/gpu/intern/gpu_extensions.cc
@@ -201,7 +201,7 @@ void GPU_get_dfdy_factors(float fac[2])
 
 bool GPU_arb_base_instance_is_supported(void)
 {
-  return GG.glew_arb_base_instance_is_supported;
+  return false;
 }
 
 bool GPU_arb_texture_cube_map_array_is_supported(void)

So presumably that code path is broken, and this can be tested and fixed on other platforms too.

There is still an issue with selection outline not displaying the right color.

Changed status from 'Confirmed' to: 'Resolved'

In #79811#1001942, @fclem wrote:
There is still an issue with selection outline not displaying the right color.

Nevermind, this was because my system was still suporting gl_BaseInstanceARB which on a platform that doesn't support glew_arb_base_instance_is_supported will never be the case.

well, that was very fast to close this..
on my mac when switching to edit mode this happens now...
blenderbug.mov

Changed status from 'Resolved' to: 'Needs Developer To Reproduce'

Folks in #80021 (Select and unselect bug) are also claiming it is not working still.

@fclem: mind checking again?

Added subscribers: @Kent-Davis, @iss, @jenkm, @mano-wii

Also #80094 (Various Asserts during selection) might be related

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

I can reproduce on the ARM devkit.

I'm experiencing the same behavior as in the video. What does seem to have changed is that if I display statistics I can see that selections are being made whereas before they weren't. The problem now appears to be only in the display (selections are visible for a moment and then appear to be overdrawn).

This issue was referenced by 949d92ad5d

Changed status from 'Confirmed' to: 'Resolved'

Confirming this is now fixed - many thanks!

NOW IT WORK FOR SURE.

Confirmed fixed in 2.91.0 - 396d39c6b9 on macOS Mojave 10.14.6.

This team really rocks - THANK YOU!

Yes me too and I do use MacOS 11 beta it work on Blender 2.91 Alpha as well.

Worked initially, but during a longer session it started to appear again?
hash: 92ad5d1f

bugreport.mov

@kostex can you provide a small test file?

should be in edit mode when opened.. just start selecting a face
TestFile.blend

@kostex the hash you mentioned doesn't exist in blender.org (92ad5d1f), could you please double check if the issue still happens with the latest available 2.91 build in builder.blender.org?

don't know why that hash was pasted wrong..
it's 949d92ad5d (my paste was a subset)

btw. I can't use the latest master (it's crashes constantly with a bus error?) don't know if that is related.. I've built against the latest related fix

With the default scene, just switch to the Compositing workspace and go back to Modeling,
and the Cube began to flicker as in the video above.

commit 479ce00809af30167a88525cdc7cddc704ed67ba (HEAD -> master, origin/master, origin/HEAD)

Operating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15

Just built from Master and I am not seeing any issues here, could be specific to hardware now?

`489b5790cf`

MacBook Pro (15-inch, 2019)
2.4Ghz 8-Core Intel Core i9
32GB RAM
Radeon Pro Vega 20 4GB

Intel UHD Graphics 630

Me iMac 27" 5K MacOS 11 beta

Radeon Pro 575:

Chipset Model:	Radeon Pro 575
Type:	GPU
Bus:	PCIe
PCIe Lane Width:	x16
VRAM (Total):	4 GB
Vendor:	AMD (0x1002)
Device ID:	0x67df
Revision ID:	0x00c4
ROM Revision:	113-D000AA-931
VBIOS Version:	113-D0001A1P-025
EFI Driver Version:	01.00.931
Metal:	Supported, feature set macOS GPUFamily2 v1
Metal Family:	Supported, Metal GPUFamily macOS 2
Displays:

iMac:

Display Type:	Built-In Retina LCD
Resolution:	5120 x 2880 Retina
Framebuffer Depth:	30-Bit Color (ARGB2101010)
Main Display:	Yes
Mirror:	Off
Online:	Yes
Automatically Adjust Brightness:	Yes
Connection Type:	Internal

Changed status from 'Resolved' to: 'Needs Developer To Reproduce'

This seems to only affect macs with AMD Radeon Pro GPUs. Is that correct? I could not reproduce on Mac + intel iris graphics 6100.

Mine is a AMD Radeon R9 M395X 4 GB
with the issue..

After @fclem resolved, I can't reproduce it. It's all fine here.

MacOS 10.5.4
Intel Iris

The build from a couple of days ago is working on my Mac AMD now.

Actually I should have said better. It does have this weird view if you take
default cube, go into edit mode and scale along an axis say 200 times.

Hello all,

Confirmed that the issue no longer exists in the following:

System Information
Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 555X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.22

Blender Version
Working: version: 2.91.0 Alpha, branch: master, commit date: 2020-08-30 21:49, hash: 429afe0c62

I've not been able to reproduce the issue in any manner.

Thank you once again!

This morning I've compiled 6879798202 and opened my own testfile posted here.. It did not show any errors.
But I didn't see any commits fixing the issue I had days ago?
I don't know anymore... We'll see how it goes in the coming days..

Blender must support for Mac graphic card on AMD Radeon please. All of them Apple made.
I am going show you same thing many months ago I told them.
There is no long any more to use Nvidia any more.
Now time to fix match on AMD Radeon

See link https://developer.blender.org/T80270

It seems to work now.

AMD Radeon Pro 455, 2020-08-31 03:47, 68797982025c.

did you inspect CUDA and OpenCL tab not work. They close and invalid make me upset!
@jenkm
https://developer.blender.org/T80270

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

@FloridaJo I don't think this is related to the issue. It seems to be a precision error of some sort.

@kostex So this seems to be fixed now. Feel free to report here if the bug is still here for some of you.

Removed subscriber: @HooglyBoogly

Removed subscriber: @RC12

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

MacOS: Edit Mode - vertex/edge/face selection is missing #79811

489b5790cf

`489b5790cf`