-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vulkan capture seems broken in v1.2.0 #40
Comments
What OS version are you on? |
Windows 10 64-bit - Microsoft Windows [Version 10.0.15063] GTX 970, driver version is 384.94 |
Probably my fault, I probably broke something while adding Win7 support. I don't currently have any machines running the Creator's Update (they're all either opted into insider previews or running internal builds), and this particular present path has been deprecated, so I'm actually not easily able to debug/fix it... Are you able to capture an ETL file captured by GPUView's log.cmd and send it to me? I could debug it that way. |
I can confirm that the latest build is not working if game mode is activated. I have game mode disabled, and all other capturing settings too, and PresentMon works as usual. I'll see if I can get some logs for you @jenatali, probably over the weekend. |
@cooky451 I think the "new ctrl+c behavior" is actually a bug that should be fixed in v1.2.1. |
I'm not sure why, could be FCU, could be new Nvidia drivers, could be the update - but it works now. |
Good enough for me! :) |
I'm testing the Vulkan capture with the cube.exe from the LunarG Vulkan SDK, but PresentMon v1.2.0 doesn't seem to get any presents from it - v1.1.2 works fine. (Also the new ctrl+c behavior is a bit annoying, since you don't get back into the command line?)
Sample output from v1.1.2 in case that helps:
cube.exe,6312,0x0000000000000000,Other,-1,0,0,Composed: Copy with CPU GDI,0,3.329873,8.362,8.332,0.000,0.008,16.488
The text was updated successfully, but these errors were encountered: