2.81 & 2.82 Eevee stops rendering in Rendered and Look Dev modes in viewports (macOS) #71147

New Issue

David Cherrie · 2019-10-28T06:06:42+01:00

David Cherrie commented

2019-10-28 06:06:42 +01:00

System Information
Operating system: Darwin-18.5.0-x86_64-i386-64bit 64 Bits
Operating system: Darwin-19.0.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: 9b6aa740be
Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-11-20 21:25, hash: ba1e9ae473
Worked: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449

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.

Open new file
Delete cube and add Suzanne
Add 6 subdivisions using the subdivision modifier
Go to Shading tab and go into either Material or Rendered viewport
Duplicate existing lamp, move it to somewhere else in the scene
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):

Viewport Render Bug.blend

**System Information** Operating system: Darwin-18.5.0-x86_64-i386-64bit 64 Bits Operating system: Darwin-19.0.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: `9b6aa740be` **Broken:** version: 2.82 (sub 1), branch: master, commit date: 2019-11-20 21:25, hash: `ba1e9ae473` **Worked:** version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `f6cb5f5449` **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. - Open new file - Delete cube and add Suzanne - Add 6 subdivisions using the subdivision modifier - Go to Shading tab and go into either Material or Rendered viewport - Duplicate existing lamp, move it to somewhere else in the scene - Click the lamp or Suzanne and Suzanne will disappear Before selecting a lamp: ![Screen Shot 2019-10-28 at 3.57.12 pm.png](https://archive.blender.org/developer/F7864231/Screen_Shot_2019-10-28_at_3.57.12_pm.png) Selected a lamp, the character disappeared however was still selectable (not in the viewport but by selecting in the collections window): ![Screen Shot 2019-10-28 at 3.57.21 pm.png](https://archive.blender.org/developer/F7864228/Screen_Shot_2019-10-28_at_3.57.21_pm.png) [Viewport Render Bug.blend](https://archive.blender.org/developer/F7864276/Viewport_Render_Bug.blend)

David Cherrie commented

2019-10-28 06:06:42 +01:00

Added subscriber: @davidcherrie

blender-admin commented

2019-10-28 06:06:42 +01:00

#71992 was marked as duplicate of this issue

blender-admin commented

2019-10-28 06:06:42 +01:00

#72091 was marked as duplicate of this issue

blender-admin commented

2019-10-28 06:06:42 +01:00

#70713 was marked as duplicate of this issue

blender-admin commented

2019-10-28 06:06:42 +01:00

#72005 was marked as duplicate of this issue

blender-admin commented

2019-10-28 06:06:42 +01:00

#70598 was marked as duplicate of this issue

blender-admin commented

2019-10-28 06:06:42 +01:00

#70780 was marked as duplicate of this issue

blender-admin commented

2019-10-28 06:06:42 +01:00

#71912 was marked as duplicate of this issue

blender-admin commented

2019-10-28 06:06:42 +01:00

#71675 was marked as duplicate of this issue

blender-admin commented

2019-10-28 06:06:42 +01:00

#71766 was marked as duplicate of this issue

David Cherrie changed title 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)

2019-10-28 06:29:46 +01:00

steve miller commented

2019-10-29 13:47:32 +01:00

Added subscriber: @winnertakesteve-1

steve miller commented

2019-10-29 13:47:32 +01:00

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.

Stephen Hamacek commented

2019-11-01 01:10:27 +01:00

Added subscriber: @StephenHamacek

Stephen Hamacek commented

2019-11-01 01:10:27 +01:00

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

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

I've had this issue and similar drawing issues for a while too e.g. [[ https://developer.blender.org/T70598 ]]

David Cherrie commented

2019-11-07 23:36:59 +01:00

Issue still happening in v2.81.16

steve miller commented

2019-11-11 14:13:35 +01:00

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.

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.

Germano Cavalcante commented

2019-11-12 16:23:33 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2019-11-12 16:23:33 +01:00

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.

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.

David Mikucki commented

2019-11-13 21:22:11 +01:00

Added subscriber: @davidmikucki

David Mikucki commented

2019-11-13 21:22:11 +01:00

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.

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.

steve miller commented

