3D Viewport Bug - Ghosting of Geometry - Blender 2.8 d28d202fd1 on macOS High Sierra 10.13.5 #55987

New Issue

Martin · 2018-07-15T22:38:00+02:00

Martin commented

2018-07-15 22:38:00 +02:00

System Information
Macbook Pro 15inch, 2017
macOS High Sierra 10.13.5
Intel Core i7 2.9GHz
Radeon Pro 560 4096 MB
Intel HD Graphics 630 1536 MB

Blender Version
Broken: 2.8 d28d202fd1 x86_64
Worked: 2.79 ;)

Short description of error
When I scroll in on an object, i. e. a cube, when I zoom back out i still see some slight silhouette of the cube blocking parts of the grid and other objects. As soon as i resize the viewport it disappears but comes back as soon as i zoom or rotate the 3D View. I attached a screencapture to elaborate.
Blender-d28d202fd1-x86_64-viewport-bug.mp4

Exact steps for others to reproduce the error
Vanilla Blender 2.8 without modifications. Regular Startup File with Eevee.

**System Information** Macbook Pro 15inch, 2017 macOS High Sierra 10.13.5 Intel Core i7 2.9GHz Radeon Pro 560 4096 MB Intel HD Graphics 630 1536 MB **Blender Version** Broken: 2.8 d28d202fd1 x86_64 Worked: 2.79 ;) **Short description of error** When I scroll in on an object, i. e. a cube, when I zoom back out i still see some slight silhouette of the cube blocking parts of the grid and other objects. As soon as i resize the viewport it disappears but comes back as soon as i zoom or rotate the 3D View. I attached a screencapture to elaborate. [Blender-d28d202fd1-x86_64-viewport-bug.mp4](https://archive.blender.org/developer/F3942988/Blender-d28d202fd1-x86_64-viewport-bug.mp4) **Exact steps for others to reproduce the error** Vanilla Blender 2.8 without modifications. Regular Startup File with Eevee.

Martin commented

2018-07-15 22:38:00 +02:00

Added subscriber: @Maddin

blender-admin commented

2018-07-15 22:38:00 +02:00

#56454 was marked as duplicate of this issue

blender-admin commented

2018-07-15 22:38:00 +02:00

#55977 was marked as duplicate of this issue

Bastien Montagne commented

2018-07-16 15:54:38 +02:00

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

Bastien Montagne commented

2018-07-16 15:54:38 +02:00

Looks like a buffer refreshing issue or something… @fclem might have a better idea of the problem, or maybe @Jeroen-Bakker ?

Jeroen Bakker commented

2018-07-17 09:09:28 +02:00

Seems like Z-fighting during the TAA. Can be that the buffers are not copied correctly, but that is strange as it only uses BLIT functions.

@Maddin Can you try to set the viewport quality to 0 in the user preferences. This will disable TAA and see if this helps.
Will try to reproduce it, but I don't have the hardware it is failing on.

Seems like Z-fighting during the TAA. Can be that the buffers are not copied correctly, but that is strange as it only uses BLIT functions. @Maddin Can you try to set the viewport quality to 0 in the user preferences. This will disable TAA and see if this helps. Will try to reproduce it, but I don't have the hardware it is failing on.

Martin commented

2018-07-17 10:51:47 +02:00

Good morning. Unfortunately that didn't have an effect. Still the same. It only occurs in LookDev mode, in solid and rendered mode everything is fine.

Clément Foucault commented

2018-07-17 11:53:23 +02:00

@Maddin You say that it only occurs in LookDev mode but your video is in Solid mode.

If you did what @Jeroen-Bakker suggested, it affects the Solid view only.
If you want to disable the TAA for lookdev and rendered mode go to the Render Properties panel (with EEVEE as render engine) and under the sampling tab set the viewport samples to 1.

@Maddin You say that it only occurs in LookDev mode but your video is in Solid mode. If you did what @Jeroen-Bakker suggested, it affects the Solid view only. If you want to disable the TAA for lookdev and rendered mode go to the Render Properties panel (with EEVEE as render engine) and under the sampling tab set the viewport samples to 1.

Martin commented

2018-07-17 11:58:38 +02:00

Of course, you're right. Viewport Quality affects solid mode. Check. But setting viewport samples to 1 or 0 does not work for the lookdev mode. Still the same effect.

// EDIT

Sorry, was in Cycles for the last part. Now its gone! You're right :)

Of course, you're right. Viewport Quality affects solid mode. Check. But setting viewport samples to 1 or 0 does not work for the lookdev mode. Still the same effect. // EDIT Sorry, was in Cycles for the last part. Now its gone! You're right :)

