Jump to content

Rexxenexx

Member
  • Content Count

    549
  • Joined

  • Last visited

  • Medals

Posts posted by Rexxenexx


  1. I just did some tests in SinglePlayer>Editor and it is different than MP (smooth). I usually play MP warfare and that has a setting default of 2000 VD and the test I just did was at 3300 something VD. Maybe a player in that area is causing it to pause that much longer? For sure it seems to be a MP thing. I remember setting VD to 800 in warefare because I was fighting a guy in Elektro. and every time I look towards the center of town it paused a bit. 800 didn't do a thing.

    I'll try to put some AI around Elektro. to see if I can recreate the MP situation.

    Update: Nah AI doesn't do a thing. It has to be something to do with MP and a player somewhere in the direction of where you are looking. I can't recreate it in SP Editor.


  2. Still happening on build 59025. I think its just the mass amounts of different textures at the docks (south-center) of Elektro. Seems if you are walking on the docks and look to the pipes it will pause to swap blits which takes long enough to notice badly. I'll try a lower texture setting to see if it could pre-load more textures, but it didn't seem to be this long of a pause before.


  3. I've used both in ArmA1 for a long time. Heres a YouTube of both same time.

    ---------- Post added at 12:13 AM ---------- Previous post was at 12:08 AM ----------

    overlay does not work so good in windows 7

    Try this instead of overlay.

    http://www.playclaw.com/en/index.php

    I tried it a couple hours ago and ArmA2 quit out after a couple minutes in MP. Didn't say anything, just disappeared. Usually it would say "ArmA2.exe Stopped..." or something but just nothing but *poof* gone so I uninstalled it. Played for hours after that. I hope TS3 has an overlay. I might just fork over the cash for the Logitech keyboard with the screen deal. My keyboard is missing A,S, D, and W is almost gone. :D


  4. I teetered on the edge so many times. I totally understand putting it aside IrishDeviant. I'll be getting OFP2 aswell.

    Do one last thing before you toss it out the window. Grab an extra HD and put XP 32bit. Install all your drivers off the web. The newest Nvidia is very important!Old driver New driver. Install Arma2+patch 1.03. put -nosplash -maxmem=2047 in the exe, then try. If it's still Death!! then format c: and fire it off the roof! ;)

    I have a Evga GTX285 and it's still chugs sometimes. -maxmem=2047 switch made it so when I alt-tab it's instant, no "receiving" waiting, that was somewhat nifty. Still their is a bit too much for me to tolerate, like the z-fighting. Something I haven't seen not fixable in a long time. Hopefully it gets better optimized in the future.


  5. You'll have a lot of latency between devices in your comp setup with the multi-cores, the X2 vidcard, and raid. One hickup and boom-goes-the-dynamite. Which is probably what's happening. I haven't checked what was updated in 1.03 that would make it more sensitive but you might want to look into that.

    Keep the -maxmem=2047 in all your tests. Make sure you have a bunch of space on your harddrives. Defrag your harddrives. Run in diagnostic...hmm that might not let the raid driver go through... Try to run in diagnostic mode, that usually stops background stuff from pausing the game for a millisecond once in a while.

    You can also Check your memory using Control Panel\Administrative Tools\Memory Diagnostics Tool or monitor when playing using Control Panel\Administrative Tools\Reliability and Performance Monitor. See if anything is filling up and up and up until crash. Also that XP install wouldn't hurt either! ;) Do it on a spare harddrive if you can so you don't have to rape what you have now.

    Good luck with it. If all this fails then compare whatever is different you your buddies systems.


  6. I'd turn Aero back on, since that didn't do anything, and wait for the next driver. From what you are saying you've narrowed it down to something new in 1.03.

    You can try one more thing. first make a copy of arma2 -so you can go back to 1.02- and install the 1.03 patch. Run msconfig and do a diagnostic startup. Then try. Other than that I only can think the driver needs to be updated by ATI.

    Also put the "-maxmem=2047" switch in the exe. For me that made alt-tabbing instant so it should ease memory a bit. You have the ram for it.


  7. If they were using a 16bit z-buffer the z-fighting would be far worse than it is.

    What is Arma2 using? 24bit?

    Also, for refrence sake; this is screen tearing.

    I couldn't see tearing in that vid. I guess because it's too low res. But tearing is distinct separation of total image from what I remember,not what I originally/incorrectly called it. My graphics glitch lingo is a bit rusty but I got it.


  8. This might be off topic, but I'll have a go.. I love sniping and SMAW. It's all I do.

    but the trouble is, sometimes (most of the time, really) destroyed vehicles will show up as if they were fully operational, only stationary. Anyone else get this? It' really my mine concern right now.

    I have similar but that's just the laggyness of the engine to. It should take a while before it loads the destroyed object. If it's REALLY REALLY far away then maybe BIS never made a LOD destroyed mesh so it uses the low res fully oper. mesh.

    These problems seem like ArmA1 problems. I haven't had the z-fighting on things so close in ArmA1. Stuff far away is really noticeable but look how close I am in the video. That's not really M107 range. And at that short distance it looks like gremlins are crawling all over objects. Very distracting.

    BTW I just remembered the last time I had "tearing" in a game. It was with a 3Dfx Voodoo card, early '90s I think, which needed VSync to be forced on games like Tribes. That really slowed games down. :D

×