Screen Glithes when Using Vulkan 4K@60HZ
When using Vulkan in 4K@60hz Resolution, I get these screen issues: https://i.imgur.com/4mvkoV7.jpg . It is in every Vulkan Game I tested: Doom 2016, Wolfenstein II, The Talos Principle and even when I'm using Dolphin (the Wii emulator) in vulkan mode. It does not happen when the resolution is < 4K , or when the graphics API is DX11, DX12 or OpenGL. And, the problem is not visible on Screenshots, as you can see here: https://i.imgur.com/RBl9x21.jpg -screenshot https://i.imgur.com/lFoe9Rm.jpg - taken with phone. I tried a different 4k display usnig HDMI 2.0 @60Hz, same issue. So not a connector or cable or display issue. The chances of that would be pretty rare. I disabled nvidia overlay, I disabled msi afterburner and RTSS. So annoying, what causes this??
When using Vulkan in 4K@60hz Resolution, I get these screen issues: https://i.imgur.com/4mvkoV7.jpg . It is in every Vulkan Game I tested: Doom 2016, Wolfenstein II, The Talos Principle and even when I'm using Dolphin (the Wii emulator) in vulkan mode.

It does not happen when the resolution is < 4K , or when the graphics API is DX11, DX12 or OpenGL.

And, the problem is not visible on Screenshots, as you can see here:


https://i.imgur.com/RBl9x21.jpg
-screenshot


https://i.imgur.com/lFoe9Rm.jpg
- taken with phone.

I tried a different 4k display usnig HDMI 2.0 @60Hz, same issue. So not a connector or cable or display issue. The chances of that would be pretty rare.

I disabled nvidia overlay, I disabled msi afterburner and RTSS.

So annoying, what causes this??

#1
Posted 11/06/2017 09:44 AM   
if the problem isn't visible on a screenshot, then the framebuffer is ok, so the card has rendered the picture just fine. So that makes the fault on the application developers part, which isn't surprising given most Vulkan devs so far have failed at device enumeration and swap interval management.
if the problem isn't visible on a screenshot, then the framebuffer is ok, so the card has rendered the picture just fine.

So that makes the fault on the application developers part, which isn't surprising given most Vulkan devs so far have failed at device enumeration and swap interval management.



In Memory of Chris "ChrisRay" Arthington, 1982-2010

Specs:
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:ROG PG279Q, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX200 250
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme

WIP:
CPU:Intel Xeon x5660, Mainboard:Asus Rampage II Gene, Memory:16GB Corsair Vengeance 1600 LP
Video:EVGA Geforce GTX 680+ 4GB, Palit Geforce GTX 550ti
Monitor:Pending, Sound:Pending
SDD:Pending
HDD:Pending
Case:NZXT Guardian 921RB, PSU:Corsair 620HX, OS:Windows 7 SP1
Cooler: ThermalRight True Spirit 120M

#2
Posted 11/06/2017 10:02 AM   
I understand that it's happening in Wolfenstein, first because it "prefers" AMD hardware, and second because it's fairly new. But I have played all through Doom late 2016, though I cannot recall any glitches like they are appearing now. So you think it's a driver issue or an issue on Doom's end (i.e. any Vulkan game)? Since I don't know much about technical stuff, I don't understand device enumaration or swap interval management... And why am I seemingly the only one experiencing these issues? So many players out there using Nvidia hardware and I don't find this documented anywhere.
I understand that it's happening in Wolfenstein, first because it "prefers" AMD hardware, and second because it's fairly new. But I have played all through Doom late 2016, though I cannot recall any glitches like they are appearing now. So you think it's a driver issue or an issue on Doom's end (i.e. any Vulkan game)?

Since I don't know much about technical stuff, I don't understand device enumaration or swap interval management...

And why am I seemingly the only one experiencing these issues? So many players out there using Nvidia hardware and I don't find this documented anywhere.

#3
Posted 11/06/2017 10:44 AM   
It's an issue caused by a late specification change in Vulkan that nvidia have opted to include [u]now[/u] while there are still few vulkan titles rather than later when it would be a 'diplomatic matter' and screw many out of getting patched. http://vulkan-spec-chunked.ahcox.com/ch29s06.html https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#_wsi_swapchain [quote] Implemented improved behavior for full-screen Vulkan swapchains using VK_KHR_win32_surface. This optimization will cause more events that trigger an out-of-date swapchain, such as when entering or leaving full-screen mode (typically by pressing Alt+tab). Applications that do not properly respond to the VK_ERROR_OUT_OF_DATE_KHR return code may not function properly when these events occur. See the WSI Swapchain section of the Vulkan specification.[/quote]
It's an issue caused by a late specification change in Vulkan that nvidia have opted to include now while there are still few vulkan titles rather than later when it would be a 'diplomatic matter' and screw many out of getting patched.

http://vulkan-spec-chunked.ahcox.com/ch29s06.html

https://www.khronos.org/registry/vulkan/specs/1.0-extensions/html/vkspec.html#_wsi_swapchain


Implemented improved behavior for full-screen Vulkan swapchains using VK_KHR_win32_surface.

This optimization will cause more events that trigger an out-of-date swapchain, such as when entering or leaving full-screen mode (typically by pressing Alt+tab). Applications that do not properly respond to the
VK_ERROR_OUT_OF_DATE_KHR return code may not function properly when these events occur. See the WSI Swapchain section of the Vulkan specification.



In Memory of Chris "ChrisRay" Arthington, 1982-2010

Specs:
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:ROG PG279Q, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX200 250
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme

WIP:
CPU:Intel Xeon x5660, Mainboard:Asus Rampage II Gene, Memory:16GB Corsair Vengeance 1600 LP
Video:EVGA Geforce GTX 680+ 4GB, Palit Geforce GTX 550ti
Monitor:Pending, Sound:Pending
SDD:Pending
HDD:Pending
Case:NZXT Guardian 921RB, PSU:Corsair 620HX, OS:Windows 7 SP1
Cooler: ThermalRight True Spirit 120M

#4
Posted 11/06/2017 11:22 AM   
I'm sure I didn't really understand most of it, but I thought I just change the "rendering surface" and switched to Borderless Fullscreen, and the issues disappeared. I mean, if it works this way... I take the borderless Fullscreen
I'm sure I didn't really understand most of it, but I thought I just change the "rendering surface" and switched to Borderless Fullscreen, and the issues disappeared. I mean, if it works this way... I take the borderless Fullscreen

#5
Posted 11/06/2017 11:59 AM   
That is an effective work around, it basically removes the vulkan swapchain from the situation.
That is an effective work around, it basically removes the vulkan swapchain from the situation.



In Memory of Chris "ChrisRay" Arthington, 1982-2010

Specs:
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:ROG PG279Q, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX200 250
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme

WIP:
CPU:Intel Xeon x5660, Mainboard:Asus Rampage II Gene, Memory:16GB Corsair Vengeance 1600 LP
Video:EVGA Geforce GTX 680+ 4GB, Palit Geforce GTX 550ti
Monitor:Pending, Sound:Pending
SDD:Pending
HDD:Pending
Case:NZXT Guardian 921RB, PSU:Corsair 620HX, OS:Windows 7 SP1
Cooler: ThermalRight True Spirit 120M

