xWiredx, on 30 December 2014 - 07:36 AM, said:
OC your CPU. I have a 5820K and a GTX 980. I do not have performance issues like this.
Really. This goes for pretty much everybody. Haswell+OC+decent GPU=happy fun time. Ivy Bridge and Sandy Bridge users will need bigger OCs. This information is abundantly available in the hardware subforum.
This game -does- need dev optimization attention badly, but many people complaining of performance issues -can- get better performance than they currently have. Trust me, I've been drumming on this for half a year at least.
It's unwise to take your single use case and make global statements like "everyone just needs to increase their CPU overclock and that'll fix everything."
I have four systems:
- Core i7 930 @ 4.05 GHz, 12 GB DDR3 RAM, 2x Radeon 6970s, Catalyst 14.11.2 BETA
- Core i5 2600K @ 4.5 GHz, 8 GB DDR3 RAM, 3x Radeon 7970s, Catalyst 14.11.2 BETA
- Core i7 3770K @ 4.6 GHz, 16 GB DDR3 RAM, 4x Radeon 290Xs, 14.12 WHQL (Omega)
- Core i7 5830K @ 4.2 GHz, 16 GB DDR4 RAM, 2x Radeon 290Xs, 14.12 WHQL (Omega)
Since the latest patch was released, I've spent something like 20 hours trying all four combinations of DX9/DX11 and 32-bit/64-bit, with and without Crossfire enabled, 8 different Crossfire profile overrides (Bioshock.exe, Crysis3.exe, etc), and toggling all MWO settings between their lowest and highest settings. In all situations, total CPU utilization has never peaked above 25%, and I've never been able to maintain a constant 62 fps (limited by MSI Afterburner)--which was child's play before the latest patch.
If I were to graph out GPU utilization for you, it would look spastic: bouncing randomly (e.g. 13%... 45%... 3%... 89%) every 500 milliseconds (per my monitoring interval in MSI Afterburner). But the
really interesting thing is that appears to be no correlation between GPU utilization, framerate, and scene content. Looking at a wall, GPU utilization is all over the place. While performance in MWO has always been exceedingly poor, this latest patch clearly brought things to a new low.
To date, here's what we know:
- This problem was introduced in the latest patch
- It occurs in both the 32-bit and 64-bit executables
- It occurs in both the DX9 and DX11 rendering pipelines
- It doesn't care whether you have an Intel or AMD CPU
- It doesn't care whether you have a nVidia or AMD GPU
- It doesn't care what driver revision you have installed
- It affects both single and multiple GPU systems
- It happens in both Windows 7 and Windows 8
Logical conclusion: MWO is at fault--not our systems.
Logical solution: replace the entire technical team with qualified personnel. If they can't manage to keep MWO running at a solid 60 fps with a single GTX 660 Ti or Radeon 7950, they need to be let go. Not only does this game look FAR worse than the original Crysis, released back in 2007, it runs FAR worse. We're almost in 2015--it's time.
It's been long established that a single,
qualified, CryEngine 3 mapmaker can run circles around PGI's entire team in terms of content creation speed, graphical fidelity, and map design. When we asked if we could help, Paul/Russ shot us down because of "quality control, legal issues, and performance"--complete and utter BS.
Edited by FuzzyLog1c, 30 December 2014 - 08:54 AM.