2019-11-13 22:44:30 +01:00

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. :(

David Cherrie commented

2019-11-14 03:03:00 +01:00

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.

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.

Piergiorgio Traversin commented

2019-11-19 11:20:50 +01:00

Added subscriber: @Piergi

mw commented

2019-11-19 14:47:59 +01:00

Added subscriber: @fuchs_und_baer

David Cherrie changed title from ~~2.81 Eevee stops rendering in Rendered and Look Dev modes in viewports (macOS)~~ to 2.81 & 2.82 Eevee stops rendering in Rendered and Look Dev modes in viewports (macOS)

2019-11-22 01:35:26 +01:00

Pablo Vazquez commented

2019-11-22 03:20:57 +01:00

Added subscribers: @fclem, @Jeroen-Bakker, @pablovazquez

Pablo Vazquez commented

2019-11-22 03:20:57 +01:00

According to reports this issue slipped into the release, making EEVEE rendering impossible in 2.81.
Did you guys get similar reports before @fclem or @Jeroen-Bakker? Seems like a good candidate for 2.81a for macOS at least.

According to reports this issue slipped into the release, making EEVEE rendering impossible in 2.81. Did you guys get similar reports before @fclem or @Jeroen-Bakker? Seems like a good candidate for 2.81a for macOS at least.

Philipp Oeser commented

2019-11-22 10:43:32 +01:00

Added subscribers: @Lolwel21, @lichtwerk

Philipp Oeser commented

2019-11-22 10:44:21 +01:00

Added subscribers: @jerrsoundripper, @WilliamReynish

Philipp Oeser commented

2019-11-22 10:48:54 +01:00

I recall another report on this as well, so this seems to be a thing...

@WilliamReynish even confirmed it in #71675
@Jeroen-Bakker, @fclem: Can you have an eye on this?

(I cannot repro myself, but I am taking this for granted and confirm, with High prio even...)

I recall another report on this as well, so this seems to be a thing... @WilliamReynish even confirmed it in #71675 @Jeroen-Bakker, @fclem: Can you have an eye on this? (I cannot repro myself, but I am taking this for granted and confirm, with High prio even...)

Clément Foucault commented

2019-11-22 11:19:37 +01:00

I cannot reproduce it either. It would be great if someone that can reproduce bisect the commit that introduced it.

Laurens commented

2019-11-22 14:37:30 +01:00

Added subscriber: @laurens

Lowell Camp commented

2019-11-22 18:46:53 +01:00

The bug also seems to affect wireframe renders and selection. After selecting the mesh and EEVEE stops rendering the objects, wireframe mode only displays object outlines without wireframes, and you will not be able to select any meshes (cameras, empties, and lamps are still selectable).

Jean First commented

2019-11-23 13:58:45 +01:00

Added subscriber: @robbott

Jean First commented

2019-11-23 13:58:45 +01:00

Bisecting reveled the offending commit c601839176 : Fix #70106 Objects with multiple materials are not displaying correctly

Bisecting reveled the offending commit c601839176 : Fix #70106 Objects with multiple materials are not displaying correctly

Jean First commented

2019-11-23 14:42:02 +01:00

reverting that commit allows me to see the all objects (lights, camera and hi poly suzanne) but it reveals a problem with selecting:

in the "layout tab", everything works as expected.

In the "shading tab", everything works in wireframe mode, but in solid, material preview and rendered although I can select the lights and camera in the viewport, I cannot select the hi poly suzanne (click select or box select). At least I cannot see it in the viewport. Selecting in the outliner and deselecting works as expected.

Also the viewport icons for zoom, move, camera and ortho toggle disappear.

reverting that commit allows me to see the all objects (lights, camera and hi poly suzanne) but it reveals a problem with selecting: in the "layout tab", everything works as expected. In the "shading tab", everything works in `wireframe mode`, but in `solid`, `material preview` and `rendered` although I can select the lights and camera in the viewport, I cannot select the hi poly suzanne (click select or box select). At least I cannot see it in the viewport. Selecting in the outliner and deselecting works as expected. Also the viewport icons for zoom, move, camera and ortho toggle disappear.

Germano Cavalcante commented

2019-11-24 23:36:09 +01:00

Noteworthy I can't reproduce the problem on both Intel and the old AMD with "GPU_DEPRECATED_AMD_DRIVER"

Nis Wegmann commented

2019-11-25 09:35:19 +01:00

Added subscriber: @nis

Nis Wegmann commented

2019-11-25 09:35:20 +01:00

In the "shading tab", everything works in wireframe mode, but in solid, material preview and rendered although I can select the lights and camera in the viewport, I cannot select the hi poly suzanne (click select or box select). At least I cannot see it in the viewport. Selecting in the outliner and deselecting works as expected.

I experience the exact same issue with Blender 2.81 on both of my Macs -- a 27" iMac and a MacBook Pro. I have included images of my specs. The bug makes blender 2.81 pretty much unusable (on my computers at least).

> In the "shading tab", everything works in wireframe mode, but in solid, material preview and rendered although I can select the lights and camera in the viewport, I cannot select the hi poly suzanne (click select or box select). At least I cannot see it in the viewport. Selecting in the outliner and deselecting works as expected. I experience the exact same issue with Blender 2.81 on both of my Macs -- a 27" iMac and a MacBook Pro. I have included images of my specs. The bug makes blender 2.81 pretty much unusable (on my computers at least). ![Screenshot 2019-09-27 at 23.07.53.png](https://archive.blender.org/developer/F8164570/Screenshot_2019-09-27_at_23.07.53.png) ![Screenshot 2019-09-27 at 23.28.57.png](https://archive.blender.org/developer/F8164569/Screenshot_2019-09-27_at_23.28.57.png)

Dalai Felinto commented

2019-11-26 02:41:39 +01:00

Added subscriber: @3Omar9

Omar Rahim commented

2019-11-26 03:46:30 +01:00

having the same (driving me crazy) issue on MacBook Pro 2016 amd 460 which seems blender doesn't utilize the dedicated graphics card only intel's, is there anyone know if the same issue happens with the new 16" MBP that has the new amd graphics card rx 5300M/5500M ?

David Cherrie commented

2019-11-26 05:10:53 +01:00

@3Omar9 I have the issue on a 2017 MacBook Pro 15inch Touch and with a 2016 MacBook Pro 15inch Retina. 2017 happens on Mojave and Catalina and the 2016 happens on High Sierra.

Mugur Marculescu commented

2019-11-26 08:46:08 +01:00

Added subscriber: @mugurm

Mugur Marculescu commented

2019-11-26 08:46:08 +01:00

I'm experiencing this bug as well on:

Blender 2.81 (release)
MacBook Pro (2018), MacOS 10.15.1 (19B88)
Radeon RX Vega 56 8 GB (The eGPU card that's normally connected when the issue occurs. The built in gpu is the Vega 20 and the second built in GPU is Intel UHD Graphics 630 1536 MB)

I'm experiencing this bug as well on: Blender 2.81 (release) MacBook Pro (2018), MacOS 10.15.1 (19B88) Radeon RX Vega 56 8 GB (The eGPU card that's normally connected when the issue occurs. The built in gpu is the Vega 20 and the second built in GPU is Intel UHD Graphics 630 1536 MB)

Clément Foucault commented

2019-11-26 11:01:35 +01:00

Can anyone try to run blender with --debug-gpu-force-workarounds and reproduce the bug?

Can anyone try to run blender with `--debug-gpu-force-workarounds` and reproduce the bug?

Jean First commented

2019-11-26 11:41:30 +01:00

Everything seems to work fine on HEAD with --debug-gpu-force-workarounds.

Everything seems to work fine on HEAD with `--debug-gpu-force-workarounds`.

David Cherrie commented

2019-11-26 11:44:47 +01:00

In #71147#817719, @fclem wrote:
Can anyone try to run blender with --debug-gpu-force-workarounds and reproduce the bug?

What do you need me to do since I can replicate reliably?

> In #71147#817719, @fclem wrote: > Can anyone try to run blender with `--debug-gpu-force-workarounds` and reproduce the bug? What do you need me to do since I can replicate reliably?

Clément Foucault commented

2019-11-26 12:51:45 +01:00

@davidcherrie Run blender from command line using blender --debug-gpu-force-workarounds

See https://docs.blender.org/manual/en/dev/advanced/command_line/launch/macos.html

@davidcherrie Run blender from command line using `blender --debug-gpu-force-workarounds` See https://docs.blender.org/manual/en/dev/advanced/command_line/launch/macos.html

Germano Cavalcante commented

2019-11-26 13:07:24 +01:00

Added subscribers: @hominy, @JacquesLucke, @GabrielMoro

Germano Cavalcante commented

2019-11-26 13:08:08 +01:00

Added subscribers: @ph-1, @Oxer-1, @gtomorrow, @FilipMond

David Mikucki commented

2019-11-26 16:28:19 +01:00

In #71147#817563, @3Omar9 wrote:
having the same (driving me crazy) issue on MacBook Pro 2016 amd 460 which seems blender doesn't utilize the dedicated graphics card only intel's, is there anyone know if the same issue happens with the new 16" MBP that has the new amd graphics card rx 5300M/5500M ?

Yes, it does occur with an 8GB 5500m on the 16 inch MBP.

> In #71147#817563, @3Omar9 wrote: > having the same (driving me crazy) issue on MacBook Pro 2016 amd 460 which seems blender doesn't utilize the dedicated graphics card only intel's, is there anyone know if the same issue happens with the new 16" MBP that has the new amd graphics card rx 5300M/5500M ? Yes, it does occur with an 8GB 5500m on the 16 inch MBP.

Óscar commented

2019-11-26 17:21:49 +01:00

I have same the same issue on iMac 27 i7 (middle 2011) / 12GB RAM/ AMD Radeon HD 6970M 1GB / macos 10.13.6

This issue happens on Blender 2.81 & 2.82, I can't explain the exact steps to reproduce it but it happens very often when I change between workspaces or modes (Object to Edit, etc) and then I rotate the wiew.
I found a momentanius fix when this issue happens:

1) Go to the Outliner and select an object.
2) Go to the Layout workspace.
3) Change to Editing workspace.
4) Return to Layout workspace.
5) Click in an empty space in the viewport.

