vk: GTX970 workaround #13577
Merged
vk: GTX970 workaround #13577
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Megamouse
added
Render: Vulkan
Driver: NVIDIA
|
I might just commit this. After looking through our issue tracker, there is a disproportionate amount of bugs filed by GTX970 owners. |
As I said in the related R&C ToD issue, yet another example of NVidia's shitty decisions screwing customers over |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Soft limit of 3G will allow vma to still go above but kick in aggressive memory reclamation routines that should hopefully keep us from going above the 3.5G limit. If this fails, we can go with a different approach where we set the heap limit directly in the allocator, but I'd like to avoid that until the next vma integration exercise.