Page MenuHomeFeedback Tracker

Horrible performance, minimal resource usage
Closed, ResolvedPublic


Arma 3 will not utilize my available resources. No combination of video settings will cause more than 50% GPU usage, and not even enough to cause it to clock up. Frame rate is consistently poor, 20 FPS and under. This system can run any game on highest settings, specs are as follows, drivers and BIOS updates are current:

Windows 7 64 Bit Professional
MSI Z77 Mpower
Intel i7-2600K @ 4.2 GHz
16 GB 1600 MHz DDR3
500 GB 7200 RPM HDD
MSI GTX 680 4GB OC @ 1.2 GHz boost clock (game runs at 849 MHz, same as idle desktop)


Legacy ID
Steps To Reproduce

Playing the game with any visual settings.

Event Timeline

nmhays edited Steps To Reproduce. (Show Details)Mar 5 2013, 11:35 PM
nmhays edited Additional Information. (Show Details)
nmhays set Category to Performance.
nmhays set Reproducibility to Always.
nmhays set Severity to Major.
nmhays set Resolution to Duplicate.
nmhays set Legacy ID to 2082727605.May 7 2016, 10:39 AM
SGTIce added a subscriber: SGTIce.May 7 2016, 10:39 AM

Try opening task manager & check that all cores (Affinity) are checked for ArmA 3.

nmhays added a subscriber: nmhays.May 7 2016, 10:39 AM

They are. I should also add that this issue happens at all resolutions, though the framerate is slightly (1-5 fps at lower res) higher, from 640x480 to 2560x1440. Raising the draw distance to maximum increased resource usage slightly and caused a slight increase in performance.

Since it's not using enough resources to get it to up the clock change your graphics card settings to always stay at maximum clock and see if the game runs smoother, I know it won't help with usage but it will probably help with performance.

I am also using less than 50% on core 1, and way less than that on all others. No usage on HT.

SGTIce added a comment.Mar 6 2013, 3:41 AM

Last I checked a few months ago BIS had no plans to support HT.

Do you have a lot of GPU memory, put that on high & can't remember if this is right or not but I believe around Gamescom they said the CPU would be used more than the GPU.

After a few more days of playing with settings, I have managed to increase the framerate slightly. However, the game appears to have a video memory leak, as the used amount of VRAM will slowly rise from ~2GB at 2560x1440 to 3.5+ GB in an hour or so, rendering the game largely unplayable with less than 15 fps.

Upvoted as my experience is very similar. GPU is generally using less that 40% and cpu is generally less than 40-50%. The 1st core of the CPU doing most of the workload. There appears to be a memory leak possibly?

Anyway you cut it the performance is appalling. Having a PC that could easily run this game at 60 FPS should run it at 60, not at 20 FPS while not even working with half the CPU's and GPU's capacity. It's almost shameful. This game could be great, IF there is some way to un-bottleneck performance.

Should easily run the game at 60? Just because you run games that are tiny little boxes dosen't mean they can run this at 60. ArmA is processing what's going on across the whole map & it's sending data back and forth across the clients/server.

Just because you're in a town on the W side of the map dosen't mean that it's not processing something that's going on the far E side.

It needs to be optimized, utilization needs to be improved, those are a given. But the games got a long way to go & so far it's a vast improvement in most places over the earlier iteriations.

pystub added a subscriber: pystub.May 7 2016, 10:39 AM

Duplicate of #0000716

Uh, considering I posted this a full day earlier, I fail to see how it's a "duplicate"?

And nowhere did I say I expect it to run at 60+ FPS, I said that I expect it to make reasonable usage of hardware well above even recommended specs, and to run at an acceptable framerate, and I fully expect BI to do something about it, that is the purpose of an Alpha. I don't think that's unreasonable, and I don't see the need to start this debate in a bug report.

This thread came before that one by a day psy. Read the time stamps.

This game is by no means a good stress test on the computer. Which being a new 2013 huge environment game, it should be putting out the heat.

You are aware... we're in Alpha. The devs are working to optimize the game, so keep your panties on.

Using the latest development build with the new shadows forces the GPU to stay in boost clock, yielding some performance increase. GPU/CPU load rarely exceeds 40% and never 50% however, and CPU usage seems to be down even further less than 45% of core one, and less than 15% of any other. FPS is up probably 10-15% though, right around 30FPS, enough to have fun with the game now.

This is bizzare, but trending better, I suppose. Keep up the good work BI!

white added a subscriber: white.May 7 2016, 10:39 AM

the reason for this is the game being mostly single core, they can optimize it to gain some performance but you would only see drastic performance improvements if they rewrote the core to properly support multicore cpus.

Which they should, someone who's tech saavy should write a ticket.

Sure that compare to other similar game, ARMAIII is very very slow and gets very incomfortable when you want to shoot somebody moving, mostly with a acog.
I'm running it on a DELL M6500 workstation:

       System Model: Precision M6500                 
               BIOS: Phoenix ROM BIOS PLUS Version 1.10 A07
          Processor: Intel(R) Core(TM) i7 CPU       Q 840  @ 1.87GHz (8 CPUs), ~1.9GHz
             Memory: 8192MB RAM
                 OS: Windows 7 Pro 64 bits
    DirectX Version: DirectX 11
          Card name: NVIDIA Quadro FX 2800M
       Manufacturer: NVIDIA
          Chip type: Quadro FX 2800M

This machine runs MWIII at 85-90 fps and only 20-25 fps for AIII !??!

There is a big big problem!


Alain make a new ticket & post your dxdiag there.

Duplicate of #0000716.

Excuse me? Once again, I reported this issue a full day before the other thread. If this is the way reported bugs will be handled by the team, then perhaps I should request a refund right now.

Very disappointed in the response to this issue.

It's not about who came first, it's about which report recieved more attention. The other report has ten times as many votes as this one, so it takes precedence. The general rule is "one report per issue", so all duplicates will be closed, no matter when they were created.

Then where do I seek my refund?

Not here on the bug tracker. Please refrain from re-opening this issue.

I am a paying customer, and I will reopen my one ticket as I see fit. This does not speak well for the management of this alpha. Never have I seen this issue in any public/private alpha addressed so poorly. You continue to close my ticket with no explanation, no information. No information was sought from me, there's no clear indication of what information should be provided with a ticket. Merely the direction to another largely ignored huge ticket, one which has not yet been acknowledged publicly, and daily my performance gets on average worse.

Not to mention that the "duplicate" thread involves AMD chipsets and AMD videocars. I have neither. Considering the different sources of drivers, and different hardware configurations, perhaps it would be prudent to thoroughly investigate the issue.

Incredibly unprofessional.

The other ticket is about low CPU/GPU utilization in general, not just on AMD hardware, as you could see if you had read the comments. It has also been assigned to a developer, meaning it has been "acknowledged publicly" and the devs are working on a solution.

I have seen nothing here to indicate that your issue is different from the one reported in the other ticket. They are the same issue, experienced by hundreds of people with varying hardware setups. Your issue is not unique and thus does not merit special attention or its own report.

There is absolutely no sense in keeping track of dozens or hundreds of individual reports on the same issue, therefore all but one are closed. Since the other issue has recieved the highest amount of attention and has already been assigned, that is the one that will remain open. As a result yours has been closed.

I hope this explanation is sufficient.

DnA added a subscriber: DnA.May 7 2016, 10:39 AM
DnA added a comment.Mar 15 2013, 1:09 PM

MadDogX's explanation is fair and accurate. You are not being ignored, and as he said the issue is being dealt with more broadly. It does not help us to have the same or very similar issue open and acknowledged in many places. Any optimization is not going to be happening in the matter of days, and this being an Alpha product has been very clearly communicated. Thank you for understanding and I hope you'll be able to enjoy Arma 3 if you can't already now :-)