Nvidia driver discussion

[zaps166]

Nvidia introduced new Vulkan SPIR-V compiler. Games using DXVK runs very slow with it (it can be disabled by using __GL_NextGenCompiler envvar).

Comparision [3840x2160, new vs old, disabled by envvar]:

• Tomb Raider 2013 main menu (ultra, but without tesselation): [7 FPS vs 40 FPS]
• NieR:Automata (some scene, full details, anti-aliasing off): [14.5 FPS vs 24 FPS]
• Sword Art Online Hollow Realization (Teleport Gate Plaza, full details, anti-aliasing off): [13 FPS vs 45 FPS]

Moreover:

• Tomb Raider 2013 scene with tesselation enabled is black (on old nvidia shader compiler graphics is corrupted, but visible)
• Sword Art Online Fatal Bullet scene is also black
• No performance difference on Unigine Heaven (DXVK) and Vulkan Examples (native Linux)

System information

• GPU: GeForce GTX 1080
• Driver: 396.18
• Wine version: 3.5
• DXVK version: 41132b8
• X11 Compositor: none/disabled
• Nvidia Force Composition Pipeline: enabled
• UseNvKmsCompositionPipeline: false

[doitsujin]

Well, the new compiler doesn't seem to be mature yet, don't use it for gaming with DXVK. Gathering some feedback might help them improve it though, and maybe uncover some new bugs in DXVK.

As for Tessellation in Tomb Raider 2013 not working properly, that is a DXVK bug I think.

@pdaniell-nv Could you keep an eye on this thread as well?

[pdaniell-nv]

Thanks for the heads up. I'll report back when I know more.

[xpander69]

Confirming its slow. GTA V usual 60-90FPS went to 20-35 FPS Fixes GTA V sun issue though

396.18 with __GL_NextGenCompiler=1

396.18 with __GL_NextGenCompiler=0

Crysis 2 Tesselation got broken and performance went down

396.18 with __GL_NextGenCompiler=1

396.18 with __GL_NextGenCompiler=0

[vesim987]

@pdaniell-nv There is example from The Witcher 3: https://streamable.com/0zgjl it is approximately 1/3 of performance of the old compiler. Disabling Hull and Domain Shaders bumps up performance twice.

[pingubot]

Hi,

here are the issues i noticed so far:

My Card: GTX 970 Driver: 396.18

Crysis2:

• Tesselation is broken, see pictures of XPander
• Performance is minimum cut into half (gpu is fully loaded all the time)

Crysis3:

• Performance is minimum cut into half (gpu is fully loaded all the time)
• Didn't notice huge display issues yet, need to check

Battlefield Bad Company 2:

• I can enable MSAA now which crashes the game before
• Performance is 30% of the old driver and gpu load increased from ~60% to 100%
• Graphical issue, file attached:
• Enabling MSAA fixes those graphical issues

Battlefield 3:

• I can enable MSAA now which crashed the driver before
• Without MSAA the performance is unaffacted with the new driver. With MSAA 2x enabled the per is cut down to 30%, from ~ 100fps to ~30fps.

Far Cry 3:

• I can enable MSAA now which crashed the driver before
• Without MSAA the performance is unaffacted with the new driver. With MSAA 2x enabled the perf is cut down to ~36fps, from ~ 56fps.

Diablo 3:

• I can enable MSAA now which crashed the driver instntly before. But it is still not usable due to game freezes
• Performance is ~ 30 fps in the menu, was >100 fps before with MSAA disabled

Unigine Heaven.

• Doesn't launch for me anymore with Tesselation on, works with tesselation off
• No graphical issues detected so far, but was a super quick test

Many thanks ! Christian

[doitsujin]

It should be noted that not all of the games @pingubot mentioned are well-tested and some of them have known issues. I think only Crysis 2 and Unigine Heaven are expected to work properly.

[pingubot]