Martin commented

2018-07-23 10:42:35 +02:00

Just a FYI: As a workaround, so i don't have to turn down sampling or viewport quality, i just put a big plane in the background. Its only an issue with a transparent backdrop.

Roel Koster commented

2018-07-23 17:40:35 +02:00

Added subscriber: @kostex

Roel Koster commented

2018-07-23 17:40:35 +02:00

on AMD Radeon R9 M395X 4096 MB (OSX iMac 5k) the proposed Viewport Samples and viewport quality "fixes" the issue.
However in Eevee Render Preview and enabled screen(space)_subsurface_scattering, viewport still acts up.

on AMD Radeon R9 M395X 4096 MB (OSX iMac 5k) the proposed Viewport Samples and viewport quality "fixes" the issue. However in Eevee Render Preview and enabled screen(space)_subsurface_scattering, viewport still acts up. ![Screen Shot 2018-07-23 at 17.34.11.jpg](https://archive.blender.org/developer/F4023038/Screen_Shot_2018-07-23_at_17.34.11.jpg)

Clément Foucault commented

2018-07-23 19:28:20 +02:00

For the record the culprit function might be GPU_framebuffer_blit.

It breaks TAA in workbench (solid view) and Eevee as well as Eeevee Subsurface because they all use this function.

@kostex Are you sure this glitch happen with the AMD GPU?

For the record the culprit function might be GPU_framebuffer_blit. It breaks TAA in workbench (solid view) and Eevee as well as Eeevee Subsurface because they all use this function. @kostex Are you sure this glitch happen with the AMD GPU?

Clément Foucault commented

2018-07-23 19:55:43 +02:00

Added subscribers: @zgorg, @brecht, @Sergey

Roel Koster commented

2018-07-23 20:25:37 +02:00

Fairly Sure ;-)