In the main cases, this solves the issue, but it is very difficult to work fluidly in Blender with this problem.
Please, Mac users need a solution soon.

I have same the same issue on iMac 27 i7 (middle 2011) / 12GB RAM/ AMD Radeon HD 6970M 1GB / macos 10.13.6 This issue happens on Blender 2.81 & 2.82, I can't explain the exact steps to reproduce it but it happens very often when I change between workspaces or modes (Object to Edit, etc) and then I rotate the wiew. I found a momentanius fix when this issue happens: **1)** Go to the Outliner and select an object. **2)** Go to the Layout workspace. **3)** Change to Editing workspace. **4)** Return to Layout workspace. **5)** Click in an empty space in the viewport. In the main cases, this solves the issue, but it is very difficult to work fluidly in Blender with this problem. Please, Mac users need a solution soon.

Rafael Chacon commented

2019-11-26 17:22:35 +01:00

Added subscriber: @RafaelChacon

David Mikucki commented

2019-11-26 17:32:39 +01:00

In #71147#817871, @fclem wrote:
@davidcherrie Run blender from command line using blender --debug-gpu-force-workarounds

See https://docs.blender.org/manual/en/dev/advanced/command_line/launch/macos.html

This does seem to resolve the problem. I haven't tested very extensively, but I tried two scenes where I've had the problem and they both worked for a few minutes without the issue. May I ask what that parameter does?

> In #71147#817871, @fclem wrote: > @davidcherrie Run blender from command line using `blender --debug-gpu-force-workarounds` > > See https://docs.blender.org/manual/en/dev/advanced/command_line/launch/macos.html This does seem to resolve the problem. I haven't tested very extensively, but I tried two scenes where I've had the problem and they both worked for a few minutes without the issue. May I ask what that parameter does?

