Maniphest T60705

EEVEE Volumetrics not working
Closed, Resolved
Actions

Assigned To
Clément Foucault (fclem)
Authored By
Daniel (elkoled)
Jan 21 2019, 9:31 AM
Tags
  • BF Blender
  • EEVEE & Viewport
Subscribers
Clément Foucault (fclem)
Daniel (elkoled)
Philipp Oeser (lichtwerk)

Description

System Information
Operating system:
Windows 7 64 bit
Intel Core i5 6300U (with Intel HD520)

Blender Version
blender 2.80 dd3f5186260e, 21.01.2019

Short description of error
Volumetrics on default cube shows only black cube and yellow-grey background with glitches on the edges on camera movement.

Exact steps for others to reproduce the error
Clean install of blender, no addons.

  1. Assign principled volume shader to default cube
  2. Enable volumetrics in eevee settings
  3. Switch to rendered view

Screenshot:

.blend file

volumetrics_glitch.blend611 KBDownload

Thank you all for your work. I love blender.

Related Objects

Mentioned Here
rBdd3f5186260e: Cleanup: rename GPU function to set buffer length

Event Timeline

Daniel (elkoled) created this task.Jan 21 2019, 9:31 AM
Philipp Oeser (lichtwerk) assigned this task to Clément Foucault (fclem).Jan 21 2019, 11:20 AM
Philipp Oeser (lichtwerk) added subscribers: Clément Foucault (fclem), Philipp Oeser (lichtwerk).

Cannot reproduce here (Fedora 29, 970m with 410.78 drivers)

Shot in the dark, but does running blender from the commandline with the --debug-gpu-force-workarounds option help here?
(Please also attach the output of that as a .txt file here...)

@Clément Foucault (fclem): does this ring a bell?

Philipp Oeser (lichtwerk) lowered the priority of this task from 90 to Normal.Jan 21 2019, 11:21 AM
Clément Foucault (fclem) added a comment.Jan 21 2019, 11:38 AM

Windows 7 64 bit

This is the issue. The drivers for win 7 are old and no more maintained. So we find all these kind of issues on theses drivers.

Can you make sure your drivers are at least at version 15.45.23.4860 ?

These drivers are also one year old and even the Win10 drivers fixed core issues only a few month ago.

Daniel (elkoled) added a comment.EditedJan 21 2019, 11:47 AM
In T60705#603369, @Clément Foucault (fclem) wrote:

Windows 7 64 bit

This is the issue. The drivers for win 7 are old and no more maintained. So we find all these kind of issues on theses drivers.

Can you make sure your drivers are at least at version 15.45.23.4860 ?

These drivers are also one year old and even the Win10 drivers fixed core issues only a few month ago.

Thanks for the reply.

--debug-gpu-force-workarounds still shows the glitch.

My dxdiag panel is attached.

Clément Foucault (fclem) added a comment.Jan 21 2019, 11:54 AM

Well the versioning seems strange. Your driver is said to be 2 years old. But the last available on intel driver page says it's only one year old. Try updating your drivers.

Daniel (elkoled) changed the task status from Unknown Status to Resolved.Jan 21 2019, 12:53 PM
In T60705#603395, @Clément Foucault (fclem) wrote:

Well the versioning seems strange. Your driver is said to be 2 years old. But the last available on intel driver page says it's only one year old. Try updating your drivers.

Updated drivers and works fine now! Thanks for your help.
I found out, that this is a device specific driver (LenovoT460 Laptop), thats why the version number is different.

Clément Foucault (fclem) edited projects, added EEVEE & Viewport; removed Eevee.Jun 19 2020, 11:08 PM