feda

No, you don't. Blizzard has your Diablo 3. Have fun with error 37 :) Anyway, the framerate issue seems to have been fixed, I can finally play again :D

Bullshit. I tried that and it didn't do shit.

E8400 560 GTX Ti 4 gigs of ram Was doing 50+ frames with FXAA before the patch. Now down to as low as 15 fps on the beach (!!!).

Same here, but I don't get an error message. The game either freezes forever at receiving data or it crashes to desktop at some point.

What are you talking about? Look in the bug report forum. Most of them have Intel & Nvidia, as do I. Not that that matters, the issue is the visibility distance that was increased with the patch. And a note to everyone: please do not refer to low framerate as "lag". It's confusing. Lag means poor connection, high latency.

Dude, just set the fog to what it was before the patch.

No. It says in the patch release notes: "* [FIXED] Fog is way too thick" I assume this means visibility distance' date=' because there is no other way to make fog in this engine that I know of. You'll also notice that you can see way farther now. The people with low-end video cards who are getting "perfectly fine" FPS were probably at the edge of the map looking at the sea where FPS is always high (I was able to get 125+ there with vsync off). Try the congested Chernogorsk center and the difference will be massive. Read please: Actually I did not know that :D. But yes, I fully intend to return once this is sorted.

A note on Field of View. An easy way to find a good fov for your monitor in ArmA2 is to first note what aspect ratio your resolution has. For me it's 5:4 (resolution 1280x1024). ArmA2 automatically detects your aspect ratio and sets the fov accordingly. For me the default values were: fovTop=0.75; fovLeft=0.9375; These are way too narrow for me. What I did was simply multiply both values so as to keep the same aspect ratio. You don't want to stretch the fov too far vertically or horizontally. In my case multiplying by 2 yielded these values which look OK to me: fovTop=1.5; fovLeft=1.875; You can experiment to get a fov that looks good to you. Remember to multiply each value by the same amount or you could get weird stretching.

Guys, they drastically increased the visibility range setting, which is a server-side setting in ArmA 2. That means there is nothing that can be done on your end, every fix people have suggested here is a placebo. We must demand that the developer sets the visibility back to what it was before.

Same here, down from almost constant 50+ to 17 on a 560 GTX Ti. Unplayable. I'm done with DayZ unless they fix this. They should not have touched the visibility distance. It was reasonably low, but they have probably set it to something like 10 000 now, which brings even a high-end PC to its knees. If they think most DayZ players have very powerful PCs, they have misjudged their target audience. Au revoir, it was fine while it lasted.

I would stop playing if my character was NOT persistent across servers. Getting into one specific server is a matter of luck right now. I'm not going to wait for 30 minutes to get to play the one character that has survived the longest and has the best stuff. If all servers were to become separate, then the value of survival would be greatly diminished.