OpenGL Driver losing connection with display using certain volumetric shader node configurations #43496

New Issue

Duncan Freeman · 2015-01-31T08:14:35+01:00

Duncan Freeman commented

2015-01-31 08:14:35 +01:00

When using the 'Tangent' On geometry connected to the color input of a volumetric shader (Node setup), it crashes the OpenGL driver.
Both monitors rebooted, and the display driver notified me that it had in fact rebooted.

Node Setup:
Geometry: Volume Absorbtion:

   Tanget -------> [     ]  Color

.Blend file and screenshot of the message given by my display driver:

Crash.blend

System info: [system-info.txt](https://archive.blender.org/developer/F140105/system-info.txt) When using the 'Tangent' On geometry connected to the color input of a volumetric shader (Node setup), it crashes the OpenGL driver. Both monitors rebooted, and the display driver notified me that it had in fact rebooted. Node Setup: Geometry: Volume Absorbtion: ``` Tanget -------> [ ] Color ``` .Blend file and screenshot of the message given by my display driver: ![Crash.png](https://archive.blender.org/developer/F140100/Crash.png) [Crash.blend](https://archive.blender.org/developer/F140099/Crash.blend)

Duncan Freeman commented

2015-01-31 08:14:35 +01:00

Changed status to: 'Open'

Duncan Freeman commented

2015-01-31 08:14:35 +01:00

Added subscriber: @Masterchef365

Sergey Sharybin self-assigned this 2015-01-31 09:40:26 +01:00

Sergey Sharybin commented

2015-01-31 09:40:26 +01:00

Please never attach system info as an inlined text since it makes report almost unreadable. Attach as the file instead.

The setup might be not totally trivial for GPU, so if you're not having dedicated GPU for rendering (and separate for the display) you'll run into time limit sooner or later. This is just how CUDA works. What's worse, that's also what windows restricts even further..

But i can see crash when rendering with CPU, so there is at least something to be looked into. Will investigate.

Please never attach system info as an inlined text since it makes report almost unreadable. Attach as the file instead. The setup might be not totally trivial for GPU, so if you're not having dedicated GPU for rendering (and separate for the display) you'll run into time limit sooner or later. This is just how CUDA works. What's worse, that's also what windows restricts even further.. But i can see crash when rendering with CPU, so there is at least something to be looked into. Will investigate.

Sergey Sharybin commented

2015-01-31 10:18:10 +01:00

Ok, had a closer look. You can't actually use tangent for the volume. Tangent is a surface property, not defined for the volume.

Will commit fix for the crash (and hopefully for the driver timeout) now, but the setup wouldn't give what you're expecting from it perhaps.

Ok, had a closer look. You can't actually use tangent for the volume. Tangent is a surface property, not defined for the volume. Will commit fix for the crash (and hopefully for the driver timeout) now, but the setup wouldn't give what you're expecting from it perhaps.

blender-admin commented

2015-01-31 10:39:19 +01:00

This issue was referenced by 03cb146afa

This issue was referenced by 03cb146afa812c95acf0da7f30b3282e71bffcf0

Sergey Sharybin commented

2015-01-31 10:44:59 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2015-01-31 10:44:59 +01:00

Sergey Sharybin commented

2015-01-31 10:44:59 +01:00

Closed by commit 03cb146afa.