Sybeck

Well said. Toxic chat accounts for no more than 5% of my battles and if you discount the ones who leave the battle after being sunk with a "TEAM OF IDIOTS!" sign off then it would be less than 1%. Besides, any troll who wants to hang around a battle's chatroom after a battle is already missing the fun of his next troll battle and with the addition of a simple "Ignore" button we are keeping them out of chat and out of battle - WIN WIN.

Lol then get rid of ingame chat too if that's a drawback. Just add an ignore function.

+1

OMG! A company that makes a free to play game at all tiers might have the audacity to monetise their product and the use of its intellectual property! The little shits! They should be doing this for free and without wages and just be grateful that we can even spare the time to turn up here and moan at them about something that isn't even a proven fact. I'm surprised this is still going. 26 pages of self-interested ingratitude based on mere speculation, based on the paranoia of a few vested interests.

Game. Probably too much specularity (reflection) added in the texturing is my guess. And yeah, it's annoying to look at.

I'd ask the OP how he knows that a player who is dodging his shells actually has this skill? Good players don't sail in straight lines so as to avoid shells/torps and this also has the happy by-product of not having to invest in a useless skill that you've already compensated for by playing with some common sense.

I agree on that point. I don't need a warning for aircraft that are 20KM away. Anything within 10-12KM I am concerned about and the present warnings could/should be pulled down to that level. As for the OP wanting an alert for when a plane is attacking then has he not realised that the only time you could be notified that you are being attacked with 100% certainty is on the TBs final run, which would be too late to take proper avoiding action and after the bombs are dropped and on their way down. If you can't be bothered to pull yourself out of sniper vision with the biggest danger to your ship flying around you then you deserve what's coming to you. There are more than enough warnings already without adding another one, which as stated above, would be too late to react to to do anything effective and if you can't be bothered to unglue your eyes from binocular view then just keep hard ruddering till those pesky annoyances go away and leave you alone.

Today - Unplayable at @35K people on server - Bearable, but still regular, if shorter, annoying spikes at around 30-35K - Playable with very rare spikes at 25-30K people - No problem at all with less than 25K. Draw your own conclusions, though that's only "my" observations today.

Just adding my name to the list as another sufferer. This all started after the drop of the last patch. The game has been near unplayable since then. My FPS stays solid at 60-70 FPS, but it's the ping which is going crazy for me; spiking up to 250 for a couple of secs before dropping to 35 and then sliding back up to 250 causing the screen freezing/stuttering, which makes it near impossible to aim or fire munitions. All other MMO games I play are fine: BF4, ArmA3 and World of Warcraft. Have submitted a ticket to WG with a Ping Plotter report so will update when and if they get around to answering it.

Will just chip in to confirm that since last patch I too have have been suffering from permanent screen stuttering or rubberbanding. Have played with the settings, dropping graphics down to minimum and all I get is uber FPS, but the rubberbanding remains. I'm also on Win 10, but this problem only happened after the patch. Haven't tried the window option instead of full screen, but will try later when I get home from work and see if that makes a difference. P.S. All drivers are up to date, disks are defragged and all other MMOs I play are fine. CPU: Intel® Core™ i7-2600 CPU @ 3.40GHz (3392.29 MHz)Memory: 8175 MBOS Version: Microsoft Windows 10 64-bit (Build 10011)Graphics Card: ASUS GeForce GTX 680/PCIe/SSE2

4 out of last 5 battles in my Minekaze, and the pertinent 4 all being Fault Line, I've been sunk by my own side! By a Kuma, Omaha and a Phoenix twice and ofc in all cases NO enemy ship on the [edited]radar! Did I put the wrong [edited]deodorant on this morning, did I look lustfully at their mothers, did I screw their sister and never call again? Well maybe 1 of the 3, but FFS! Sorry had to vent. /rant

TY Ovan! I will overshoot my first broadside if I ever run across you; so no change there!

tl;dr Cannot afford a bitchin nVidia card END OF

How do I get to play this? Is it seekrit closed beta? If not can I join and all the other great unwashed peoples so you know what it will really be like when opened to the public?

Anyone who uses anime memes is barred on the grounds of already being a pussy and therefore is unable to raise a cogent argument before extreme lolz ensue.

You have shown by your question that you shouldn't be in control of a Midway or that you are lolz troll. Either way you shouldn't be captaining a Midway yet.

Again, never had this problem till latest patch dropped, and it's still affecting gameplay. Can only presume that it's not server side as everybody and their wife and dog would be complaining, so it must be calling some clientside function that was introduced in last patch. If anyone else is getting the same thing then speak up it needs to be communicated to devs if it's more than me suffering.

You know that makes no logical sense whatever...? Or do you? In fact if you wanted to write the dumbest response ever you have just achieved it. If there was a medal for stupid then you have just won it,but to which spot under a bridge and to what bridge do I post it to?

And you haven't torped me either! The theorem gains evidence! Though you are quiet on your mother.

Yeah these were all accidental, if death by stupid is classed as accidental.

So no hot mother or sister? ;-)

This has started for me since the latest patch. Up until today I've never encountered it, but it's happening every 30-40 seconds for about 2-3 secs and is really beginning to spoil game play when you have a target lined up and then it stutters back and forward for 2-3 secs. It's not the target moving ofc it's my view of it stuttering back and forth that gives the appearance of the target moving. This stuttering is called rubberbanding in other places. You suddenly stutter forward and then like a rubber band snap back to where you were.

Because after a week people will be complaining that 23 minutes is not enough time to realise you shouldn't have been chasing that last DD/CV and should have been capping earlier. Why not cut the pussyfooting around not enough time and just come out and ask for a Deathmatch mode where the game ends when there's no more players left alive on Red or Green? It's pretty simple, the mission is to cap or dominate. Failing that, killing all the opposition will also result in a win. I haven't seen a mission say, "Kill all the opposition, but failing that capping will also result in a win."

^THIS and Soooo Much THIS ^ - Have a +1 for detailing so well the scenario that is usually the case when somebody has 50% of enemy kills and blames their team for not winning.

Then I stand corrected and was misinformed in another post on this subject elsewhere. I guess I will just have to take extra pleasure in the schadenfreude