-
Notifications
You must be signed in to change notification settings 8000 - Fork 427
[vulkan] Debug report from ObjectType: 5 #81
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
Comments
I went to work on the project anyways, and i found calling Walnut::Image::SetData doesnt show the warning for that frame, checked by not calling it after a couple of frames, and when it is not called the errors return |
important note i feel i need to add, as the logging of this message is only a debug message, running in release doesnt show this message |
Same problem appeared after switching from 1050 Ti to 4090 |
Don't know if anyone is still having issues with this, but here is a quick fix for anyone dealing with issues regarding some [vulkan] Debug report from ObjectType: 5 related errors. There are multiple ways to handle this but if your just download an older sdk of Vulkan it should solve you problems. I personally just went back and used sdk version 1.3.126.0. If you prefer to use the most recent version of Vulkan this should fix your issue as well ocornut/imgui#7236. |
When launching a Walnut app, the console is spammed with these messages (these are the first four frames)
Each frame the handle swaps between two values,
0x967dd1000000000e
and0xdcc8fd0000000012
The line i found caused the error is this line
I also found this issue at the dear ImGui repo which seems related (same objectType, same handle)
This is a repost from an issue in WalnutAppTemplate, but as i stated there, the issue lies with Walnut, not with WalnutAppTemplate
The text was updated successfully, but these errors were encountered: