Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
As VRAM is only being accessed through a MMU, one can only get the size of the memory window being used without directly interacting with the driver.
It's all just about how to get the total amount of VRAM available, e.g. to make certain guesses on which graphics settings should be disabled by default in a game. Pretty much every driver has provided that piece of information before, but everyone did it in its own way. The only place where you'll pretty much always find those values are the kernel and/or X logs, but it's hard to parse them out of there in a unified way.
I'm convinced that this is what Valve's games still do; why else would performance be so abysmal? Besides failing to utilize all of the GPU's cores, which I've heard might be the case. I just really want to get to the bottom of this already. Is there a program I can get that monitors, in real time, resource usage to that extent? Bonus points if there's also one for Windows so I can compare.