Joan commented

2019-11-26 18:04:09 +01:00

Added subscriber: @JoanBetbese

Joan commented

2019-11-26 18:04:09 +01:00

So... It's supposed to Mac's users to wait until Blender supports Vulcan, isn't it? It's a joke, right? 2.81 isn't a stable version. You guys want to run too faster for the releases. I only have Mac computers to work and I can't work with Blender. It's a shame. :(

Mugur Marculescu commented

2019-11-26 18:23:37 +01:00

@fclem I just ran the with the --debug-gpu-force-workarounds flag on a MacBook Pro and I can still reproduce the bug with the original steps.

Output below:

Read prefs: /Users/mugurm/Library/Application Support/Blender/2.81/config/userpref.blend

GPU: Bypassing workaround detection.
GPU: OpenGL identification strings
GPU: vendor: ATI Technologies Inc.
GPU: renderer: AMD Radeon Pro 555X OpenGL Engine
GPU: version: 4.1 ATI-2.11.20

found bundled python: /Applications/Blender.app/Contents/Resources/2.81/python
ndof: using SpaceNavigator
Info: Deleted 1 object(s)

@fclem I just ran the with the --debug-gpu-force-workarounds flag on a MacBook Pro and I can still reproduce the bug with the original steps. Output below: Read prefs: /Users/mugurm/Library/Application Support/Blender/2.81/config/userpref.blend GPU: Bypassing workaround detection. GPU: OpenGL identification strings GPU: vendor: ATI Technologies Inc. GPU: renderer: AMD Radeon Pro 555X OpenGL Engine GPU: version: 4.1 ATI-2.11.20 found bundled python: /Applications/Blender.app/Contents/Resources/2.81/python ndof: using SpaceNavigator Info: Deleted 1 object(s)

Jean First commented

2019-11-26 19:15:49 +01:00

In #71147#818416, @mugurm wrote:
@fclem I just ran the with the --debug-gpu-force-workarounds flag on a MacBook Pro and I can still reproduce the bug with the original steps.

[...]

@mugurm is right. I can also reproduce it in the "Shader" tab with --debug-gpu-force-workarounds enabled.

> In #71147#818416, @mugurm wrote: > @fclem I just ran the with the --debug-gpu-force-workarounds flag on a MacBook Pro and I can still reproduce the bug with the original steps. > > [...] @mugurm is right. I can also reproduce it in the "Shader" tab with `--debug-gpu-force-workarounds` enabled.

David Cherrie commented

2019-11-26 23:56:48 +01:00

In #71147#817871, @fclem wrote:
@davidcherrie Run blender from command line using blender --debug-gpu-force-workarounds

See https://docs.blender.org/manual/en/dev/advanced/command_line/launch/macos.html

Have done and here is a recording.

Blender Error 2.81-H.264 15mbps.mov

> In #71147#817871, @fclem wrote: > @davidcherrie Run blender from command line using `blender --debug-gpu-force-workarounds` > > See https://docs.blender.org/manual/en/dev/advanced/command_line/launch/macos.html Have done and here is a recording. [Blender Error 2.81-H.264 15mbps.mov](https://archive.blender.org/developer/F8170205/Blender_Error_2.81-H.264_15mbps.mov)

Evan Wilson commented

2019-11-27 01:33:13 +01:00

Added subscribers: @fulviobosco, @EAW

Evan Wilson commented

2019-11-27 01:33:13 +01:00

https://developer.blender.org/p/fufletch/

@fulviobosco I am having issues trying to add you as a subscriber from your duplicate report as I am on my phone, appologies.

Edit: Looks like it went through. Forgot to also add you @MaciejJutrzenka

https://developer.blender.org/p/fufletch/ @fulviobosco I am having issues trying to add you as a subscriber from your duplicate report as I am on my phone, appologies. Edit: Looks like it went through. Forgot to also add you @MaciejJutrzenka

Evan Wilson commented

2019-11-27 02:03:47 +01:00

Added subscriber: @MaciejJutrzenka

mark ferguson commented

2019-11-27 05:17:10 +01:00

Added subscriber: @massey

mark ferguson commented

2019-11-27 05:17:10 +01:00

I have also been experiencing this bug randomly.

(15-inch, Mid 2012)
8 GB 1600 MHz DDR3
2.3 GHz Intel Core i7
NVIDIA GeForce GT 650M 512 MB
Intel HD Graphics 4000 1536 MB

Its happening in 2.82 2019-11-15.
I have access to a range of mac's in work and I can try to reproduce the error there. I don't remember it happening too frequently in work, but I don't use blender a lot in work at this time.

I have also been experiencing this bug randomly. (15-inch, Mid 2012) 8 GB 1600 MHz DDR3 2.3 GHz Intel Core i7 NVIDIA GeForce GT 650M 512 MB Intel HD Graphics 4000 1536 MB Its happening in 2.82 2019-11-15. I have access to a range of mac's in work and I can try to reproduce the error there. I don't remember it happening too frequently in work, but I don't use blender a lot in work at this time.

Mugur Marculescu commented

2019-11-27 06:25:12 +01:00

I have Windows running on Bootcamp on one of the MacBook Pros which is experiencing this bug (under MacOS of course).

I didn't have a chance to test extensively under Windows Bootcamp, but the first pass I was unable to reproduce this bug. Listing this here in case the clue is helpful.