I haven't played all the games from beginning to the end (i did that for crysis 2, also a few hours into crysis 3, for the rest it is really less than 1 hour per game), but the things i mentioned are the things that have changed between the new and the old nvidia driver spirv compiler. So it is just to show the differences.

[pdaniell-nv]

@doitsujin Are there any SPIR-V work arounds in place for our old compiler? If so, they probably need to be removed for the new compiler in 396.18 and beyond.

[doitsujin]

@pdaniell-nv the only Nvidia-specific workaround in my compiler is adding an extra component to the coordinate vector for the OpImageSampleDref* instructions, which is legal in SPIR-V and doesn't actually seem to cause any issues with the new compiler.

With the exception of the aforementioned workaround, as well as GPUs which do not support the ShaderImageReadWithoutFormat capability, it generates the same code for all GPUs.

@pingubot What I'm trying to say is that you might simply be hitting undefined behaviour in some cases, which just happened to work for some reason with the old compiler.

[pdaniell-nv]

Ok, thanks. We're looking into the functionality and performance regressions described above.

[SveSop]

Using __GL_NextGenCompiler=1 (default) causes some sort of "black/green'ish" picture in Unigine benchmarks. This is with commit: 140dc27ea3987d79f5c37fa6f7066203efd02b15 On the other hand, there was a change vs. previous in Unigine Superposition with the setting __GL_NextGenCompiler=0 when it comes to lightreflections.. (Did not start with default =1 setting)

[pchome]

TW3:

• CPU usage: ~18%
• GPU usage: 100%
• Inverted colors (yellow == green)
• Texture glitches
• low fps (1/3, due to low cpu usage ?)
• log diff: old : warn: D3D11Device: No matching border color found for (1e+10,1e+10,1e+10,1e+10) new: warn: D3D11Device: No matching border color found for (1e+010,1e+010,1e+010,1e+010)

[pchome]

As an opposite effect to bugs in other games/applications I can report Just Cause 3 runs without issues (except green color dominated) now.

This is for wine-staging, game was launched from steam menu, no other settings touched. Without DXVK it fully unplayable, a lot of glitches and missing textures.

[dmitry64]

Tested Dark Souls 2 and Dark Souls 3 on this commit: adb1789571354141b4046882d88f654763ad3638. Both games now have inverted colors (yellow is now green) with __GL_NextGenCompiler=1. With old compiler colors are normal.

UPDATE: On the latest commit 8dfe7088fd7102f3b180868b92c53ab3680e37f0 color issues are gone (with new compiler). Or maybe it was just a glitch.

On my GTX 970 with 396.18 driver, with 1440p resolution, wine 3.5, on low settings Dark Souls 3 is playable at 40-55 FPS. If i enable shadows in graphics settings (Off->Low) performance drops to 1-2 FPS.

[nairaner]

With new compiler Path of Exile crash while loading with: NVRM: Xid (PCI:0000:01:00): 8, Channel 0000006a Setting __GL_NextGenCompiler=0 makes the game work Using DXVK: 8dfe7088fd7102f3b180868b92c53ab3680e37f0 PathOfExile_x64_d3d11.log PathOfExile_x64_dxgi.log shaders.zip

[pingubot]

Want to add FEAR 3 to the list of affected games: All game settings at max, 1920x1080, MSAAx 4. GPU load is 100% with the new and with the old compiler:

Driver 396.18:

New Compiler: 9 fps Old Compiler: 63 fps

Disabling MSAA leads to:

New Compiler: ~ 35fps Old Compiler: ~ 150fps

Many thanks ! Christian

[Glog78]

Want to add Skyrim SE to the list of affected games:

New Compiler = 3.5 to 5 fps Old Compiler = 60+ fps (vsync on)

Settings have no influence at all on the bad performance of the New Compiler.

[tpruzina]

I suggest using __GL_NextGenCompiler=0 until this gets resolved (presumably upstream problem).

[pingubot]

Want to add Dirt 2 demo to the list:

Old Compiler: No graphical issues, ca. 100fps in menu outside New Comppiler: ~ 15fps in menu outisde and those funky pictures:

