How do I do that? This still isn't working with a 2018 MacBook Pro 2018 i7 Vega 20. It initially worked with the first fix. On version blender-2.80.0-git20190315.35b78d9807c4-x86_64 5.34.24 PM is the latest one that I use to get the noise textures to work in with Volumes.
Solution introduces older bugs. No reliable state found to solve the real issue ( depth buffer is incorrect perhaps as it is written twice) assigned the task to @Clément Foucault (fclem) for better fit in current design
This reintroduce ghosting artifacts.
Open file and switch between solid and lookdev mode. no reflection from the environment should pass through the reflection of the red cube on the metal cube.
Mon, Jul 15
@Patrick (Xpected) please create a new report with all your system information. It probably has a different cause:
How do i fix this, im new to blender, when i add the reflection plane it crashes too.
Sun, Jul 14
Fri, Jul 12
Yes you can do both.
@Clément Foucault (fclem): not sure if this is rather harmless? (release builds seems to survive, but this sounds as if it might have unwanted consequences...)
Thu, Jul 11
Just as a note.
Wed, Jul 10
I updated to blender-2.80-3b4054cb586f-linux-glibc217-x86_64,I can not produce the problem again,I will try with my big scene now ,this is my system info: thanks
Tue, Jul 9
This seems to have been fixed.
Unfortunately this is a limitation of the current implementation. Transparency never worked well with DoF, especially in the realtime graphics domain.
Ok closing as the fix for the work around for source drivers has been added.
Can't reproduce this with the open source drivers, so I guess this is a closed source bug.
@Michael Soluyanov (crantisz), this is always a good idea to make a new report. It covers different aspect from the original report and for the discoverability of issues it totally makes sense to have separate report.
I am able to reproduce this one, (Cascade Size to 4096) with the latest AMD Pro Drivers.
For completeness can you upload your system_info.txt (Help => Save System Info).
Still doesn't work with world.
Mon, Jul 8
This is caused by the tagging of the viewport by the walk operator. The issue is the same as the refresh issue when hovering on manipulators.
Ideally, we should do like cycles and re-render only if there is a change in the scene or a change of camera.
Sun, Jul 7
Fri, Jul 5
Hello, in the end I was finally able to found the source of the problem. The scene had several 4k textures and after changing settings so the texture "Limit Size" was 1024 (instead of the default "no limit"), the shader compilation went smoother, the program didn't stall and it rendered the scene as expected. Also when working with that limit the program didn't have those big hiccups. I also changed Image Display Method to "2D Texture".
Thu, Jul 4
Shouldn't the priority of this task raised from Medium to High?
@Ali Najafi (shylon) it happen on linux too with the closed source AMD driver (not the open source driver).
Interesting is that, this bug is not on Linux on AMD GPUs
Here is the blend file.
This is happening to AMD GPUs only and mostly with RX series. Seems like this bug has not fixed for a long time. Any information about fixing it?
Wed, Jul 3
Tue, Jul 2
I am convinced that if separate albedo is on, the best is to not mask the lighting.