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
Texture flickering issue reappeared after 'the big update' #37
Comments
This seems surprising for it to be happening on a 4GB GPU since we should be using < 2GB. Can you run with -con_logfile when this happens and upload game/dota/console.log? Also, can you have nvidia-smi running and see how much GPU memory is consumed overall on the system? I'm thinking it may be something else on your machine using up GPU memory causing us to start evicting textures to try to make up for it. |
@danginsburg I tried to reproduce this in a quick bot game but wasn't able to. I did notice that even before starting the game, I was using over 2G of the available 4G GPU memory:
During my test game, Underlords never rose to above 1325M or so (maxed out all graphics settings):
So it seems reasonable that if the 2G limit was approached, or if I had say other chrome tabs or something using up some more space, that I would hit the 4G mark. I'll keep an eye on things, and if it happens again I'll report back. We can otherwise close this issue for now. Thanks for the pointer on nvidia-smi, that looks like a useful tool! |
Your system information
Steam
->Help
->System Information
) in a gist: https://gist.github.com/stellarhopper/341bd08f8389a2b24ff773b62ce7be01Please describe your issue in as much detail as possible:
This is similar to #27, the symptoms are exactly the same as the youtube clip linked there.
This would happen infrequently before the Big Update, but has been much more consistent since then.
Dropping the video settings way down seems to temporarily fix it, but slowly turning things on didn't find an immediate culprit.
The video card is an Nvidia GTX 980.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: