Mos1ey

Will run close to max settings with decent FPS, you might have to drop them a bit for recording though.

The only things that I was ever using MMB for were doors and ladders so I figured it was a bit of a waste to use such a well positioned button for something so menial, that can be done with the scroll wheel. I use it for toggle zoom out now instead and I think that's definitely better, for me at least.

I think the idea was that it would be situational. You can't lean while running anyway so Q and E would assume the function of looking behind you whilst running, while still functioning as 'lean' the rest of the time. It seems a bit silly to me when you can Alt so easily reachable with your thumb the entire time though.

You're pretty badly bottlenecked by the graphics card. You'll run the mod fine but I don't think you'll be able to record with Fraps unless you drop your graphics settings right down. I'd think about upgrading your graphics card, the rest of your system is great but it's really dragging it down.

I play AWA #1. It's pretty much the closest thing to vanilla that isn't empty, lol.

Inb4 horse meat lasagne.

It's probably not what you want to hear but I think you'd be a lot better off just saving up and putting a desktop together. Laptops just aren't great for gaming, and you'll just end up having problems again eventually.

I mean delete your @DayZ (or whatever you called it) folder and install the DayZ 1.8 patch again.

Unlucky, lol, but yeah, these things happen. The only advice I can give you is try to stabilize your connection to prevent from lagging out in future, unfortunately.

Yes, you'll definitely run the mod no problem. I'd say medium settings but it's hard to judge when I don't know exactly which CPU you have there. Are you using any startup parameters? If not, try these... -cpuCount=6 -exThreads=7 -maxvram=2048 -maxmem=2048 -nosplash -high Make sure that video memory is set to default in your ArmA II advanced graphics options. Also, have you tried a few servers? Some use shared hosting or are run on poor machines and will perform poorly. It's worth trying a few different ones.

This.^ First and foremost you need to figure out if it's a hardware or software issue.

No problem. :)

You need two copies of Operation Arrowhead. You should be able to both use the same ArmA II key but you will need seperate ones for Operation Arrowhead.

You increased your res and gained FPS? That doesn't sound right. It's more likely that either the server you were originally playing on was very slow, or it could be down to your location on the map. I get 60-70 FPS out in the middle of nowhere but 40 in cities. That's good that you've managed to sort out the issues that you were having, anyways.

Go in to the Anansi driver software like we talked about earlier, click on the space bar and assign function: default key. You've probably recorded a macro by accident.

They may have updated the files. I'd reinstall 1.8 and try again.

I think it's Alt + Enter while in the server menu.

Cheap PSUs can quite literally blow up, I've had a cheapish one shoot sparks out the back before, lol.

Yeah, looks like you've ended up in windowed mode somehow.

If you're running through DayZ Commander go in to the settings in DZC and make sure you haven't ticked 'Windowed Mode' If that's not the case then in ArmA 2 try this... Options > Graphics Options Make sure 3D and interface resolution are both set to your monitor's native resolution. Restart the game.

Ah, that makes sense. Fn + M enables the macro feature, lol.

The white arrow.

You've probably changed your 3D resolution. Just change it back to your monitor's native resolution and restart the game. On the Razer Anansi Fn + F11 enables 'gaming mode' but all that does is disable the Windows key so that you're able to assign a function to it in a game as far as I know. If you open up the Anansi driver software from the system tray you can check that you haven't accidentally assigned a different function to the space bar. If that's not the case then try restarting you PC and see if that fixes it. If that doesn't work then try reinstalling the Anansi driver software... http://drivers.razersupport.com/index.php?_m=downloads&_a=viewdownload&downloaditemid=562&_m=downloads&_a=viewdownload&downloaditemid=562

He's edited his system specs out of the OP for some reason. Starting to seem like a strange troll attempt. :S

Okay, well that I can't help you with unfortunately, lol...