#6
Posted 11/06/2017 11:48 PM   
[quote="Kaiser King"]When using Vulkan in 4K@60hz Resolution, I get these screen issues: https://i.imgur.com/4mvkoV7.jpg . It is in every Vulkan Game I tested: Doom 2016, Wolfenstein II, The Talos Principle and even when I'm using Dolphin (the Wii emulator) in vulkan mode. It does not happen when the resolution is < 4K , or when the graphics API is DX11, DX12 or OpenGL. And, the problem is not visible on Screenshots, as you can see here: https://i.imgur.com/RBl9x21.jpg -screenshot https://i.imgur.com/lFoe9Rm.jpg - taken with phone. I tried a different 4k display usnig HDMI 2.0 @60Hz, same issue. So not a connector or cable or display issue. The chances of that would be pretty rare. I disabled nvidia overlay, I disabled msi afterburner and RTSS. So annoying, what causes this??[/quote] I'm having the same issue. It only happens when I play any Vulkan game at 4k via HDMI. I don't have the option to use any other input as I am using a UHDTV. This issue just started happening a couple of Nvidia dirver updates ago. Vulkan currently doesn't work properly and this was not an issue in the past. How can I report this to get a fix? Has anyone found any workarounds?
Kaiser King said:When using Vulkan in 4K@60hz Resolution, I get these screen issues: https://i.imgur.com/4mvkoV7.jpg . It is in every Vulkan Game I tested: Doom 2016, Wolfenstein II, The Talos Principle and even when I'm using Dolphin (the Wii emulator) in vulkan mode.

It does not happen when the resolution is < 4K , or when the graphics API is DX11, DX12 or OpenGL.

And, the problem is not visible on Screenshots, as you can see here:

https://i.imgur.com/RBl9x21.jpg
-screenshot

https://i.imgur.com/lFoe9Rm.jpg
- taken with phone.

I tried a different 4k display usnig HDMI 2.0 @60Hz, same issue. So not a connector or cable or display issue. The chances of that would be pretty rare.

I disabled nvidia overlay, I disabled msi afterburner and RTSS.

So annoying, what causes this??

I'm having the same issue. It only happens when I play any Vulkan game at 4k via HDMI. I don't have the option to use any other input as I am using a UHDTV. This issue just started happening a couple of Nvidia dirver updates ago. Vulkan currently doesn't work properly and this was not an issue in the past. How can I report this to get a fix? Has anyone found any workarounds?

#7
Posted 12/02/2017 10:49 PM   
[quote="PCGamer247"][quote="Kaiser King"]When using Vulkan in 4K@60hz Resolution, I get these screen issues: https://i.imgur.com/4mvkoV7.jpg . It is in every Vulkan Game I tested: Doom 2016, Wolfenstein II, The Talos Principle and even when I'm using Dolphin (the Wii emulator) in vulkan mode. It does not happen when the resolution is < 4K , or when the graphics API is DX11, DX12 or OpenGL. And, the problem is not visible on Screenshots, as you can see here: https://i.imgur.com/RBl9x21.jpg -screenshot https://i.imgur.com/lFoe9Rm.jpg - taken with phone. I tried a different 4k display usnig HDMI 2.0 @60Hz, same issue. So not a connector or cable or display issue. The chances of that would be pretty rare. I disabled nvidia overlay, I disabled msi afterburner and RTSS. So annoying, what causes this??[/quote] I'm having the same issue. It only happens when I play any Vulkan game at 4k via HDMI. I don't have the option to use any other input as I am using a UHDTV. This issue just started happening a couple of Nvidia dirver updates ago. Vulkan currently doesn't work properly and this was not an issue in the past. How can I report this to get a fix? Has anyone found any workarounds?[/quote] OK so it seems to be an issue when VSYNC is enabled. Hopefully NVIDIA will fix this problem as it only happens with Vulkan and I have been running games with Vulkan no problem up until recently. I am using a Samsung 4k SUHDTV and never had any problems with this. Please fix Nvidia.
PCGamer247 said:
Kaiser King said:When using Vulkan in 4K@60hz Resolution, I get these screen issues: https://i.imgur.com/4mvkoV7.jpg . It is in every Vulkan Game I tested: Doom 2016, Wolfenstein II, The Talos Principle and even when I'm using Dolphin (the Wii emulator) in vulkan mode.

It does not happen when the resolution is < 4K , or when the graphics API is DX11, DX12 or OpenGL.

And, the problem is not visible on Screenshots, as you can see here:


https://i.imgur.com/RBl9x21.jpg
-screenshot


https://i.imgur.com/lFoe9Rm.jpg
- taken with phone.

