Playing Domination on Locker with a few lads from here, though had to rage quit due to admins camping on the inaccessible balcony at C flag. I refuse to play when people are glitching just because they are too bad at the game to get kills any other way.
That's one of the reasons why I enjoy the tfu operation locker server, as people glitching there are usually dealt with quickly. Plus it's a good map for unlocking guns and attachments.
Playing Obliteration on Operation Locker (on a server with out a stupid 15 min time limit), can be great fun if any of you haven't tried it yet.
Glad you like our server. We do try and kick anybody who thinks it's acceptable to play like that.
I haven't seen you on before though, you're welcome to add me on battlelog so we can squad up.
My battlelog name is: Netphreak
You've probably seen me trying (and failing) to kill people using random weapons nobody uses, or chasing people with the EoD bot.
Ooooh interesting!
So the budda's code has been cracked!
errrrr I'll correct a couple of points there :d
SMAW is unguided less powerful but flater trajectory RPG, the SRAW is kinda like the AT-4 from BC2. Also the Double SRAW / Igla was meant to have been fixed, haven't checked tho.
Airburst you aim (while NOT ADS's) at the cover the target is croutched behind then ADS over / around the cover and fire away. It's the aiming when not ADS'd that sets the range![]()
I've recently purchased an overclocked system consisting of an i5 4670K paired with an R9 280X. Naturally, I expect the game to run well, but is the ultra preset within reason at 1080p? The CPU is coupled with a Corsair H60 and clocked at a stable 4.2GHz. (Windows 8.1 is my OS of choice, owing to better optimisation etc.)
First bsod in a while in the middle of a fun round of cq, (0x124), seems this chip needs a touch more voltage.
Strange at stock, was it the same bsod code as i got? 0x124 is normally a sign of too little cpu vcore, sometimes though it can be memory controller rated such as system agent or ioa/d. Im running 2400mhz memory via xmp, but have upped cpu voltage a touch to see how it go's. May also drop the ram to 1600mhz too.I have just had exactly the same problem. I'm running at stock speeds now so see no reason why it would do it...
Strange at stock, was it the same bsod code as i got? 0x124 is normally a sign of too little cpu vcore, sometimes though it can be memory controller rated such as system agent or ioa/d. Im running 2400mhz memory via xmp, but have upped cpu voltage a touch to see how it go's. May also drop the ram to 1600mhz too.
On Tue 10/12/2013 23:27:25 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121013-3687-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x255D)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A003FBAE00, 0x8, 0x272AAC)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.