Jump to content

rob151515

Member
  • Content Count

    27
  • Joined

  • Last visited

  • Medals

Community Reputation

10 Good

About rob151515

  • Rank
    Private First Class
  1. To be honest, I wanted to re-install the OS and Arma 2 onto the SSD but I'm too lazy and have a very tiny SSD! Like I said, initial impressions seem pretty good but I haven't had much of a chance to test it out yet.
  2. Everyone here has been so helpful I thought I should update in case it helps someone else. Was having same problems as op except I have 2 x 6970 in cfx. If I tried to use Default my FPS suddenly dropped 10 or more and it became quite stuttery. Yesterday I purchased a 60 gb Vetex 3 SSD, moved my arma 2 folder over to it and now it seems I can use Default without issues. Only fps issues i've noticed now are when there is a lot of vegetation to render but the gpus are going flat out so thats understandable. Still doing testing but so far its looking very promising.
  3. I do get better frame rates using both in crossfire as opposed to a single GPU - I just wish I could use the "Default" setting as I don't think the full amount of VRAM is being utilized. I get a frame rate drop when I look through the scope which usually lasts a few seconds before it rights itself and I can't put objects or terrain on anything greater than normal/high...
  4. I have 2x6970 and have the exact same behaviour using the "Default" memory setting so you are not alone.
  5. rob151515

    Insurgency

    Sorry if this is the wrong place for this. I'm playing the ACE version of this mission with the bon recruit ai script which I added based on a suggestion from a previous poster and am absolutely loving it!. Only problem is I can't seem to get medics to heal. If I call out that I'm injured or ask them to heal somebody, they will go over to the injured soldier and stand around for a bit before reporting back with "negative". Does anyone know if this is normal? Anyone else playing this with bon recruitment ai script also seeing this behaviour?
  6. Thanks for posting these. Was doing some testing last night and I definitely can't seem to get rid of the white pixels all over foliage when using any form of AA. Also done a bit of searching and there's already a bug posting about it here: https://dev-heaven.net/issues/15668 - doesn't look like it's going to be fixed in a hurry. :( There's a couple of people are reporting that if they use driver controlled Anisotropic Filtering instead of Application controlled it's gets rid of the issue, but it's not doing anything for me. From what I'm reading it seems to be isolated to Takistan which is pretty much the only map I have been playing on.
  7. To be fair, the white blinding flickering light only occurs when running in crossfire I think... Are you using AA in game? What are your video settings?
  8. I purchased my 6970 (I actually have 2 of them now, not that crossfire seems to work that well with Arma 2 anyway) and I wish I hadn't. Arma 2 is the only game that I really wanted to get running well and I haven't been able to - I have an i5 2500k oc'd to 4.3 Ghz Problems, ok where do I start... I can't use AA in game or I get white pixels spread throughout the trees and bushes. I get significant fps drop when looking through scopes and then I get flickering of buildings/textures when looking at them through a scope. Oh yeah and then if I do manage to achieve a reasonable frame rate the lighting starts blindly flickering white util the entire screen is white and I can't see! (not being able to see kinda makes it a bit unplayable) From what I have read people with ATI cards seem to have started getting problems when upgrading their drivers from 10.10 to anything later. Unfortunately there is no support for 6970 using 10.10's (I think support was added sometime around 10.12) IMO there is something not quite right with the memory setttings in Arma 2 and my 6970. From what I have read, there seem to be quite a few people out there with 6000 or 7000 series ATI cards that are having similar problems. Sorry for the rant but if it was me, I would return that card and buy something else.
  9. Can I ask which drivers you used to be using? I have a 6970 and would like to give them a go.
  10. I agree with the op, I also have a 6970 and there is definitely something odd going on with the default memory setting. If I switch to Very High memory my frame rate picks up significantly but I start getting lots of textures popping in all over the place. As soon as I set it to Default, my texture problems are gone but so is my frame rate. :(
  11. Did a bit more testing over the weekend, but have come up empty unfortunately. :( Yep Takistan - that's what I'm seeing. Went through the whole process - installed the drivers exactly to his specifications - no difference unfortunately. Haven't test with Chernaruss map - only tested with Takistan at this point (didn't want to introduce to many variables). I'm not sure how you are getting a min of 40 fps with those settings on Takistan, does that include walking into the middle of towns? When I run those settings, even when I do get 99% GPU load I'm definitely dropping well below 40 fps in towns with lots of buildings and trees around (and that's with a VD of 3000)... :confused: I am running with memory at 'Default' rather than 'High' though. I find that If I run with memory set to 'High' I get a lot of 'Blob' trees and low res textures not swapping to high res textures until I'm right in front of them.... As frustrating as this is, I still love this game. It is easily the best game (sorry simulation) I have ever played. :)
  12. I didn't think i5's had hyperthreading? If they do I don't think it's enabled on my system because task manager is only show 4 processors...
  13. I'll give them a go and report back. Thanks.
  14. Thanks unfortunately it wasn't AToC. Switching it off had no effect on the issue I'm seeing.
  15. I posted a new thread in this forum (http://forums.bistudio.com/showthread.php?t=130220), but I've just found this thread and this looks to be what I am seeing in SP. As Burdy puts it: Maybe it's not my hardware after all?
×