Fairly Sure ;-) ![Screen Shot 2018-07-23 at 20.20.54.jpg](https://archive.blender.org/developer/F4024027/Screen_Shot_2018-07-23_at_20.20.54.jpg)

Clément Foucault commented

2018-07-23 20:37:50 +02:00

@kostex this does not indicate the graphic card used by OpenGL.

To know that, use Help menu > Save System Info.
Then search for the Opengl renderer string.

@kostex this does not indicate the graphic card used by OpenGL. To know that, use Help menu > Save System Info. Then search for the Opengl renderer string.

Roel Koster commented

2018-07-23 20:58:40 +02:00

That's what you get when dealing with noobs ;-) Sorry..

But the OpenGL Renderer is in fact AMD.. is it not? I don't dare to conclude anything anymore ;-)
system-info.txt

That's what you get when dealing with noobs ;-) Sorry.. But the OpenGL Renderer is in fact AMD.. is it not? I don't dare to conclude anything anymore ;-) [system-info.txt](https://archive.blender.org/developer/F4024220/system-info.txt)

Martin commented

2018-07-23 22:07:06 +02:00

I attached mine too. Since GPU Rendering, at least with cycles, is broken since for ever on the mac, i always thought blender is running sole on CPU. Who knew.

system-info.txt

I attached mine too. Since GPU Rendering, at least with cycles, is broken since for ever on the mac, i always thought blender is running sole on CPU. Who knew. [system-info.txt](https://archive.blender.org/developer/F4024624/system-info.txt)

Clément Foucault commented

2018-07-23 22:31:25 +02:00

So seems you are both using the AMD card. So there is a similar problem on the intel 630 on windows reported by other users.

Pepper commented

2018-07-30 15:48:15 +02:00

Added subscriber: @Sankel

Pepper commented

2018-07-30 15:48:15 +02:00

I also have the same issue as mentioned above. On an iMac5K with AMD Radeon Pro 580.

system-info.txt

I also have the same issue as mentioned above. On an iMac5K with AMD Radeon Pro 580. [system-info.txt](https://archive.blender.org/developer/F4085551/system-info.txt)

-- commented

2018-07-30 16:30:40 +02:00

Hello my subject was connected to this one.
WIN 10 processor intel I3 7300 HD graphics 630
last driver win64_24.20.100.6194
blender-2.80-8f01623ef31-win64
yesterday I tried the new version and now I get something normal in solid view
but with EEVEE and cycles the same issue in material view (lookdev) and render view
Open GL is ok in material view
I tried the different setting in viewportsampling to 1 and viewport quality to 0 > no change

Hello my subject was connected to this one. WIN 10 processor intel I3 7300 HD graphics 630 last driver win64_24.20.100.6194 blender-2.80-8f01623ef31-win64 yesterday I tried the new version and now I get something normal in solid view but with EEVEE and cycles the same issue in material view (lookdev) and render view Open GL is ok in material view I tried the different setting in viewportsampling to 1 and viewport quality to 0 > no change

Vincent Lovett commented

2018-08-02 05:55:00 +02:00

Added subscribers: @ClementPellegrini-3, @OathOfPosidon

Vincent Lovett commented

2018-08-02 05:55:00 +02:00

As of right now, Intel Integrated Graphics users are having the black ghosting affect in the Eevee render mode as well. The workbench is working fine, and cycles works fine, but Eevee does not. It has been a bug for some time now, but we havent had a proper means to report it, although it does technically lead to a crash if one tries to edit materials while in the Eevee renderer. A lot of us are eager to use Eevee, as it seems to be an extremely valuable asset, we are not able to though because of this bug.

As far as I have heard, its affecting a wide range of different Integrated Graphics cards from Intel. For instance, mine is a 530, but as stated above, the 630 is also having the issue. @ClementPellegrini-3

As of right now, Intel Integrated Graphics users are having the black ghosting affect in the Eevee render mode as well. The workbench is working fine, and cycles works fine, but Eevee does not. It has been a bug for some time now, but we havent had a proper means to report it, although it does technically lead to a crash if one tries to edit materials while in the Eevee renderer. A lot of us are eager to use Eevee, as it seems to be an extremely valuable asset, we are not able to though because of this bug. As far as I have heard, its affecting a wide range of different Integrated Graphics cards from Intel. For instance, mine is a 530, but as stated above, the 630 is also having the issue. @ClementPellegrini-3

Vincent Lovett commented

2018-08-11 07:18:15 +02:00

I'm guessing that the Intel thing isn't as high of a priority as others, which is understandable. Just really makes testing Eevee hard when one cant actually use Eevee. As of right now, the main reason I'm not using blender is because Intel users can't use the Eevee render engine (nor material preview in both Cycles and Eevee) because it's broken for Integrated graphics cards.

Clément Foucault commented

2018-08-11 12:08:46 +02:00

@OathOfPosidon It's not that it is a lower priority issue it's just that it's hard to debug this particular issue without access to the hardware. But I found someone who has the same issue and live nearby so I will fix this ASAP.

Vincent Lovett commented

2018-08-11 19:14:33 +02:00

@fclem Thank you for the work that you are doing, I'm sorry if my previous comment came off as demanding or anything, because it wasn't. I really do appreciate you caring enough to look into, and fix, the bug.

Brecht Van Lommel commented

2018-08-19 22:34:16 +02:00

Added subscriber: @PawelBzyl

Martin commented

2018-09-10 23:19:28 +02:00

Good evening gentlemen. Is there any news on this issue? Right now it's the one thing keeping me from really getting into 2.8. I just compiled again, but the bug still persists.

Thanks :)

Good evening gentlemen. Is there any news on this issue? Right now it's the one thing keeping me from really getting into 2.8. I just compiled again, but the bug still persists. Thanks :)

Pepper commented

2018-09-12 01:14:56 +02:00

Because of this planes viewed in orto arent't visable, unless you're in edit-mode

![Naamloos.jpeg](https://archive.blender.org/developer/F4669868/Naamloos.jpeg) Because of this planes viewed in orto arent't visable, unless you're in edit-mode

Orfeo commented

2018-10-02 13:00:04 +02:00

Added subscriber: @orfeo

Orfeo commented

2018-10-02 13:00:04 +02:00

If I set the Viewport Quality to 0.000 the ghosting is gone

Blender 2.80 Alpha 2 (2018-09-30)
MacBook Pro (15-inch, 2017)
macOS Mojave 10.14

![Screenshot 2018-10-02 at 11.54.13.png](https://archive.blender.org/developer/F4905453/Screenshot_2018-10-02_at_11.54.13.png) If I set the Viewport Quality to 0.000 the ghosting is gone Blender 2.80 Alpha 2 (2018-09-30) MacBook Pro (15-inch, 2017) macOS Mojave 10.14

Pepper commented

2018-10-02 17:00:03 +02:00

This works for me!

Blender 2.8 Alpha 2 (2018-09-29)
iMac 27" (2017)
macOS Mojave 10.14

This works for me! Blender 2.8 Alpha 2 (2018-09-29) iMac 27" (2017) macOS Mojave 10.14

-- commented

2018-10-03 14:33:47 +02:00

video to show the situation now on HD630
1rst October version
https://www.youtube.com/watch?v=dG-6Cfb-jFE

viewport is at 0
and when I close preferences window > crash
even if I want to open fullscreen

video to show the situation now on HD630 1rst October version https://www.youtube.com/watch?v=dG-6Cfb-jFE viewport is at 0 and when I close preferences window > crash even if I want to open fullscreen

-- commented

2018-10-22 12:38:52 +02:00

it's working! the very last update of my graphic card HDgraphics630 helps
a bug with contact shadowartefact on the left
other user of HD graphics, what are your settings?

it's working! the very last update of my graphic card HDgraphics630 helps a bug with contact shadow[artefact on the left ](https://www.dropbox.com/s/zkjhviqrjonu7bm/Blender.jpg?dl=0) other user of HD graphics, what are your settings?

-- commented

2018-10-22 12:47:09 +02:00

but I have some little black points on my surface and I don't know why

Clément Foucault commented

2018-11-09 12:13:40 +01:00

Changed status from 'Open' to: 'Resolved'

Clément Foucault closed this issue

2018-11-09 12:13:40 +01:00

Clément Foucault self-assigned this 2018-11-09 12:13:40 +01:00

Clément Foucault commented

2018-11-09 12:13:40 +01:00

I think we fixed this issue for everyone now. Closing.

-- commented

2018-11-09 22:58:32 +01:00

yes it's working. big job. I had hope a such work in the interface. but it's not so sure about that...for instance modifications in keys are strange and often useless! I have to restored shift C cursor to center, ctrl alt shit c set origin. I added shift RMB to move cursor and shift alt RMB to move it on surfaces ^^ it's already possible in the key configuration. why not present in their tool menu. border select have a bug in object mode: it doesn't add several selections. it's cool to work on such mysterious keys like alt E to add several color in the ramp node but there is more logical things to do first. ctrl t and alt t back! no way. why all this is still present but was substract from the settings. ctrl u is back no way...
and in the interface if they don't understand how much faster is a crtl t I dont have to explain many other things...

yes it's working. big job. I had hope a such work in the interface. but it's not so sure about that...for instance modifications in keys are strange and often useless! I have to restored shift C cursor to center, ctrl alt shit c set origin. I added shift RMB to move cursor and shift alt RMB to move it on surfaces ^^ it's already possible in the key configuration. why not present in their tool menu. border select have a bug in object mode: it doesn't add several selections. it's cool to work on such mysterious keys like alt E to add several color in the ramp node but there is more logical things to do first. ctrl t and alt t back! no way. why all this is still present but was substract from the settings. ctrl u is back no way... and in the interface if they don't understand how much faster is a crtl t I dont have to explain many other things...

Niels commented

2018-11-27 00:04:52 +01:00

Added subscriber: @nielspl-2

Niels commented

2018-11-27 00:04:52 +01:00

Hi Clément. I had the exact same issue on the Mac (hackintosh) with an AMD Radeon RX 560. Adding the exact matching string "AMD Radeon RX 560 OpenGL Engine" resolved it.

Can you, depending on the scope of this issue, add:
"AMD Radeon RX 560 OpenGL Engine" or
"AMD Radeon RX 560" or
"AMD Radeon RX"?

gpu_extensions.c

#if defined(__APPLE__)
    if (strstr(renderer, "AMD Radeon Pro") || strstr(renderer, "AMD Radeon R9") || strstr(renderer, "AMD Radeon RX 560 OpenGL Engine")) {
        GG.depth_blitting_workaround = true;            
    }
#endif

Hi Clément. I had the exact same issue on the Mac (hackintosh) with an AMD Radeon RX 560. Adding the exact matching string `"AMD Radeon RX 560 OpenGL Engine"` resolved it. Can you, depending on the scope of this issue, add: `"AMD Radeon RX 560 OpenGL Engine"` or `"AMD Radeon RX 560"` or `"AMD Radeon RX"`? gpu_extensions.c ``` #if defined(__APPLE__) if (strstr(renderer, "AMD Radeon Pro") || strstr(renderer, "AMD Radeon R9") || strstr(renderer, "AMD Radeon RX 560 OpenGL Engine")) { GG.depth_blitting_workaround = true; } #endif ```

Niels commented

2018-11-27 16:37:09 +01:00

Changed status from 'Resolved' to: 'Open'

Niels reopened this issue

2018-11-27 16:37:09 +01:00

Niels commented

2018-11-27 16:37:09 +01:00

Hi. I forgot to re-open this issue yesterday.

Can anyone apply my "fix" as shown in my previous post?

Hi. I forgot to re-open this issue yesterday. Can anyone apply my "fix" as shown in my previous post?

-- commented

2018-11-28 12:17:23 +01:00

to validate some changes in material I have to click on the object it's like if it was not selected anymore.
in edit stroke I don't see any selection but it is selected
and I opened a bug about B not selecting several object in object mode.
I think it 's linked to graphic card (HD grahic 630)

to validate some changes in material I have to click on the object it's like if it was not selected anymore. in edit stroke I don't see any selection but it is selected and I opened a bug about B not selecting several object in object mode. I think it 's linked to graphic card (HD grahic 630)

blender-admin commented

2018-11-28 13:19:04 +01:00

This issue was referenced by 52458ab49d

This issue was referenced by 52458ab49d40081466e369709d68c13a6a47663e

Clément Foucault commented

2018-11-28 16:00:12 +01:00

Changed status from 'Open' to: 'Resolved'

Clément Foucault closed this issue

2018-11-28 16:00:12 +01:00

Timur Yessenov commented

2018-12-10 09:42:33 +01:00

Added subscriber: @synth1983

Timur Yessenov commented

2018-12-10 09:42:33 +01:00

Hi!
I use Radeon Vega 64
I have some other type of overlapping glitches in viewport when using bevel modifier in Edit Mode and in Ortho view mode
It randomly flickers and changing during viewport movements.

Hi! I use Radeon Vega 64 I have some other type of overlapping glitches in viewport when using bevel modifier in Edit Mode and in Ortho view mode It randomly flickers and changing during viewport movements. ![Screen Shot 2018-12-10 at 14.39.19.png](https://archive.blender.org/developer/F5908195/Screen_Shot_2018-12-10_at_14.39.19.png)

Roel Koster commented

2018-12-10 09:54:39 +01:00

Timur,

I think you need to check your topology.. you've got overlapping faces.. That's how that looks like.. has nothing to do with this (fixed) bug as I see it

Timur, I think you need to check your topology.. you've got overlapping faces.. That's how that looks like.. has nothing to do with this (fixed) bug as I see it

isoueu commented

2020-12-31 22:47:18 +01:00

Added subscriber: @isoueu

isoueu commented

2020-12-31 22:47:18 +01:00

This comment was removed by @isoueu

*This comment was removed by @isoueu*

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

3D Viewport Bug - Ghosting of Geometry - Blender 2.8 d28d202fd1 on macOS High Sierra 10.13.5 #55987

3D Viewport Bug - Ghosting of Geometry - Blender 2.8 `d28d202fd1` on macOS High Sierra 10.13.5 #55987