Black screen with Vulkan 1.2 and RTSS (work fine with Vulkan 1.1)

Hello all,

With Vulkan version 1.1, RTSS OSD worked fine in Red dead Redemption.

Since I upgraded to Vulkan version 1.2 I have a problem when I use RTSS with a Vulkan game the game window is totally black with just the OSD and everything works again when I hide the OSD.

Can you help me please ?

 

RTSS is just fine with 1.2.

 

Its fine here too.

 

For me it was just unable to launch RDR2 with RTSS/AB on. So there is something wrong here.

 

paste the output of vulkaninfo.exe (cmd prompt)

 

I specify that I have a 1070 GTX with the 456.71 drivers. When I had my old 442.59 drivers with Vulkan 1.1 there was no problem

 

Actually, I have seen this occur.

Its specific to the way certain applications load the vulkan library, and Kombuster is affected but GPU Caps Viewer is not.

Faulting application name: MSI-Kombustor-x64.exe, version: 4.1.10.0, time stamp: 0x5fd758e1
Faulting module name: vulkan-1.dll, version: 1.2.162.0, time stamp: 0x5fd3ef4d
Exception code: 0xc000041d
Fault offset: 0x00000000000390cf
Faulting process ID: 0x3018
Faulting application start time: 0x01d6fefe27d74539
Faulting application path: C:\Program Files\Geeks3D\MSI Kombustor 4 x64\MSI-Kombustor-x64.exe
Faulting module path: C:\WINDOWS\SYSTEM32\vulkan-1.dll
Report ID: 6cc146f3-b7f1-473b-ab11-50a183098720
Faulting package full name:
Faulting package-relative application ID:

@Unwinder

Attached is the crash dump
https://cdn.discordapp.com/attachme...4499956981760/MSI-Kombustor-x64.exe1.10236.7z

My loaded layers are

Code:

Vulkan Instance Version: 1.2.162


Instance Extensions: count = 15
===============================
        VK_EXT_debug_report                    : extension revision 9
        VK_EXT_debug_utils                     : extension revision 2
        VK_EXT_swapchain_colorspace            : extension revision 4
        VK_KHR_device_group_creation           : extension revision 1
        VK_KHR_display                         : extension revision 23
        VK_KHR_external_fence_capabilities     : extension revision 1
        VK_KHR_external_memory_capabilities    : extension revision 1
        VK_KHR_external_semaphore_capabilities : extension revision 1
        VK_KHR_get_display_properties2         : extension revision 1
        VK_KHR_get_physical_device_properties2 : extension revision 2
        VK_KHR_get_surface_capabilities2       : extension revision 1
        VK_KHR_surface                         : extension revision 25
        VK_KHR_surface_protected_capabilities  : extension revision 1
        VK_KHR_win32_surface                   : extension revision 6
        VK_NV_external_memory_capabilities     : extension revision 1

Layers: count = 4
=================
VK_LAYER_NV_optimus (NVIDIA Optimus layer) Vulkan version 1.2.155, layer version 1:
        Layer Extensions: count = 0
        Devices: count = 1
                GPU id = 0 (GeForce GTX 1060 6GB)
                Layer-Device Extensions: count = 0

VK_LAYER_RTSS (RTSS overlay hook bootstrap) Vulkan version 1.1.73, layer version 1:
        Layer Extensions: count = 0
        Devices: count = 1
                GPU id = 0 (GeForce GTX 1060 6GB)
                Layer-Device Extensions: count = 0

VK_LAYER_VALVE_steam_fossilize (Steam Pipeline Caching Layer) Vulkan version 1.2.136, layer version 1:
        Layer Extensions: count = 0
        Devices: count = 1
                GPU id = 0 (GeForce GTX 1060 6GB)
                Layer-Device Extensions: count = 0

VK_LAYER_VALVE_steam_overlay (Steam Overlay Layer) Vulkan version 1.2.136, layer version 1:
        Layer Extensions: count = 0
        Devices: count = 1
                GPU id = 0 (GeForce GTX 1060 6GB)
                Layer-Device Extensions: count = 0

Hmm, I can get Kombuster to crash also by trying to start it immediately after closing it - this is with just RTSS open - its fine if i wait a few seconds.

With RTSS+AB closed Kombustor starts first time every time, there does seem to be an issue here Alexey, why some things are less or half the time affected is weird. Might be either the driver or Windows 10 itself.

 

I suspect it may actually be the vulkan loader, so i'm going to test the SDK version now.

Nope, 1.2.162.1 has no differences.

 

It's very interesting your discussion but I do not see the connection with my question if you want to talk about your problem you can create your own topic

 

It's on topic, its just going over your head, sorry about that.

Depending on how the game or application initializes its renderer and loads the vulkan loader, you could either see it.....

A) Work fine
B) Crash at start
C) Draw the application window but with nothing rendered in it.

C is most likely to occur when the application is using a GUI library that isn't itself accelerated by vulkan (Wx for example)

But there is also

D) Clash with the social club vulkan layer and not draw anything to screen.

C:\Program Files\Rockstar Games\Social Club\SocialClubVulkanLayer.json

 

Ah!, well its not like kombuster needs an overlay anyway, it has its own.

I'm not sure about GREGIX's issue then, would need crash dumps.

I've tested a few different Vulkan applications at this point, and none of them fail to start or fail rendering @stivan, could you disable rockstars vulkan layer?

Dolphin-emu
GPU Caps Viewer
No Mans Sky
Serious Sam Fusion
R6:S

All working.

 

OK
SORRY guys, not RTSS was faulty here(but it triggered my problem with RDR2, or was just indicator of it)

Thing is, I did some MB swaps meantime, some dirty memory OC was done, some of it damaged my OS. RDR2 was failing in damaged OS with RTSS/AB on. This is what happens when u wanna test BAR too quick...

After painfull repairs , DISM etc. my OS is fixed, and now AB/RTSS doesn't crash RDR2 anymore and working as intended.

Sorry for fuss.