Thank you for reporting this issue to us. If it is not asking too much, can you add the issue details using the table format as detailed here: Default level information for reporting Graphics issues
Once we have this info I'll report it directly to our development team.
Thank You, Ronald.
Answers (N/A if not applicable)
Provide a detailed description of the issue
Intel's Vulkan driver ignores minDepth and maxDepth fields in VkViewport structure, always defaults to minDepth=0.0f and maxDepth=1.0f disallowing to use a reverse-z technique
Please place an X to the right of the option showing how often you see this issue using specific steps. (Ex: 'Every few times a game is started it flickers.' <- This would be "Often")
Always (100%): X
Very Sporadic (<20%):
Brand and Model of the system.
Custom built desktop PC
Hybrid or switchable graphics system?
ie Does it have AMD or NV graphics too?
PC also has GeForce GTX 960 in PCI Express slot, monitor cable connected to Intel HD 530 (i7 6700k)
Make and model of any Displays that are used to see the issue (see note2 below).
LFP = Local Flat Panel (Laptop panel)
EFP = External Flat Panel (Monitor you plug in)
Tested on 3 monitors:
ASUS MX239H EFP
SAMSUNG 743BM EFP
SAMSUNG 797MB EFP
but the issue can be observed on any display
How much memory [RAM] in the system (see note2 below).
Provide any other hardware needed to replicate the issue.
ie: Cables&brand, cable type [vga, hdmi, DP, etc], dock, dongles/adapters, etc
Hardware Stepping (see note1 below).
Operating System version (see note2 below).
Windows 10 AU x64 and Windows 7 x64
VBIOS (video BIOS) version. This can be found in “information page” of CUI (right click on Desktop and select “Graphics Properties”.
Graphics Driver version; for both integrated Intel and 3rd party vendors (see note2 below).
Intel: 126.96.36.19978 (15.45, tested on Windows 7 x64) and 188.8.131.5229 (15.46, tested on Windows 10 AU x64)
NVIDIA: 384.94 on Windows 7 x64, 382.05 on Windows 10 AU x64
SW or Apps version used to replicate the issue.
Vulkan SDK 1.0.51, custom built app
Single display, clone, or extended (see note2 below).
Display resolution & refresh rate setting of each display (see note2 below).
ASUS MX239H: 1920x1080@60
SAMSUNG 743BM: 1280x1024@60
SAMSUNG 797MB: 1024x768@100
AC or DC mode, i.e. is power cable plugged in or not?
How to repro
Please provide steps to replicate the issue. These steps are very crucial to finding the root cause and fix.
A screenshot to illustrate the issue is a huge plus. A video of the failure is even better! Attach to the post or provide the YouTube link.
- set minDepth=1.0f and maxDepth=0.0f in VkViewport
- clear depth buffer to 0.0f or render a triangle with depth=0.0f
- notice depth buffer isn't calculated in reverse
1 of 1 people found this helpful
I apologize for not replying sooner, I try to stay away from the "we're working on it" kind of updates.
With the information you provided, I filed internal bug ID 1406462374, and our devs were able to reproduce the issue.
Today I was informed that we have a fix checked-in, so please look forward to our next 15.46 and higher driver releases.
Thank you for taking the time to report this issue to us.
That's an excellent news, thank you for doing a fantastic job.
I will be waiting for the next driver update.
I installed the latest update that has been released yesterday (15.47.02.4815 (184.108.40.20615)) but I see no changes whatsoever.
Could you please check if the fix has been included in the mentioned update?
With viewport.minDepth=1.0f and viewport.maxDepth=0.0f, depth that should be written for a triangle with depth=0.95f is 0.05f, not 0.95f.
I use VK_FORMAT_D32_SFLOAT_S8_UINT format.
Hi again thom36,
Thank you for your reply. Let me check with our devs, I think the fix was checked-in after this particular driver package was finalized, but need to confirm it first to be sure.
I'll let you know once I have more details.