[pdaniell-nv]

Thanks for all the reports posted here on our 396.18 driver. We have just released a new 396.18.02 beta driver on our Vulkan driver page here: https://developer.nvidia.com/vulkan-driver

This should resolve some of the performance and corruption issues reported. As an added bonus this driver also increases the number of UBOs allowed per shader stage from 12 to 15 as discussed in issue https://github.com/doitsujin/dxvk/issues/90.

We look forward to hearing feedback on the new 396.18.02 driver. Thanks!

[varris1]

Driver version: 396.18.02 DXVK: b82ae16 Card: GTX 970

This is what Overwatch via DXVK (b82ae16) looks like with: __GL_NextGenCompiler=1 https://imgur.com/a/eNRnK

__GL_NextGenCompiler=0 https://imgur.com/a/9Knko

So it seems like there is still some corruption going on.

EDIT: fixed with commit 5eaacf7

[varris1]

Driver version: 396.18.02 DXVK: 05a96e9 Card: GTX 970

This Unity engine demo seems to have issues with corruption as well: https://blogs.unity3d.com/en/2015/06/24/releasing-the-blacksmith/

__GL_NextGenCompiler=1: https://imgur.com/a/9xfhs

__GL_NextGenCompiler=0: https://imgur.com/a/mZKTi

EDIT: fixed with commit 5eaacf7

[sambow23]

Driver: 396.18.02 DXVK: 05a96e9 GPU: GTX 1060 6GB

The performance issues on GTAV with __GL_NextGenCompiler=1 are fixed, but with the maximum settings, this line exists onscreen

This does not happen with __GL_NextGenCompiler=0

[pdaniell-nv]

For the issue with the Unity engine demo that @varris1 reported, it appears the SPIR-V is invalid in at least one of the shaders. In one of them there is this:

        %84 = OpFAdd %v3float %79 %83
        %85 = OpLoad %float %o0
        %86 = OpVectorShuffle %float %85 %84
              OpStore %o0 %86

In this example %o0 is actually a pointer to v4float and the OpVectorShuffle should have be used with vector types. So some kind of scalar/vector mixup going on. Actually the spir-v validator catches the OpLoad type mismatch above, but not the OpVectorShuffle issue.

[doitsujin]

@pdaniell-nv what are the settings that generate the invalid shader? Just tested with Higher and I'm not getting spirv-val errors on any of the spir-v shaders.

Edit: Not getting any errors with the other presets either.

[pdaniell-nv]

This was with "High" the default. Not sure why we're seeing different results. Are you setting anything like DXVK_SHADER_OPTIMIZE=1?

[doitsujin]

No. I removed that knob a while ago as well.

That said, I do remember fixing a similar issue before tagging dxvk v0.42. Any chance you're running an old dxvk build?

[varris1]

I used the "higher" preset as well. Sorry for not mentioning that.

[pdaniell-nv]

We're not sure why we're getting different results. We're using https://haagch.frickel.club/files/dxvk/r994.05a96e9/64/bin/ and http://democontent.unity3d.com/BlacksmithStandalone_2015-06-24_0-00-06.05%202.7z and reproducing on Windows.

[pdaniell-nv]

Here is our dump of the SPIR-V of the problematic shader. dump.4451.zip

[doitsujin]

@ZeroFault just reported a similar issue and sent me the faulty shaders. It looks like the demo itself generates different shaders depending on which GPU is being used, because I definitely don't see those shaders in my shader dump.

I'll look into that bug in my compiler.

[pingubot]

Hi,

thanks for the quick driver update, here is an update with the new beta driver:

My Card: GTX 970 Driver: 396.18.02

Crysis2->still the same issues:

• Tesselation is broken, see pictures of XPander
• Performance is a little bit better, but still much worse than the old compiler(gpu is fully loaded all the time)

Crysis3->Edit: Not fixed

• Performance now seems similar to the old compiler
• Noticed display issues now:

Battlefield Bad Company 2->seems fixed:

• I can enable MSAA now which crashes the game before
• Performance is equal now to the old compiler
• Graphical issues when reloading a map(similar issue with the older driver an bf3, so this could be a dxvk issue as well), file attached:

Diablo 3->seems fixed:

• I can enable MSAA now which crashed the driver instntly before. Game works fine now with MSAA on.
• Performance is similar to the old compiler

Fear 3 -> seems fixed

• Perf is equal and partly a little bit faster than with the old compiler, no visual issues noticed.

Many thanks for fixing many of the issues already !

Many thanks ! Christian

[pchome]

Card: GTX 750 Ti Driver: 396.18.02

Superposition: still have rough shadows (https://github.com/doitsujin/dxvk/issues/267#issuecomment-380541358) The Witcher 3: performance fixed; ground near the character became transparent (not fixed)

[doitsujin]

@pdaniell-nv The Blacksmith shader issue should be fixed as of 8eb78591a0657e711d6a7cdcdf90382681b69036. There's something weird about the DXBC shaders that it generates on some systems, not sure if it does the right thing - but the SPIR-V should be valid.

[ZeroFault]

@pdaniell-nv

Could we also get some help on the buffer creation issue with Nvidia drivers here, please? It seems to affect the Windows/Linux drivers including the beta drivers as well.

[varris1]

I tried the blacksmith demo again with DXVK commit 8eb7859 and the same kind of artifacts are still there, so it doesn't look like it's entirely fixed yet.

[jeffbolznv]

Hi @doitsujin, unity.1.spv.zip

I'm the NVIDIA driver/compiler engineer that has been looking at some of these issues. I debugged the Unity Blacksmith demo again, and found another instance of invalid SPIR-V. In this case, the shader uses the gs_vertex_in variable which is not listed in the entry point's interface, and this leads to the geometry corruption in https://github.com/doitsujin/dxvk/issues/267#issuecomment-382181673.

I've also poked spirv-tools issue https://github.com/KhronosGroup/SPIRV-Tools/issues/1120 which would have caught this.

[doitsujin]

@jeffbolznv Thanks for letting me know, 5eaacf74594f4558483917f6f0ecc1c5fd713dff should fix this. Sorry for the inconvenience.

[varris1]

Confirming that 5eaacf7 fixed both the corrupted Overwatch fonts and the Blacksmith demo.

Good job to everyone involved.

EDIT: on unrelated note: Please let us increase the shader cache in the driver via an env variable. Overwatch has tons and tons of shaders and the limit of 128 MB is way too low.

[daschaffert]

Does this commit 5eaacf7 also fixes the bad ground in witcher3 ?

[pingubot]

Did some additional tests with Driver: 396.18.02: DXVK: 5eaacf7

Dirt 2 Demo: Same isse like before with 396.18 :

Unigine Heaven, Unigine Valley, Unigine Superposition:

• Work all fine here, Superpos is working correctly now, thanks to raising the ubo limit !

Looking forward to the next beta driver with new fixes :)

[pchome]

It's looks like all reported resource limits are changed only for some certain GPUs in 396.18.02 : http://vulkan.gpuinfo.org/compare.php?compare=compare&id[3072]=on&id[3040]=on&id[3035]=on&id[2935]=on

That's explains why shadow artefacts still there in superposition for me (750 Ti) while others reported them as fixed.

[pdaniell-nv]

Hmm, that's not expected. Any chance that vulkaninfo was captured with __GL_NextGenCompiler=0?

[pchome]

@pdaniell-nv Oh, yes, I forgot about __GL_NextGenCompiler=0 was set as global env variable. But __GL_NextGenCompiler=1 for separate WINE prefixes, so artefacts in superposition detected with new compiler.

Now my device in database and I cant resend correct data, but here are reported limits for __GL_NextGenCompiler=1 from json file:

"limits": {
            "bufferImageGranularity": "0x10000",
            "discreteQueuePriorities": 2,
            "framebufferColorSampleCounts": 15,
            "framebufferDepthSampleCounts": 15,
            "framebufferNoAttachmentsSampleCounts": 15,
            "framebufferStencilSampleCounts": 15,
            "lineWidthGranularity": 0.125,
            "lineWidthRange": [ 0.5, 10 ],
            "maxBoundDescriptorSets": 8,
            "maxClipDistances": 8,
            "maxColorAttachments": 8,
            "maxCombinedClipAndCullDistances": 8,
            "maxComputeSharedMemorySize": 49152,
            "maxComputeWorkGroupCount": [ 2147483647, 65535, 65535 ],
            "maxComputeWorkGroupInvocations": 1536,
            "maxComputeWorkGroupSize": [ 1536, 1024, 64 ],
            "maxCullDistances": 8,
            "maxDescriptorSetInputAttachments": 1048576,
            "maxDescriptorSetSampledImages": 1048576,
            "maxDescriptorSetSamplers": 1048576,
            "maxDescriptorSetStorageBuffers": 1048576,
            "maxDescriptorSetStorageBuffersDynamic": 16,
            "maxDescriptorSetStorageImages": 1048576,
            "maxDescriptorSetUniformBuffers": 90,
            "maxDescriptorSetUniformBuffersDynamic": 15,
            "maxDrawIndexedIndexValue": 4294967295,
            "maxDrawIndirectCount": 4294967295,
            "maxFragmentCombinedOutputResources": 16,
            "maxFragmentDualSrcAttachments": 1,
            "maxFragmentInputComponents": 128,
            "maxFragmentOutputAttachments": 8,
            "maxFramebufferHeight": 16384,
            "maxFramebufferLayers": 2048,
            "maxFramebufferWidth": 16384,
            "maxGeometryInputComponents": 128,
            "maxGeometryOutputComponents": 128,
            "maxGeometryOutputVertices": 1024,
            "maxGeometryShaderInvocations": 32,
            "maxGeometryTotalOutputComponents": 1024,
            "maxImageArrayLayers": 2048,
            "maxImageDimension1D": 16384,
            "maxImageDimension2D": 16384,
            "maxImageDimension3D": 2048,
            "maxImageDimensionCube": 16384,
            "maxInterpolationOffset": 0.4375,
            "maxMemoryAllocationCount": 4294967295,
            "maxPerStageDescriptorInputAttachments": 1048576,
            "maxPerStageDescriptorSampledImages": 1048576,
            "maxPerStageDescriptorSamplers": 1048576,
            "maxPerStageDescriptorStorageBuffers": 1048576,
            "maxPerStageDescriptorStorageImages": 1048576,
            "maxPerStageDescriptorUniformBuffers": 15,
            "maxPerStageResources": 4294967295,
            "maxPushConstantsSize": 256,
            "maxSampleMaskWords": 1,
            "maxSamplerAllocationCount": 4000,
            "maxSamplerAnisotropy": 16,
            "maxSamplerLodBias": 15,
            "maxStorageBufferRange": 4294967295,
            "maxTessellationControlPerPatchOutputComponents": 120,
            "maxTessellationControlPerVertexInputComponents": 128,
            "maxTessellationControlPerVertexOutputComponents": 128,
            "maxTessellationControlTotalOutputComponents": 4216,
            "maxTessellationEvaluationInputComponents": 128,
            "maxTessellationEvaluationOutputComponents": 128,
            "maxTessellationGenerationLevel": 64,
            "maxTessellationPatchSize": 32,
            "maxTexelBufferElements": 134217728,
            "maxTexelGatherOffset": 31,
            "maxTexelOffset": 7,
            "maxUniformBufferRange": 65536,
            "maxVertexInputAttributeOffset": 2047,
            "maxVertexInputAttributes": 32,
            "maxVertexInputBindingStride": 2048,
            "maxVertexInputBindings": 32,
            "maxVertexOutputComponents": 128,
            "maxViewportDimensions": [ 16384, 16384 ],
            "maxViewports": 16,
            "minInterpolationOffset": -0.5,
            "minMemoryMapAlignment": "0x40",
            "minStorageBufferOffsetAlignment": "0x20",
            "minTexelBufferOffsetAlignment": "0x10",
            "minTexelGatherOffset": -32,
            "minTexelOffset": -8,
            "minUniformBufferOffsetAlignment": "0x100",
            "mipmapPrecisionBits": 8,
            "nonCoherentAtomSize": "0x40",
            "optimalBufferCopyOffsetAlignment": "0x1",
            "optimalBufferCopyRowPitchAlignment": "0x1",
            "pointSizeGranularity": 0.125,
            "pointSizeRange": [ 1, 189.875 ],
            "sampledImageColorSampleCounts": 15,
            "sampledImageDepthSampleCounts": 15,
            "sampledImageIntegerSampleCounts": 15,
            "sampledImageStencilSampleCounts": 15,
            "sparseAddressSpaceSize": "0xffffffffffffffff",
            "standardSampleLocations": 1,
            "storageImageSampleCounts": 15,
            "strictLines": 1,
            "subPixelInterpolationOffsetBits": 4,
            "subPixelPrecisionBits": 8,
            "subTexelPrecisionBits": 8,
            "timestampComputeAndGraphics": 1,
            "timestampPeriod": 1,
            "viewportBoundsRange": [ -32768, 32768 ],
            "viewportSubPixelBits": 8
        },

[pchome]

Correct data posted from WINE prefix: http://vulkan.gpuinfo.org/compare.php?compare=compare&id[3074]=on&id[3040]=on&id[3035]=on&id[2935]=on

[zaps166]

Witcher 3 crashes at startup (Wine 3.6, NVIDIA drivers 396.18.02), Steam Overlay disabled. Other games works OK.

Backtrace:
=>0 0x00007fee81c53f82 in libglx_nvidia.so.0 (+0xadf82) (0x000000000000000c)
  1 0x00007fee81c54932 in libglx_nvidia.so.0 (+0xae931) (0x0000000000000008)
  2 0x00007fee81c5fa5b in libglx_nvidia.so.0 (+0xb9a5a) (0x00007fee81c5df60)
  3 0x00007fee81bf47a8 in libglx_nvidia.so.0 (+0x4e7a7) (0x00007fee818df060)
  4 0x00007ff889b1043a call_init.part+0x59() in ld-linux-x86-64.so.2 (0x0000000000000002)
  5 0x00007ff889b10586 _dl_init+0x75() in ld-linux-x86-64.so.2 (0x0000000000000002)
  6 0x00007ff889b14a5e dl_open_worker+0x38d() in ld-linux-x86-64.so.2 (0x000000000213e170)
  7 0x00007ff8892b6b64 _dl_catch_error+0x83() in libc.so.6 (0x000000000213e370)
  8 0x00007ff889b1427a _dl_open+0xc9() in ld-linux-x86-64.so.2 (0x000000000213e370)
  9 0x00007ff888f24e86 GLIBC_2.3+0xe85() in libdl.so.2 (0x00007ff888f24e30)
  10 0x00007ff8892b6b64 _dl_catch_error+0x83() in libc.so.6 (0x00007ff888f24e30)
  11 0x00007ff888f25587 in libdl.so.2 (+0x1586) (0x00007ff888f24e30)
  12 0x00007ff888f24f22 GLIBC_2.3+0xf21() in libdl.so.2 (0x000000000213ea20)
  13 0x00007ff882994eb0 in libvulkan.so.1 (+0x26eaf) (0x000000000213ea20)
  14 0x00007ff882999138 in libvulkan.so.1 (+0x2b137) (0x000000000213ec24)
  15 0x00007ff88299aebf vkEnumerateInstanceExtensionProperties+0x19e() in libvulkan.so.1 (0x0000000000000002)
  16 0x00007ff8848362f2 in winex11 (+0x362f1) (0x000000000213ed10)
  17 0x00007ff88748faa4 wine_vkEnumerateInstanceExtensionProperties+0x183() in winevulkan (0x000000000213ed10)
  18 0x00007ff8891639b2 vkEnumerateInstanceExtensionProperties+0x81() in vulkan-1 (0x000000000213ee10)
  19 0x000000006f2464ba dxvk::vk::NameSet::addInstanceLayerExtensions+0x39(this=0x213f0e0, vkl=0x24aae40, layer=0x0(nil)) [/home/tomo/Desktop/dxvk/build.w64/../src/dxvk/vulkan/dxvk_vulkan_loader_fn.h:39] in dxgi (0x00000000024aae40)
  20 0x000000006f24681f dxvk::vk::NameSet::enumerateInstanceExtensions+0x4e(vkl=0x24aae40, layers=0x213f330) [/home/tomo/Desktop/dxvk/build.w64/../src/dxvk/vulkan/dxvk_vulkan_extensions.cpp:30] in dxgi (0x00000000024aae40)
  21 0x000000006f22dc3a dxvk::DxvkInstance::getExtensions+0x59(this=0x24a8a60, layers=0x213f330) [/home/tomo/Desktop/dxvk/build.w64/../src/dxvk/dxvk_instance.cpp:97] in dxgi (0x00000000024aae70)
  22 0x000000006f22e7a1 dxvk::DxvkInstance::createInstance+0x30(this=0x24a8a60) [/home/tomo/Desktop/dxvk/build.w64/../src/dxvk/dxvk_instance.cpp:35] in dxgi (0x000000000213f350)
  23 0x000000006f22eaf5 DxvkInstance+0x34(this=0x24a8a60) [/home/tomo/Desktop/dxvk/build.w64/../src/dxvk/dxvk_instance.cpp:7] in dxgi (0x000000000213f8e0)
  24 0x000000006f20635b DxgiFactory+0x4a(this=0x24aade0) [/home/tomo/Desktop/dxvk/build.w64/../src/dxgi/dxgi_factory.cpp:7] in dxgi (0x000000000213f8e0)
  25 0x000000006f2066c1 dxvk::createDxgiFactory+0x60(riid=<internal error>, ppFactory=0x213f7f0) [/home/tomo/Desktop/dxvk/build.w64/../src/dxgi/dxgi_main.cpp:18] in dxgi (0x000000000213f8e0)
  26 0x0000000002a7b678 in gameoverlayrenderer64 (+0x8b677) (0x000000000213f8e0)
  27 0x0000000140006608 in witcher3 (+0x6607) (0x000000000213f8e0)
  28 0x00000001400010e4 in witcher3 (+0x10e3) (0x000000000213f8e0)
  29 0x000000014004436d in witcher3 (+0x4436c) (0x000000000213ffd0)
  30 0x00000001400034bf in witcher3 (+0x34be) (0x000000000213ffd0)
  31 0x000000014000378c in witcher3 (+0x378b) (0x000000000213ffd0)
  32 0x0000000140e7c368 in witcher3 (+0xe7c367) (0x000000000213ffd0)
  33 0x000000007b47c06a in kernel32 (+0x5c069) (0x000000000213ffd0)

[damienleone]

Hi @zaps166, does the issue go away if you set this envvar?

$ __GL_CONSTANT_FRAME_RATE_HINT=3

[zaps166]

Hi @damienleone, Yes, the game runs properly with __GL_CONSTANT_FRAME_RATE_HINT=3, thanks!

Btw. is it possible to fix two "Allow Flipping" issues with Vulkan applications?

[damienleone]

Thanks for confirming. This issue will be resolved in a later release (not from 396). You can keep using that envvar in the meantime. I'll take a look at the flipping issues you mentioned.

[zaps166]

I'll take a look at the flipping issues you mentioned.

Ok, thanks!