Black screen on GeForce 1000 series (Linux)

[gpsnoopy]

Black screen on GeForce 1000 series (Linux)

[GPSnoopy]

Hi @ohouha ,

Which version are you using?
If you have the possibility, try the Win32 prebuild binaries if you have a dual boot, to confirm that the card works fine.

Master is currently a tad broken depending on which driver you're using, as VK_KHR_ray_tracing specs got finalised (and well, doesn't exist in that form anymore).

I'm waiting on a proper Vulkan SDK release from LunarG to update the code to the final extension specs.

[ohouha]

Hi,
I am using drive:450, can you recommend which version should I use?

[GPSnoopy]

I meant for the source code (should have been clearer). Try with the latest tagged release, or lookup the history of master and pick the commit before the VK_KHR_ray_tracing PR was merged in

[ohouha]

oh, I see, thanks. I will try other versions.

[GPSnoopy]

Hey @ohouha, with your current setup, you're probably best to try Release 4.

I've updated master and tagged Release 5 which uses the latest Vulkan ray tracing extensions, but they require NVIDIA drivers 460.89. As far as I'm aware, these newer drivers are not yet available on Linux.

[hradec]

theres a beta 460.27 released today (15-Dec-2020) together with the Win10 460.89.
https://www.nvidia.com/download/driverResults.aspx/167671/en-us
Would that beta work? the release notes says Add support for the VK_KHR_ray_tracing_pipeline extension.!

[GPSnoopy]

Ah, failed to see that. Yes, that should work, in theory.

Personally, I'm lazy. I'm waiting for the official Ubuntu 20.04 packages before testing it on Linux. ;-)

[hradec]

LoL! Fair enough!

As I'm on Arch , I'll update to the latest driver and give it a go, as soon as I finish a Dockerfile to build and run it inside docker, using ubuntu 20.04! LoL

[Skipperro]

Hi,

I've tried master branch on Linux Mint 20 with NVIDIA Titan Xp and newest drivers 460.32.03 with RayTracing extensions (https://www.nvidia.com/download/driverResults.aspx/168347/en-us) and newest Vulkan SDK.

After building the app it kind of run - my GPU is loaded, I see lower FPS values with ray-tracing enabled and higher without ray-tracing. If I use WSAD keys or move mouse FPS is also changing. But no matter what I do, all I see is black window with controls and stats.

Hope it will help you, I'm really excited to see it working :)

[GPSnoopy]

I've just tested on Ubuntu 20.04 with an RTX 3090 and NVIDIA drivers 460.32.03, and it works as expected. I suspect this bug might only occur on Pascal GPUs. Unfortunately, my PC with the 1080 Ti is currently in storage.

@Skipperro Does it display anything if you uncheck the "Enable ray tracing" option?

Also, if you have a dual boot, could you test on Windows to see if it's only happening on Linux?

[Skipperro]

@GPSnoopy No, if I uncheck "Enable ray tracing" FPS jumps to 144 (which is my display refresh rate) but everything is still black.

Maybe you could include Linux binaries in next release, so I can test if I didn't make any mistake while building it?

I don't have dual-boot on my PC at home, but I've just connected with one of my PCs at work (with Quadro RTX 4000 and Windows 10 Pro) and tried Release 5 there. Got this error:

[GPSnoopy]

@Skipperro I'm surprised about the RTX 4000 failure. Was that through Remote Desktop or similar?

I've added prebuilt R5 binaries with debug info, such that the stack trace will display the method names (the 7zipped file is not that much bigger, so I might make this the default for future releases). This will help find out exactly where the RTX 4000 fails to enumerate a property: https://github.com/GPSnoopy/RayTracingInVulkan/releases/download/r5/RayTracingInVulkan.r5.WithDebugInfo.7z

Unfortunately without my 1080 Ti to locally debug the issue, it's going to be hard for me to reproduce it. Best bets include:

• a motivated soul to find a fix and raise a PR,
• a future version of the Vulkan SDK with new validation errors that spot the bug (note that the validation layers are only enabled when running the debug build),
• a future version of NVIDIA drivers (in the unlikely case it's not my fault).

The fact the the screen remains black even when not using the ray tracing pipeline implies that this is likely a bug in the application rather than a driver bug.

I would suggest that in the meantime you try other VK_KHR_ray_tracing_pipeline applications such as Quake II RTX and NVIDIA's own examples (https://github.com/nvpro-samples/vk_raytracing_tutorial_KHR). Just to make sure that it works correctly on your machine in general.

[GPSnoopy]

Would you mind trying Release 6 (https://github.com/GPSnoopy/RayTracingInVulkan/releases/tag/r6)?

It fixes several issues that were uncovered when testing the ray tracer on AMD RX 6000 series. One of these might be the same reason for the black screen you're seeing.