I have Windows running on Bootcamp on one of the MacBook Pros which is experiencing this bug (under MacOS of course). I didn't have a chance to test extensively under Windows Bootcamp, but the first pass I was unable to reproduce this bug. Listing this here in case the clue is helpful.

barrymulrooney commented

2019-11-27 16:37:46 +01:00

Added subscriber: @barrymulrooney

barrymulrooney commented

2019-11-27 16:37:46 +01:00

Getting the same error here. Latest version of Mac OS and Blender 2.81.

It works again if you switch back and fourth and deselect things and change the viewport mode.

Disaster to work with though.

Getting the same error here. Latest version of Mac OS and Blender 2.81. It works again if you switch back and fourth and deselect things and change the viewport mode. Disaster to work with though.

Leif Buckley commented

2019-11-27 18:04:29 +01:00

Added subscriber: @Punker3D

Leif Buckley commented

2019-11-27 18:04:29 +01:00

Same issue on my Mac Pro. I also lose ability to edit an object at times. Lights show up fine and can be moved. With Cycles I can some times get the model to show in Rendered View, but not Material and eevee doesn't show in either. I went back to 2.8 just to continue working. I tried the 2.82 Alpha and it was no different.

Specs:
MacPro Mid 2012
High Sierra 10.13.6 (on 500GB SSD)
3.33 GHz 6-Core Intel Xeon
16 GB 1333 MHz DDR3
AMD Radeon R9 280X 3072 MB

Same issue on my Mac Pro. I also lose ability to edit an object at times. Lights show up fine and can be moved. With Cycles I can some times get the model to show in Rendered View, but not Material and eevee doesn't show in either. I went back to 2.8 just to continue working. I tried the 2.82 Alpha and it was no different. Specs: MacPro Mid 2012 High Sierra 10.13.6 (on 500GB SSD) 3.33 GHz 6-Core Intel Xeon 16 GB 1333 MHz DDR3 AMD Radeon R9 280X 3072 MB

Clément Foucault self-assigned this 2019-11-27 20:04:38 +01:00

Clément Foucault commented

2019-11-27 20:04:38 +01:00

We were able to reproduce on a developer laptop. We will investigate this issue tomorrow.

Philipp Oeser commented

2019-11-28 11:04:32 +01:00

Added subscriber: @UmbertoOldani

Ted van Gaalen commented

2019-11-28 15:28:15 +01:00

Added subscriber: @TedvG

Ted van Gaalen commented

2019-11-28 15:28:15 +01:00

Same here with Blender 2.81
on a Mac Mini 2012 with a 4k screen. Specs (copied) :

System Version:	macOS 10.15.1 (19B88)
Kernel Version:	Darwin 19.0.0
Boot Volume:	Macintosh HD
Boot Mode:	Normal
Computer Name:	***************User Name:*************

Model Name:	Mac mini
Model Identifier:	Macmini6,2
Processor Name:	Quad-Core Intel Core i7
Processor Speed:	2,6 GHz
Number of Processors:	1
Total Number of Cores:	4
L2 Cache (per Core):	256 KB

L3 Cache:	6 MB
Hyper-Threading Technology:	Enabled
Memory:	4 GB
Boot ROM Version:	281.0.0.0.0
SMC Version (system):	2.8f0

with Intel Graphics:

Chipset Model:	Intel HD Graphics 4000
Type:	GPU
Bus:	Built-In
VRAM (Dynamic, Max):	1536 MB
Vendor:	Intel
Device ID:	0x0166
Revision ID:	0x0009
Metal:	Supported, feature set macOS GPUFamily1 v4
Displays:
U28D590:
Resolution:	3840 x 2160 (2160p/4K UHD 1 - Ultra High Definition)
UI Looks like:	3840 x 2160 @ 30 Hz
Framebuffer Depth:	24-Bit Color (ARGB8888)
Main Display:	Yes
Mirror:	Off
Online:	Yes
Rotation:	Supported
Automatically Adjust Brightness:	No
Connection Type:	DisplayPort

was happily playing with sculpting
problem started when adding three point lights
in Eevee render mode

Same here with Blender 2.81 on a Mac Mini 2012 with a 4k screen. Specs (copied) : ``` System Version: macOS 10.15.1 (19B88) Kernel Version: Darwin 19.0.0 Boot Volume: Macintosh HD Boot Mode: Normal Computer Name: ***************User Name:************* Model Name: Mac mini Model Identifier: Macmini6,2 Processor Name: Quad-Core Intel Core i7 Processor Speed: 2,6 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB ``` ``` L3 Cache: 6 MB Hyper-Threading Technology: Enabled Memory: 4 GB Boot ROM Version: 281.0.0.0.0 SMC Version (system): 2.8f0 ``` with Intel Graphics: ``` Chipset Model: Intel HD Graphics 4000 Type: GPU Bus: Built-In VRAM (Dynamic, Max): 1536 MB Vendor: Intel Device ID: 0x0166 Revision ID: 0x0009 Metal: Supported, feature set macOS GPUFamily1 v4 Displays: U28D590: Resolution: 3840 x 2160 (2160p/4K UHD 1 - Ultra High Definition) UI Looks like: 3840 x 2160 @ 30 Hz Framebuffer Depth: 24-Bit Color (ARGB8888) Main Display: Yes Mirror: Off Online: Yes Rotation: Supported Automatically Adjust Brightness: No Connection Type: DisplayPort ``` was happily playing with sculpting problem started when adding three point lights in Eevee render mode

dupoxy commented

2019-11-28 17:40:49 +01:00

Added subscriber: @dupoxy

Clément Foucault commented

2019-11-28 18:09:08 +01:00

Changed status from 'Open' to: 'Resolved'

Clément Foucault closed this issue

2019-11-28 18:09:08 +01:00

blender-admin commented

2019-11-28 18:39:08 +01:00

This issue was referenced by 54bff9dc89

This issue was referenced by 54bff9dc8972240d2683c58e31d21ce9324003a4

blender-admin commented

2019-11-28 18:39:08 +01:00

This issue was referenced by 4e42a98edd

This issue was referenced by 4e42a98edd8ca259c9b13c5548a62b46f0261d60

Ted van Gaalen commented

2019-11-28 21:42:05 +01:00

Hello Clément
(Eevee stopped rendering)
You have found the bug and fixed it, great!
I just logged in here to report my error info, hoping was helpful.
Because I am not familiar with the developer's procedures/way of working,
I'd like to ask:

will there be a new download for 2.81 with this fix
or
will this fix be done in 2.82 only (hope not)
In both cases, when will this fix be available for "normal users" ?
Thank you.
TedvG

Hello Clément (Eevee stopped rendering) You have found the bug and fixed it, great! I just logged in here to report my error info, hoping was helpful. Because I am not familiar with the developer's procedures/way of working, I'd like to ask: - will there be a new download for 2.81 with this fix or - will this fix be done in 2.82 only (hope not) In both cases, when will this fix be available for "normal users" ? Thank you. TedvG

Clément Foucault commented

2019-11-28 21:57:14 +01:00

In #71147#820641, @TedvG wrote:
-will there be a new download for 2.81 with this fix

Yes we are planning to do a 2.81a release because of this bug.

when will this fix be available for "normal users" ?

You will be able to test with the next buildbot version (2.82 beta) tomorrow.

> In #71147#820641, @TedvG wrote: > -will there be a new download for 2.81 with this fix Yes we are planning to do a 2.81a release because of this bug. > when will this fix be available for "normal users" ? You will be able to test with the next buildbot version (2.82 beta) tomorrow.

Clément Foucault commented

2019-11-28 21:59:05 +01:00

Added subscriber: @kostex

choihojin commented

2019-11-29 04:11:14 +01:00

Viewport bugs have been fixed.
Thank you.

Viewport bugs have been fixed. Thank you.

Stanislav commented

2019-11-30 08:17:27 +01:00

Added subscriber: @StanK

Stanislav commented

2019-11-30 08:17:27 +01:00

How we can test this fix?
Latest blender 2.82 from 30 Novemver still unresponsible in EEVEE mode (10.15.1 + RX5700 XT)

I try to test with this demo file: https://download.blender.org/demo/eevee/archiviz/archiviz.blend

There are very slow viewport under material view & render modes.

How we can test this fix? Latest blender 2.82 from 30 Novemver still unresponsible in EEVEE mode (10.15.1 + RX5700 XT) I try to test with this demo file: https://download.blender.org/demo/eevee/archiviz/archiviz.blend There are very slow viewport under material view & render modes.

Roel Koster commented

2019-11-30 08:25:35 +01:00

During sculpting this morning the issue returned for me..
I can't tell exactly the things I did.. but the fact that it happened means there is still something not quite alright.. sorry..

As soon as I can reproduce the issue consistently, I'll report back.

During sculpting this morning the issue returned for me.. I can't tell exactly the things I did.. but the fact that it happened means there is still something not quite alright.. sorry.. As soon as I can reproduce the issue consistently, I'll report back.

Filip commented

2019-11-30 21:46:14 +01:00

Added subscriber: @Filemoner

Filip commented

2019-11-30 21:46:14 +01:00

Where can the fixed version be downloaded? Official one has the same bug on iMac 27 2017.
Waited for 2.81 release to start a new project, and now can't do any serious work with it.
2.80 worked like a charm.
Thank you.

Where can the fixed version be downloaded? Official one has the same bug on iMac 27 2017. Waited for 2.81 release to start a new project, and now can't do any serious work with it. 2.80 worked like a charm. Thank you.

Jean First commented

2019-11-30 21:55:31 +01:00

@Filemoner try 2.82 alpha from https://builder.blender.org/download/
as @fclem said, it's possible 2.81a will be released soon....

@Filemoner try 2.82 alpha from https://builder.blender.org/download/ as @fclem said, it's possible 2.81a will be released soon....

mark ferguson commented

2019-11-30 21:56:09 +01:00

In #71147#821650, @Filemoner wrote:
Where can the fixed version be downloaded? Official one has the same bug on iMac 27 2017.
Waited for 2.81 release to start a new project, and now can't do any serious work with it.
2.80 worked like a charm.
Thank you.

@Filemoner: Go to blender.org. Click 'download 2.81". scroll down and you will see "go experimental". This is the nightly builds. Todays version should have the fix.

> In #71147#821650, @Filemoner wrote: > Where can the fixed version be downloaded? Official one has the same bug on iMac 27 2017. > Waited for 2.81 release to start a new project, and now can't do any serious work with it. > 2.80 worked like a charm. > Thank you. @Filemoner: Go to blender.org. Click 'download 2.81". scroll down and you will see "go experimental". This is the nightly builds. Todays version should have the fix.

Filip commented

2019-11-30 23:01:47 +01:00

Thank you all,
tried 2.82 alpha,
and there were no vanishing objects.

