Jump to content

S20

Member
  • Content Count

    13
  • Joined

  • Last visited

  • Medals

  • Medals

Community Reputation

10 Good

About S20

  • Rank
    Private First Class
  1. The R7 260x or R7 265 should run Arma fine. Your cpu is perhaps slightly older but still better than any AMD chip for this game. Intel CPU is the way to go, either way. Also I second the SSD recommendation. Worth the money.
  2. Well, let me rephrase then. 300ft is a rough guess of how far you can basically jog (the animation and speed are hardly a sprint), before debilatated by fatigue. I've never served in the military, but I've backpacked extensively, including some very fast travel above treeline. Yes, your heart-rate is up for a sustained period, but you don't slow to a crawl and have to take a dirt-nap to recover. That's absurd.
  3. Agreed with the above; the weapon sway mechanic is entirely unrealistic, and unwelcome in any form IMO. Nearly everyone I play with (and I play most nights) dislikes it, and the accompanying increase in sway that occurs when fatigued after running 300ft, or injured, can make some moments in-game infuriating.
  4. The servers are more of an issue than your hardware, I'd suspect. I have an i5 and get good frames in single player or lightly populated servers, but as servers fill up the game bogs down due to low server side fps. Hosts need to lower their max players to something like 40-50 players, IMO.
  5. S20

    Arma 3 crash to desktop

    Just my own anecdotal experience, but my crashing turned out to be due to different custommissions, not Arma. After the main culprit was patched by the dev, I have ceased to have crashing issues. My point I guess is that if you are crashing in KotH or something else like that, it might not be BI Studios' fault.
  6. S20

    Arma 3 crash to desktop

    Removed TBBmalloc, skill crashing with "Arma stopped working blah blah"
  7. S20

    Arma 3 crash to desktop

    Will try this myself... here is my most recent .rpt and I'm using the tbb4malloc as well... Any thoughts on this? ---------- Post added at 19:15 ---------- Previous post was at 19:12 ---------- Also, just noticed my code for -cpuCount was misspelled, so I fixed that already...
  8. Not sure if this has already been mentioned or addressed, but it seems that while ArmA server specs have always been too low, or player slots too optimistic, things are even worse since the last patch. No matter what server I'm on, once the player number exceeds ~24-30 players, server FPS drops into the single digits, rubber banding and yellow/red chains occur almost steadily, and I'm not sure if it's related, but I have to reboot early and often if I want to connect to a multiplayer server (namely, King of the Hill) without ArmA 3 crashing to desktop. Please, BiStudios, I love this game but it's not playable really in its current form. Please fix deal with these issues before adding more content such as a launcher and all that other stuff on your roadmap. In fact I'd write your roadmap like so: 1) optimize game. 2) optimize game.
  9. It magically works again for me. Drivers all current.
  10. Same issue here today, tried Byremo's settings, no change. Reset modem/router, went into router and checked settings, I don't see how any of them would cause an issue. Mostly stock other than putting in my own DNS server settings, and tweaks to WiFi channels. Can play other multiplayer games just fine.
  11. Cool, thanks for clarifying. So all of the servers with the wrong version are somehow able to populate... annoying.
  12. Hey, so I went to update and connect to some DayZ servers using another service which works in tandem with Steam, and found that neither Steam nor this service would allow me to use the most common server side version which is 125402; steam pushes 125548 to my client. Is there a way to manually downgrade to the former?
×