Skip to content
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.

Sign up for GitHub

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

Jump to bottom

best practices validation warnings #271

Open
jjYBdx4IL opened this issue Feb 26, 2022 · 3 comments
Open

best practices validation warnings #271

jjYBdx4IL opened this issue Feb 26, 2022 · 3 comments

Comments

@jjYBdx4IL
Copy link

There are some best practices validation warnings. Maybe we can fix them together? Here are two that I simply can't fix because I don't know what's causing them:

  • Validation Warning: [ UNASSIGNED-BestPractices-pipeline-stage-flags ] Object 0: handle = 0x1ddf07b8550, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x48a09f6c | You are using VK_PIPELINE_STAGE_ALL_COMMANDS_BIT when vkCmdPipelineBarrier is called
  • Validation Performance Warning: [ UNASSIGNED-BestPractices-vkCreateCommandPool-command-buffer-reset ] Object 0: handle = 0x2a6c31da9d0, type = VK_OBJECT_TYPE_DEVICE; | MessageID = 0x8728e724 | vkCreateCommandPool(): VK_COMMAND_POOL_CREATE_RESET_COMMAND_BUFFER_BIT is set. Consider resetting entire pool instead.
@jjYBdx4IL
Copy link
Author

pull request #270

@jjYBdx4IL
Copy link
Author

booted up my PC, warnings are gone now. for no apparent reason. Adding the bp layer would be useful nonetheless, I guess.

@jjYBdx4IL
Copy link
Author

turns out it was MSI Afterburner OSD. That and other apps like OBS seem to cause issues like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jjYBdx4IL