"dxgi.nvapiHack = False" ignored, reporting AMD GPU.

Techwolf commented 4 years ago

Software information

Elder Scrolls Online

System information

GPU: GeForce RTX 2070
Driver: 450.51.0
Wine version: 5.11
DXVK version: 1.7

Log files

eso64_d3d11.log eso64_dxgi.log

When running game, I notice in the console output that setting the AMD hack off fails to do so:

info:  DXGI: NvAPI workaround enabled, reporting AMD GPU
248c:fixme:ole:CoInitializeSecurity (0000000000000000,-1,0000000000000000,0000000000000000,0,3,0000000000000000,0,0000000000000000) - stub!
248c:fixme:wbemprox:client_security_SetBlanket 00007F90F1FB8720, 000000000104F1C0, 10, 0, (null), 3, 3, 0000000000000000, 0x00000000
248c:fixme:wbemprox:client_security_Release 00007F90F1FB8720
info:  Game: eso64.exe
info:  DXVK: v1.7
info:  Found config file: dxvk.conf
info:  Effective configuration:
info:    dxgi.nvapiHack = False
info:  Built-in extension providers:
info:    Win32 WSI
info:    OpenVR
warn:  OpenVR: Failed to locate module
info:  Enabled instance extensions:
info:    VK_KHR_get_surface_capabilities2
info:    VK_KHR_surface
info:    VK_KHR_win32_surface
info:  GeForce RTX 2070:
info:    Driver: 450.51.0
info:    Vulkan: 1.2.133
info:    Memory Heap[0]: 
info:      Size: 8192 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 24012 MiB
info:      Flags: 0x0
info:      Memory Type[0]: Property Flags = 0x0
info:      Memory Type[1]: Property Flags = 0x0
info:      Memory Type[2]: Property Flags = 0x0
info:      Memory Type[3]: Property Flags = 0x0
info:      Memory Type[4]: Property Flags = 0x0
info:      Memory Type[5]: Property Flags = 0x0
info:      Memory Type[6]: Property Flags = 0x0
info:      Memory Type[8]: Property Flags = 0x6
info:      Memory Type[9]: Property Flags = 0xe
info:    Memory Heap[2]: 
info:      Size: 246 MiB
info:      Flags: 0x1
info:      Memory Type[10]: Property Flags = 0x7

doitsujin commented 4 years ago

It's working fine here, and the log file you attached also indicates that it's working fine for you. The console output might come from a different executable (launcher?).

FWIW if this really didn't work for eso64.exe, you would see the log message below all the device information.

Techwolf commented 4 years ago

There was no launcher. I was directly executing the program.

doitsujin commented 4 years ago

It's still coming from a different executable, not from the game itself.

doitsujin / dxvk