Thank you all, tried 2.82 alpha, and there were no vanishing objects.

Evan Wilson commented

2019-12-01 18:58:57 +01:00

Added subscribers: @DesertG, @dark999

Clément Foucault commented

2019-12-02 10:13:39 +01:00

@StanK This bug is about disappearing objects not EEVEE speed. The workaround is expected to slowdown things a bit. How much ? I can't say.

@kostex you are the only one who still encounter this bug, could you confirm you did with the latest 2.82 beta?

@StanK This bug is about disappearing objects not EEVEE speed. The workaround is expected to slowdown things a bit. How much ? I can't say. @kostex you are the only one who still encounter this bug, could you confirm you did with the latest 2.82 beta?

Roel Koster commented

2019-12-02 14:34:42 +01:00

Clément,

Like I've stated, it happened during extensive editing/sculpting/remeshing etc.. but not right away as before.. so I can't reproduce consistently.
I'm not asking to re-open this case, just wanted to tell you/others that I did witness the issue while working on a scene after the patch.
Could be a completely different cause, but the result was the same.
So as far as I'm concerned/have a say in this, leave the case closed. I'll report back as soon/if I encounter the issue again and can reproduce it.

And yes.. I (always) compile with the latest commits added.

Regards,
your biggest fan ;-)

Clément, Like I've stated, it happened during extensive editing/sculpting/remeshing etc.. but not right away as before.. so I can't reproduce consistently. I'm not asking to re-open this case, just wanted to tell you/others that I *did* witness the issue while working on a scene *after* the patch. Could be a completely different cause, but the result was the same. So as far as I'm concerned/have a say in this, leave the case closed. I'll report back as soon/if I encounter the issue again and can reproduce it. And yes.. I (always) compile with the latest commits added. Regards, your biggest fan ;-)

Dawood commented

2019-12-02 16:41:08 +01:00

Added subscriber: @dawood-3

Dawood commented

2019-12-02 16:41:08 +01:00

it's happening for me as soon as I enter render mode. It started last week intermittently. It seems like when I try to zoom or pan everything disappears. Downloaded latest experimental and seems worse.
Was on 2.8 and 2.81 when it started
https://share.getcloudapp.com/OAuLKRxm

it's happening for me as soon as I enter render mode. It started last week intermittently. It seems like when I try to zoom or pan everything disappears. Downloaded latest experimental and seems worse. Was on 2.8 and 2.81 when it started https://share.getcloudapp.com/OAuLKRxm

Dawood commented

2019-12-02 17:34:08 +01:00

here's a video
https://share.getcloudapp.com/bLuGYG5n

here's a video https://share.getcloudapp.com/bLuGYG5n

Dawood commented

2019-12-02 18:23:29 +01:00

@fclem am still getting the error

barrymulrooney commented

2019-12-05 11:45:16 +01:00

I'm still getting this error in 2.82.

Meshes randomly disappear in the lookdev view and the only way I've found to fix it is to close and reopen Blender.

I'm still getting this error in 2.82. Meshes randomly disappear in the lookdev view and the only way I've found to fix it is to close and reopen Blender.

Clément Foucault commented

2019-12-05 12:12:21 +01:00

@dawood-3 can you simplify your scene and give us the blend file?

Sebastián Barschkis commented

2019-12-05 12:23:27 +01:00

Added subscriber: @sebbas

Ted van Gaalen commented

2019-12-06 17:02:30 +01:00

2.81a: Objects no longer disappear here!
Looks like this problem is solved.
I've downloaded Blender 2.81a on my Mac Mini with Catalina
(see previously entered specs)

loaded the .blend file with the objects that disappeared in previous version 2.81

Playing (ehhrm.. working :o) with it for about 2 hours now,
sculpting with several objects, deleting them, creating new ones,
changing back and forth between workspace render modes etc.
Thanks!

2.81a: Objects no longer disappear here! Looks like this problem is solved. I've downloaded Blender 2.81a on my Mac Mini with Catalina (see previously entered specs) loaded the .blend file with the objects that disappeared in previous version 2.81 Playing (ehhrm.. working :o) with it for about 2 hours now, sculpting with several objects, deleting them, creating new ones, changing back and forth between workspace render modes etc. Thanks!

Laurens commented

2019-12-06 17:58:06 +01:00

Removed subscriber: @laurens

Filip commented

2019-12-12 14:07:33 +01:00

I was wondering, does this fix (2.81a) change performance of Blender? I can't work in Eevee LookDev with some heavy scenes, that work in 2.80
Thanks!

I was wondering, does this fix (2.81a) change performance of Blender? I can't work in Eevee LookDev with some heavy scenes, that work in 2.80 Thanks!

Clément Foucault commented

2019-12-12 14:19:50 +01:00

In #71147#827914, @Filemoner wrote:
I was wondering, does this fix (2.81a) change performance of Blender? I can't work in Eevee LookDev with some heavy scenes, that work in 2.80
Thanks!

yes it has a performance impact. At this point we are adding workaround on top of workaround for osx and it's becoming a problem.

> In #71147#827914, @Filemoner wrote: > I was wondering, does this fix (2.81a) change performance of Blender? I can't work in Eevee LookDev with some heavy scenes, that work in 2.80 > Thanks! yes it has a performance impact. At this point we are adding workaround on top of workaround for osx and it's becoming a problem.

Jean First commented

2019-12-13 03:46:08 +01:00