I tried a different 4k display usnig HDMI 2.0 @60Hz, same issue. So not a connector or cable or display issue. The chances of that would be pretty rare.

I disabled nvidia overlay, I disabled msi afterburner and RTSS.

So annoying, what causes this??

I'm having the same issue. It only happens when I play any Vulkan game at 4k via HDMI. I don't have the option to use any other input as I am using a UHDTV. This issue just started happening a couple of Nvidia dirver updates ago. Vulkan currently doesn't work properly and this was not an issue in the past. How can I report this to get a fix? Has anyone found any workarounds?

OK so it seems to be an issue when VSYNC is enabled. Hopefully NVIDIA will fix this problem as it only happens with Vulkan and I have been running games with Vulkan no problem up until recently. I am using a Samsung 4k SUHDTV and never had any problems with this. Please fix Nvidia.

#8
Posted 12/02/2017 11:44 PM   
nvidia won't be fixing this problem, the game developer has to.
nvidia won't be fixing this problem, the game developer has to.



In Memory of Chris "ChrisRay" Arthington, 1982-2010

Specs:
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:ROG PG279Q, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX200 250
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme

WIP:
CPU:Intel Xeon x5660, Mainboard:Asus Rampage II Gene, Memory:16GB Corsair Vengeance 1600 LP
Video:EVGA Geforce GTX 680+ 4GB, Palit Geforce GTX 550ti
Monitor:Pending, Sound:Pending
SDD:Pending
HDD:Pending
Case:NZXT Guardian 921RB, PSU:Corsair 620HX, OS:Windows 7 SP1
Cooler: ThermalRight True Spirit 120M

#9
Posted 12/03/2017 12:40 AM   
[quote="Sora"]nvidia won't be fixing this problem, the game developer has to.[/quote] It's an issue with the Vulkan API. Until the latest drivers, the last 3 versions there was not a problem with Vulkan at 4k with VSYNC. If you rollback to older versions of the NVIDIA drivers like 3 months ago all Vulkan games work fine. It's a driver issue.
Sora said:nvidia won't be fixing this problem, the game developer has to.

It's an issue with the Vulkan API. Until the latest drivers, the last 3 versions there was not a problem with Vulkan at 4k with VSYNC. If you rollback to older versions of the NVIDIA drivers like 3 months ago all Vulkan games work fine. It's a driver issue.

#10
Posted 12/03/2017 09:02 AM   
no it isn't, its an intentional specfication change. do catch up.
no it isn't, its an intentional specfication change.

do catch up.



In Memory of Chris "ChrisRay" Arthington, 1982-2010

Specs:
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition
Monitor:ROG PG279Q, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro
SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX200 250
HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black
Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1
Cooler: ThermalRight Silver Arrow IB-E Extreme

WIP:
CPU:Intel Xeon x5660, Mainboard:Asus Rampage II Gene, Memory:16GB Corsair Vengeance 1600 LP
Video:EVGA Geforce GTX 680+ 4GB, Palit Geforce GTX 550ti
Monitor:Pending, Sound:Pending
SDD:Pending
HDD:Pending
Case:NZXT Guardian 921RB, PSU:Corsair 620HX, OS:Windows 7 SP1
Cooler: ThermalRight True Spirit 120M

#11
Posted 12/03/2017 02:57 PM   
[quote="Sora"]no it isn't, its an intentional specfication change. do catch up.[/quote] What spec change is that? HDMI? 60hz? 4k?
Sora said:no it isn't, its an intentional specfication change.

do catch up.


What spec change is that? HDMI? 60hz? 4k?

#12
Posted 12/07/2017 02:14 PM   
[quote="Sora"]no it isn't, its an intentional specfication change. do catch up.[/quote] I'm using standard issue gear here that is becoming pretty common. 4k via HDMI @60hz. Is that not a thing or what?
Sora said:no it isn't, its an intentional specfication change.

do catch up.

I'm using standard issue gear here that is becoming pretty common. 4k via HDMI @60hz. Is that not a thing or what?

#13
Posted 12/07/2017 02:40 PM   
Scroll To Top