Black artifacts and outline artifacts in editor viewports

I get black artifacts in the editor viewport. It’s like anything forward-rendered (the UI mainly) gets “stuck” but with a black color. Like some buffer is not cleared correctly.

This happens in both lit and unlit mode, the only mode that is working correctly is wireframe. I can temporarily “clear” the blackness by switching to and from wireframe mode, but as soon as the camera transform is changed again, more blackness shows up.

This issue is more prone to happening in lower viewport sizes/resolutions. If I resize the viewport to make it bigger (or go fullscreen), the issue pretty much disappears. However, when I do this, I notice another issue; The “masking buffer” for the yellow actor selection outlines doesnt seem to get cleared either. When I rotate the camera view, the outline just grows according to where the selected actor is, but it doesnt disappear where it isnt.

This doesnt seem to happen in PIE/play mode.

EDIT: This doesnt happen either if I check “Game view”

Please poke me if you need more information or any clarifications.

System informaiton:

Arch Linux x86_64
Intel(R) Core(TM) i5-6440HQ CPU @ 2.60GHz
Intel HD 530
8GB DDR4 RAM

[2017.02.18-14.23.37:824][  0]LogRHI:   GL_VENDOR: Intel Open Source Technology Center
[2017.02.18-14.23.37:824][  0]LogRHI:   GL_RENDERER: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 
[2017.02.18-14.23.37:824][  0]LogRHI:   GL_VERSION: 4.5 (Core Profile) Mesa 17.0.0
[2017.02.18-14.23.37:824][  0]LogRHI:   GL_SHADING_LANGUAGE_VERSION: 4.50

LogInit: Build: ++UE4+Release-4.15-CL-0
LogInit: Engine Version: 4.15.0-0+++UE4+Release-4.15
LogInit: Compatible Engine Version: 4.15.0-0+++UE4+Release-4.15
LogInit: Compiled (64-bit): Feb 18 2017 14:52:59
LogInit: Compiled with Clang: 3.9.1 (tags/RELEASE_391/final)
LogInit: Build Configuration: Development
LogInit: Branch Name: ++UE4+Release-4.15

Anything like this?

This video should explain it well.

OK, that looks nothing like what I get.

Hey -

I do not see the same results in a new project on my end. Can you try updating your graphic drivers for me? Additionally, can you let me know what your Engine Scalability Settings and Preview Rendering Level are set at? You can find both of these in the Settings dropdown at the top of the viewport.

No change without xf86-video-intel. Now I just use the standard mesa and kernel drivers.

Device: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2)  (0x191b)

I use the latest xf86-video-intel package on Arch Linux (xf86-video-intel 1:2.99.917+757+g93942b7d-1) in combination with the latest mesa packages (mesa and mesa-libgl 17.0.0-1). If you use Ubuntu or something, these versions (or newer) will inevitably come to those distros some time in the future as well.

Engine Scalability is set to low, changing the resolution scaling doesnt affect the issue. Setting scalability to high or above just gives me a completely black viewport.

Preview rendering level is set to SM5. I tried setting it to SM4, but now the editor doesnt respond. Will leave my laptop for a few mins and respond later.

Reading up on the wiki it’s apparently recommended these days to ditch the xf86-video-intel and go with the bare modesetting driver. I will try this and come back to you.

SM4 gives a completely corrupted viewport (looks like it just renders uninitialized buffers or something, random memory regions).

Currently using UE 4.15 and have an issue where the viewport screen displays black artefacts (which flicker both when editing and when Playing in Editor)

The other issues are that selected objects are highlighted even when highlight colour is set to transparent and the game object icons are chequer boarded at all times as though selected.

UE 4.14 was OK on the same iMac (Intel Iris Pro Graphics 6200).

It seems to be an incompatibility issue with the Intel Iris Pro Graphics 6200 as another iMac with Nvidia graphics don’t display the issues.

130950-artefacts.png

Hello jasoncunsw-

Can you provide the drivers that you’re on? If you are still seeing this issue, please try upgrading to the latest released drivers. Additionally, if you’re using an integrated card (which the Intel Iris Pro is) then it is recommended that you have more than 8g of RAM.

Same issue here using Intel HD 5500 on Arch with xf86-video-intel drives.

Hey Alko1989-

We have still not seen this reproduce locally. If possible, could you provide a project that shows this behavior for me to test on my end?

Its my first project in UE, its just a side scroller from wiki tutorial. I don’t think the issue is related to the project itself, this occurs on any new project. The behaviour is exactly as shown on the video Frederik provided.

I also tried projects from Unreal course with the same result.

I did compile the engine with clang 3.9.1 or clang package in Arch instead of required clang35. But I can’t use the other since it breaks other dependencies on my system. And it compiled without errors.

Hey ! I am certain that this is not a project issue. Are you sure you are using the same setup? If would guess the same versions for the gpu driver, X11 etc would make a lot of difference.

I have the same issue on ArchLinux as well using Intel Graphics. I started UE 4.15.1 for the first time and created a project based on the ThirdPerson sample project. Once I move in the scene the black artifacts are left behind like if the buffer isn’t being cleared, the more I move, the more clutered the scene gets. I’ve installed on ArchLinux through https://aur.archlinux.org/packages/unreal-engine.

My issue is the same as in the video posted on YouTube. I’m running a 7700K.

, you might be able to reproduce this by disabling the external graphics card and use the integrated Intel graphics. If you can do this on your machine. Every new Intel cpu comes with the integrated graphics card.

Hey everyone,

Though I have not reproduced this personally, I have gone ahead and entered a report for this issue based on the information provided: Unreal Engine Issues and Bug Tracker (UE-44099) . You can track the report’s status as the issue is reviewed by our development staff. Please be aware that this issue may not be prioritized or fixed soon.

Cheers

@, I think the report can add that this happens when using Intel Graphics, I think everyone complaining here is using it.

To help us, can you provide your logs from the project after this occurs. Those could help point to where this problem is occurring.