@fclem I can still reproduce it with this file: #71147.blend

How to reproduce:

try selecting the room object and switch to edit mode - you cannot select anything. In any other mode than wireframe you cannot see your selection at all.

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

Blender Version
Broken: version: 2.82 (sub 4), branch: master (modified), commit date: 2019-12-10 19:44, hash: e760972221

@fclem I can still reproduce it with this file: [#71147.blend](https://archive.blender.org/developer/F8214844/T71147.blend) How to reproduce: 1) try selecting the room object and switch to edit mode - you cannot select anything. In any other mode than wireframe you cannot see your selection at all. **System Information** Operating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20 **Blender Version** Broken: version: 2.82 (sub 4), branch: master (modified), commit date: 2019-12-10 19:44, hash: `e760972221`

filip mond commented

2019-12-15 15:46:34 +01:00

You have disabled "Show Overlays". Enabling it - select / deselect go to edit mode ... works for me.

Jean First commented

2019-12-17 02:14:55 +01:00

Gosh. Your right. Sorry for the noise.

Philipp Oeser commented

2019-12-17 12:34:05 +01:00

Added subscriber: @generic.fit

Aditya Raj commented

2020-12-29 08:32:35 +01:00

Added subscriber: @aditya_raj

Aditya Raj commented

2020-12-29 08:32:35 +01:00

Hello i am new to blender and im having the same issue. Im using a windows pc
My PC Specs are as follow :-

i3 4010U
12gb DDR3 ram
AMD Raedon HD 8670m 2gb (Dedicated GPU)

It was working fine when i had blender 2.90 but after updating to blender 2.91 i started facing the issue. I tried installing 2.90 again but the issue was still not fixed. I decided to fresh install windows. Even after installing new Windows my issue is not fixed. Plz help me

Hello i am new to blender and im having the same issue. Im using a windows pc My PC Specs are as follow :- i3 4010U 12gb DDR3 ram AMD Raedon HD 8670m 2gb (Dedicated GPU) It was working fine when i had blender 2.90 but after updating to blender 2.91 i started facing the issue. I tried installing 2.90 again but the issue was still not fixed. I decided to fresh install windows. Even after installing new Windows my issue is not fixed. Plz help me

Owen commented

2021-01-15 23:32:18 +01:00

Added subscriber: @Teddy1282

Owen commented

2021-01-15 23:32:18 +01:00

This has been happening every time for me.
Steps to reproduce:

Open blender
Switch to material preview
And then the materials just disappear the preview in the material tab goes black and the little thumbnail esque things next to them in the material lists disappear

I've tested this with blender installed through steam on the following versions
2.83 LTS
2.90
2.91
And then as a last resort I have also tried installing blender through the installer on your website not through steam. WIth a fresh install and nothing other than chrome running on 2.91 I get the same exact problem. This happens when loading old 2.83 saves as well. It really sucks cause it means I can't use blender provided things don't even show in rendered mode. I've tried switching to gpu compute as well but it gave me an error the first time I tried when loading render kernels.
I have also tried launching blender from CLI with the parameters you specified
My specs:

Win 10 20H2
Amd radeon rx 480 8gb version latest drivers - I checked.
Ryzen 5 1600 - Did a chipset update last month
32gb ram
Just updated my bios last month as well - this is the first time I've had any issues with bledner although I haven't used it since the bios + chipset updates I did if it matters?
Blender itself is installed on a HDD if it matters.
I have tried factory resetting blender multiple times as well so I don't think it could be caused by any of my addons, besides I'm using the exact same versions blend files and addons on my laptop with no issues.
Any help?
This error occurs in evee and cycles as well.

This has been happening every time for me. Steps to reproduce: - Open blender - Switch to material preview And then the materials just disappear the preview in the material tab goes black and the little thumbnail esque things next to them in the material lists disappear I've tested this with blender installed through steam on the following versions 2.83 LTS 2.90 2.91 And then as a last resort I have also tried installing blender through the installer on your website not through steam. WIth a fresh install and nothing other than chrome running on 2.91 I get the same exact problem. This happens when loading old 2.83 saves as well. It really sucks cause it means I can't use blender provided things don't even show in rendered mode. I've tried switching to gpu compute as well but it gave me an error the first time I tried when loading render kernels. I have also tried launching blender from CLI with the parameters you specified My specs: - Win 10 20H2 - Amd radeon rx 480 8gb version latest drivers - I checked. - Ryzen 5 1600 - Did a chipset update last month - 32gb ram Just updated my bios last month as well - this is the first time I've had any issues with bledner although I haven't used it since the bios + chipset updates I did if it matters? Blender itself is installed on a HDD if it matters. I have tried factory resetting blender multiple times as well so I don't think it could be caused by any of my addons, besides I'm using the exact same versions blend files and addons on my laptop with no issues. Any help? This error occurs in evee and cycles as well.

crecentech system commented

2023-01-30 16:11:34 +01:00

Added subscriber: @crecentechsystem

crecentech system commented

2023-01-30 16:11:34 +01:00

Thanks for sharing with us. Such amazing information. This information is really very informative for me.. Really thankful to you.
Digital marketing services in USA

Thanks for sharing with us. Such amazing information. This information is really very informative for me.. Really thankful to you. [Digital marketing services in USA ](https://crecentech.com/)

Michael Parkin-White commented

2023-01-30 16:27:56 +01:00

Added subscriber: @Michael-Parkin-White-Apple

Sign in to join this conversation.