Page MenuHome

2.81 Eevee stops rendering in Rendered and Look Dev modes in viewports (macOS)
Open, Needs Triage by DeveloperPublic

Description

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

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-10-27 13:40, hash: rB9b6aa740be31
Worked: (optional)

Short description of error
When in rendered and look dev mode (particularly in shading tab), when selecting or moving objects like lights, objects disappear and go transparent. The objects are still selectable but when in either mode, they are not rendering. The only way to get them back is by saving the file, closing Blender and then reopening.

Exact steps for others to reproduce the error
When creating/editing materials and moving objects or changing the selection of objects in the scene (mainly in the Shading tab), objects will disappear and no longer render. Removing the material from the object and re-adding it, will not allow the object to show up in the viewport. When actually rendering the file the object does appear.

Issue happens in Eevee and when switching to cycles, the object renders in the viewport but if you switch back to Eevee, the object is still not rendering.

  1. Open new file
  2. Delete cube and add Suzanne
  3. Add 6 subdivisions using the subdivision modifier
  4. Go to Shading tab and go into either Material or Rendered viewport
  5. Duplicate existing lamp, move it to somewhere else in the scene
  6. Click the lamp or Suzanne and Suzanne will disappear

Before selecting a lamp:

Selected a lamp, the character disappeared however was still selectable (not in the viewport but by selecting in the collections window):

Details

Type
Bug

Event Timeline

David Cherrie (davidcherrie) renamed this task from Objects disappearing in Rendered and Look Dev modes in viewports to 2.81 Eevee stops rendering in Rendered and Look Dev modes in viewports (macOS).Mon, Oct 28, 6:29 AM
David Cherrie (davidcherrie) updated the task description. (Show Details)

also having this issue when working with a rigged character: selecting a bone in pose mode often makes the mesh its deforming disappear. 2.80 official still working fine.

I've had this issue and similar drawing issues for a while too

e.g. https://developer.blender.org/T70598

Issue still happening in v2.81.16

a number of other graphical issues i'd been having were fixed by deleting the blender application support folder on my system.

however this one seems to persist.

Apple has discontinued OpenGL support on macOS platforms.
We are aware of many such problems.
Let's wait to see if when blender has Vulkan support these issues will be resolved.

This seems to be related to VRAM usage. It wasn't occurring for me in 2.80, but now it does occur when I use 2.81 with complex scenes. Adding a 3–4 Suzannes with level 6 subdivision surface and a few lights with contact shadows on seems to pretty consistently trigger this behavior on a Vega 20. Also related seem to be factors like having more or fewer applications open while working.

Also hoping Vulkan solves this, but it'd be great if 2.81 doesn't ship with this regression.

yeah, as i haven't heard any hard timelines on a vulcan transition, these issues are substantial enough for me at least that blender would no longer be viable on macos. :(

VRAM would certainly make sense. I just used the factory default 2.81.16 (one released 13th November) and created a metaball, added a multi-resolution modifier with 3 sub-divisions. Sculpted a bit, turned on Render viewport, added a second lamp into the scene and then selected the other lamp, and then the metaball disappeared.

I very much hope Blender fixes this problem too, otherwise my $6,000 MacBook Pro is useless to me.