BF3 lag issues

[ColKlink]

Just wondering if anyone can help me out with this.

I recently had my mother board replaced when it went faulty. It was replaced with a similary spec'd board.

Now, when I try to play BF3 I can't join any servers that have more than about 10 people. When I join a server with low numbers, I'm monitoring my fps and once it gets over about 10 people, the frames dropp down dramatically, to about 10 fps. I have no hope of joining a server with 32 people, just get a disconnecction error message.

I have other games installed and they seem to be running fine. I've tried swapping around my modem, to no effect. Tried 'Googling' for an answer and haven't found anything that helps. I can play it on my laptop, but it's not strong enough to handle BF3 and TS at the same time for long, before over heating.

I'm really at a loss here as my playing future with BF3 looks very limited atm. Any help/ideas appreciated.

[Phazon]

Hey Klink, did you install the network controller driver for your motherboard? Also might want to check that anti-virus isn't interferring with anything.

Post your specs and BF3 graphic settings as well. You might of accidentally activated the MSAA anti-aliasing which is very performance intensive on most machines. Depending on your graphics card, the Ambient Occlusion setting when set to HBAO also hits performance a fair bit when enabled.

[ColKlink]

Issue fixed, port forwarding problem. I've no idea how the laptop worked OK without the port forwarding though.

[Phazon]

Good to hear you managed to fix it.

[ColKlink]

Old problem back again. I had to reset my router to reiniatlise the Wi-Fi part, now I can't get the port forwarding right. This thing from EA about having to port forward is giving me the sh!ts.

[Shadow]

If you where getting lag last night it was ea side as everyone was getting it. If you need help with port forwarding you can get me in ts when l am on tonight and l can give you a hand

[ColKlink]

yeah, I did get a bit of lag last night, did think it was still the same problem, but it wasn't the same as earlier.