Jump to content
🛡️FORUMS ARE IN READ-ONLY MODE Read more... ×

MavericK96

Member
  • Content Count

    1880
  • Joined

  • Last visited

  • Medals

Everything posted by MavericK96

  1. MavericK96

    New ARMA2 OA Beta Patch 72291 Available!

    EDIT: Apparently this got moved over from the other thread and thus makes no sense now. :cool:
  2. MavericK96

    Incremental Aiming back?!

    Unfortunate because I hate the way that mouse smoothing works in this game, but oh well.
  3. AFAIK, you can't fly around in Far Cry 2. I don't think the wall thing would work for ArmA2.
  4. Well, that's a good theory, but I don't think that's the case, seeing as I've played games (Cryostasis, Crysis, etc.) that are MUCH more graphically-intensive than ArmA2 (and in fact Crysis uses SSAO), for several hours straight, with no issues. I've never gone over ~95C on either of my cards. I honestly just think the ArmA2 implementation of SSAO (or whatever it is in higher post processing settings) is not playing nicely with the nVidia drivers. ArmA2 1.07 never had a problem with the same driver revisions, and the only difference with post processing in OA is (AFAIK) SSAO.
  5. MavericK96

    arma2 betas?

    Yeah, at this point there's not much reason to not just use Combined Operations (OA with ArmA2 assets)
  6. Maybe each 40mm "slot" could contain like, 3 grenades? But then some sort of "magazine" system might have to be implemented, which doesn't make sense.
  7. Because it's a beta, I think you need to use Addon Sync or Six Updater.
  8. MavericK96

    Getting Serious with Game Controls

    You don't use strafe? Whaa...? :confused:
  9. Yes, that was one of the first things I tried. Didn't help. Like I said in my post before, at this point I think this is directly related to SSAO implementation in OA.
  10. MavericK96

    Update FaceTrackNoIR

    I think you quoted the wrong post, but, you're welcome. :cool:
  11. MavericK96

    Update FaceTrackNoIR

    Try adjusting your camera's Exposure setting. That helped for me.
  12. That's correct, though if HT is off the cpuCount=4 may not affect anything, but it's worth a shot. Also, if you are using the beta (which you earlier said you weren't, but you might give it a try), it automatically sets those parameters for you with a quad-core. ArmA2 1.07 already implements this as well.
  13. Nope, no difference at stock speeds and AFAIK no difference minus SLI, though there's no way I would play the game without it since it boosts performance considerably. I think I've narrowed the problem down to SSAO in OA. If I set Post Processing to anything Normal or above, I get driver crashes. However, with Low, I was able to play through several missions with no issue.
  14. MavericK96

    Recoil (again)

    It doesn't need to be turned off or reverted back, just tweaked some more for certain weapons (whatever you are given in Laser Show (MK16? 17? not sure) comes to mind as being way too jumpy)
  15. Likely because cpuCount=7 is not what you want to use, you want cpuCount=4. And exThreads=8 is invalid, you probably want exThreads=7. Regarding this, it's likely that you are using SpeedStep or whatever Intel calls it, that throttles back your CPU when you're not utilizing it fully. Try running a program like prime95 on all cores and then see what CPU-Z says. You can also disable SpeedStep in the BIOS, but it's nice to use for power consumption and heat purposes.
  16. Small bump regarding driver issues: I've tried all of these versions so far with OA: -197.45 WHQL -257.21 WHQL -258.69 Beta -258.96 (Beta and WHQL) And all of them give me driver crashes. Did not occur with ArmA2 prior to OA, and does not occur in any other game. It is also reproducible in that I will *always* get a driver crash in OA, though the amount of time it takes varies.
  17. MavericK96

    How to fix Performance

    That seems a little odd. I get crippling performance loss if I put 3D res above 125%.
  18. MavericK96

    Terrain Detail/Visibility Distance

    That issue was present in the 258.69 driver, but was fixed in the 258.96 one.
  19. Sort of off-topic, but what is that little radar thing with the names at the bottom of your screenshot? Is that some mod?
  20. +1. This seems to be the main offender in performance issues regarding PP.
  21. MavericK96

    Latest Beta Patch: 72197

    Yes, I did that whole procedure after they didn't work the first time. No luck. Next step is to roll back to 197.45, I guess, though there is no SLI profile for OA in those. :( On the one hand, I've read on the nVidia forums that a lot of people are getting driver crashes with the 2xx.xx series of drivers. However, on the other hand, I've only ever gotten a driver crash from ArmA2/OA, and have played continuous hours in other graphic-intensive games with no issue whatsoever. So I'm honestly not sure what is causing the issue. OA will cause a driver crash within probably 15 minutes or so.
  22. Yeah, having to "(re)load" the launcher in ACE is sort of weird.
  23. Interesting. You're one of the few, then. (regarding HT being on and no stutter) That's cool about the GTX 480. I've thought about getting one but I can't really justify the cost right now. What card were you using before?
  24. MavericK96

    Terrain Detail/Visibility Distance

    AFAIK you can't change that. It's just a hard-coded parameter.
  25. I think it's, as suggested, related to server desync/lag. I've noticed the same issue since OFP, I think it's just the way the netcode works. It's never been bad enough that I really cared too much, TBH.
×