Closed kephale closed 6 years ago
Hey @kephale,
I'm trying to investigate this at the moment, and it seems to be quite weird. Device lost errors should actually not occur, and usually point to a severe mistake before the error. I've so far only been able to reproduce this with the 396 Nvidia driver, which one are you using?
Further investigation has led me to believe that the issue is not caused by scenery, but by Nvidia's new shader compiler, introduced with the 396.xx+ series of drivers. The new shader compiler can be disabled by setting the environment variable __GL_NextGenCompiler=0
, which should at least work around the problem for the moment.
Source for this: http://www.nvidia.com/download/driverResults.aspx/133859/en-us
Further issues with these driver versions are reported also by the dxvk project (https://github.com/doitsujin/dxvk/issues/267), and Nvidia reports issues with the Vulkan-only game Wolfenstein II.
93a3463 contains some new code for device-specific workarounds, the only thing it can do about this issue though is emitting a warning to set abovementioned environment variable.
This issues is successfully worked around by using a newer shader compiler version introduced with spirvcrossj 0.4.1, in commit 45cec6c3af9d74d84d3cc499d50c666b58f1fca7. Closing the issue therefore.
Note that this issue also arises in SciView: http://forum.imagej.net/t/3d-viewer-doesnt-work-with-java8/8078/9?u=kephale
I get this with a Quadro P5000 running Ubuntu 16.04 and explicitly specify VulkanRenderer (fallback to OpenGLRenderer works). This happens on texturedcube: