Jump to content

OUT FOX EM

Member
  • Content Count

    53
  • Joined

  • Last visited

  • Medals

Community Reputation

10 Good

About OUT FOX EM

  • Rank
    Lance Corporal
  1. OUT FOX EM

    Trapped Unit - Help

    I have to be honest, when I saw "trapped unit - help" I wasn't sure what I was about to see...
  2. Yeah that's about right. If I use RivaTuner (or EVGA Precision) to set the clocks to factory settings, in other words override factory settings with ANY setting -- higher or lower than stock -- then I get the problem. If I never use RivaTuner at all then I don't have the problem. As for other games, this is a clean install. I haven't really installed much on there other than ArmA II and BF2 (for ProjectReality). PR runs fine either with the overclock or without it. The system uses a Corsair 750w PSU (this one). Next thing I'll try is overclocking before playing BF2, then reducing back to stock clocks via RivaTuner and see if it makes any difference in there.
  3. I'm trying to squeeze the last drop of performance out of my brother's computer that I can, so I overclocked his CPU and his GPU. I ran all stress/torture tests to make sure the system is stable and that the temperatures are good, so I know that is not a problem. What IS a problem though is when I overclock his GPU, ArmA II's framerate takes a HUGE hit (up to 50%). Here's the PC specs: Intel Q9550 (3.8 GHz) 4 GB Corsair Dominator DDR2 (1066 MHz) Nvidia GTX 260 216 (740/1586/1650 MHz) Asus P5E Windows 7 x64 ArmA II Settings: Version: 1.05 Visibility: 1600 Quality preference: High Interface resolution: 1920x1080x32 3D resolution: 1920x1080 Texture detail: Normal Video memory: Default Anisotropic filtering: Normal Antialiasing: Normal Terrain detail: Normal Objects detail: Normal Shadow detail: Normal Postprocess effects: Low The odd thing is that when I use RivaTuner to overclock his GPU from 655/1404/1125 to 740/1586/1650, the framerate will go from 60-80 in the menu and 30-45 in the game, to 18-22 in the menu and 15-25 in the game. That's a 50% performance hit. I know the simple answer is "well then don't overclock it" but that doesn't help me understand why overclocking is killing performance, when it should in fact be just the opposite. Even odder still is if I use RivaTuner to set the clocks back to the stock factory clocks, my performance suffers just the same. Obviously this is not related to the clocks of the card, but the act of changing the clocks itself. For the record, I tried EVGA Precision and the same thing occurs. I've monitored the clocks and the temps while in-game and they're normal. The GPU is at 54C under full load in FurMark, and doesn't pass 51 in ArmA II. If anyone has any experiences like this, or better yet an explanation, why RivaTuner/EVGA Precision would kill performance even at stock clocks I'd love to hear it. Once I solve that problem I should see results from the higher clocks.
  4. OUT FOX EM

    Quad SLI (Two Questions)

    Where? I read both pages and that quote is the only post mentioning X13000. I also tracked down the original article in that thread, which is found here (in English): http://www.semiaccurate.com/2009/08/13/gt300-have-nvio-chip/ There's no mention of any scores at all on any of those sites, other than the quote in my last post. I think you shouldn't get your hopes up until some real scores do emerge. On the other hand, I definitely agree that a paper launch is pretty weak but they're in no need to rush, seeing as Nvidia currently has no DX11 competition yet.
  5. OUT FOX EM

    Quad SLI (Two Questions)

    I certainly hope that's true. However, I followed the chain of links, and even tried deciphering the Chinese translation, but I found nothing indicating those scores unfortunately. This was the closest I came: "G300 is slightly a bit of it, but also your head refers to the Vantage X13000" That's certainly nothing concrete. At this point I'll have to throw that into the rumor bin and wait until some real benchmarks comes out. I definitely do hope they're that good though...
  6. OUT FOX EM

    Note for i7 users

    Nice. Thanks for the post, though I haven't yet added the patch. Everything works fine right now and I didn't want to roll the dice. At least they fixed that though.
  7. I don't understand why the developers don't make it look like this, obviously it can be done. Good job man!
  8. OUT FOX EM

    ArmA2; Windows 7 64x bit. Failure.

    Honestly, if you're not familiar with the registry then you should not venture in there. It's an extremely dangerous place for someone who does not know what they're doing to be in. He told you where you could find the registry key and you didn't even realize it, so I know your experience in the registry is somewhere between zero and none. I strongly advise against doing anything in the registry at all, and just reinstalling ArmA II. I'm not trying to be a jerk here, I'm trying to help, seriously.
  9. That's what I'm saying. I'm glad I made this thread and was told to disable HT, because I definitely never suspected that as the culprit of the stuttering. The odd part too is it only happened in Windows 7 for me. :confused: In Vista HT didn't cause ANY stuttering at all. I can only hope that future patches and driver updates will resolve this problem, but I'm sure the developers are hard at work on their new expansion pack instead... :icon_rolleyes:
  10. Just for shits and giggles, see how long you can play in windowed mode and get back to me... (-window -x=800 -y=600)
  11. OUT FOX EM

    Fraps kills FPS with any setting

    Speaking of the obvious... You have an 8800 GTX! Found your problem. :icon_rolleyes:
  12. Well I don't know if you read the thread (or even just the first post) but those drivers didn't work for me. As others have said, all hardware/software combinations respond differently from one another, so what works for you won't always work for me (or anyone else).
  13. Back once again, and I did what I did before -- installed 186.18 and renamed to Crysis64.exe. I decided this time not to install the EVGA SLI enhancement, as I can live with the file being named after Crysis... and that's what fixed it for me. Thanks for everybody's help. Hopefully my experience and everybody's advice in this thread will help someone else down the line. I'm off to play Crysis... oops I mean ArmA.
  14. So here we are, nearing the end of 2009, and we still gotta trick the goddamn thing into thinking it's 2001. I actually had momentary success with the 186.18 drivers along with renaming ArmA2.exe to Crysis64.exe, believe it or not. That got me up to Vista framerates for one play session, but now I'm back down to where I was after I kept on tinkering. :banghead: I'm off to reinstall my drivers... again.
  15. For the OP, there's a good tool (it's free) called EVGA Precision, that you can have display your GPU temps in-game, much like FRAPS displays your FPS. You can also use it to display your FPS if you want too. NOTE: Many games that run PunkBuster will kick for running EVGA Precision. So if you use it on other games and get kicked, then you know why.
×