Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Usually
I would assume it's my CPU but the average usage is 50%, it's hardly using the hardware I have.
I have an RX 480 and not even a Freesync monitor so that can't be it.
%50 doesnt mean anything, draw call performance is determined by the performance of a single core, one can be taxed at %98 and the rest are barely taxed, it will still bottleneck due to the nature of the crappy API
I personally have an RX480 + FX8350 @4.2GHz and it ran terribly until i turned off v-sync in the .ini and capped fps to maintain 60fps (because bugs at higgher fps)
I'm using AMD overdrive to view my core usage and it's 50% on all cores.
MSI Afterburner is reporting more frames, it clearly reduced draw cells if my CPU is the bottleneck.
Well, in any case, I'm playing in 1440p I guess.
As CPU load goes up, the GPU can no longer be supplied with a steady stream of commands to render the next frame. CPU load goes up when you ask the game to render miles and miles of terrain, simultaneously GPU usage goes down because the CPU's busy with non-render stuff.
Except CPU load actually isn't going up. It stays the same.