Windows driver version 376.80 and Linux driver version 375.27.08 provide new features for Vulkan developers to test their upcoming Vulkan applications. Release Updates February 1st, 2017 - Linux 375.27.08, Windows 376.80 Bug fixes Download links:Windows 7/8 x64 Windows 10 x64 376.80 is VK375_17-25, 1/2/2017 378.57 is r378_48-4, 30/1/2017 378.49 is r378_48-2, 20/1/2017 376.71 is VK375_17-24, 20/1/2017 376.66 is VK375_17-21, 10/1/2017 376.62 is r375_00-229, 10/1/2017
GeForce 1000 Series: GeForce GTX 1080, GeForce GTX 1070, GeForce GTX 1060, GeForce GTX 1050 >>> and what about TITAN X PASCAL ?? not supported ??
GeForce 376.80 vs GeForce 378.49 Doom Vulkan 1080p Great Driver... https://scontent-cdg2-1.xx.fbcdn.ne...=bbfd47418905c83e8ec545ad4d96b4e0&oe=5906D93F
Those results you showed are based on entirely different runs. What are we comparing? 2.5 seconds snip and 60 seconds?
Well, with your CPU there's no much profit to get with low driver overhead. Thaks for the graph, it's seems that 1.0.38 API gets a big improvement. EDIT: Just tried the driver, and I get aproximately -20 fps compared to OpenGL. uke2:
Interesting, I did not realize this detail, I retake the test, in the beginning should be both 60s, some mistake of the OCAT. Thanks for warning PS: Revised test https://scontent-cdg2-1.xx.fbcdn.ne...=84963758e29ad1ee7ce61be2e732ac79&oe=5949D793
Credits to Alexandre Ziebert, NVIDIA BRASIL. Just drag the TXT RecordingResults file onto the executable and convert it to the FRAPSBenchViews. Download:https://drive.google.com/file/d/0ByeudBtCZO7cTkE4THNQQ1Mza0E/view?usp=sharing
getting the error when i lunch doom with vulkan.. Callstack Function(desc) Line Bytes File Process Address --------------------------- ---- ----- ---- ------- ------- vkWaitForFences() ... + 0x1ac0b65f vulkan-1.dll GetGameSystemInterface() ... + 0x5a8089b1 DOOMx64vk.exe GetGameSystemInterface() ... + 0x5a814c14 DOOMx64vk.exe GetGameSystemInterface() ... + 0x5a80fad1 DOOMx64vk.exe GetGameSystemInterface() ... + 0x5b0fcd3f DOOMx64vk.exe ** UNKNOWN **(** FUNC_PARAM_ERROR **) ... + 0x59bd7d81 DOOMx64vk.exe GetGameSystemInterface() ... + 0x5b38882b DOOMx64vk.exe BaseThreadInitThunk() ... + 0x3ad08364 KERNEL32.DLL RtlUserThreadStart() ... + 0x3d7a70d1 ntdll.dll Register Info --------------------------- EDI: 0x000000000676FFE0 ESI: 0x0000000000000000 EAX: 0x00000000062BB9E0 EBX: 0x0000000006763C50 ECX: 0x00000000066B1800 EDX: 0x0000000000000002 EIP: 0x00007FFF1AC0B65F EBP: 0x00000000041E63F0 SegCs: 0x0000000000000033 EFlags: 0x0000000000010202 ESP: 0x00000000041E62C0 SegSs: 0x000000000000002B Exception Info --------------------------- ExpCode: 0xC0000005 (Access Violation) ExpFlags: 0 ExpAddress: 0x00007FFF1AC0B65F Build & Runtime Info --------------------------- User: sajib Version: 20160808-123534-peach-almond File Path: D:\Doom\DOOMx64vk.exe System Time: 2/3/2017 16:31:30 Build String: 20160808-123534-peach-almond VT File Path: VMTR Override: generated/pagefiles Launch Command: "D:\Doom\DOOMx64vk.exe" Memory Info --------------------------- In Use: 28% MB Physical RAM: 8131 MB Physical Free: 5845 MB Paging File: 16227 MB Paging Free: 12986 MB User Address: 134217728 MB User Free: 134216878 CPU Info --------------------------- Num Packages: 1 Num Cores: 4 Num Logical: 8 CPU ID: Generic CPU MHz: 3500
i have better performance on opengl too... but 5/10fps you have 20 fps of the difference with .38? and before?
There we go...That makes more sense. There is a slight improvement in frame time and FPS. Probably imperceptible on screen.
I think this is a much better way to evaluate the performance of GPUs in Vulkan (youtube.com/watch?v=uChRzAPqF2c)