EsaTuunanen

What Event Viewer says for time of game log outs? At least for not total freezes there might be some hints to source of problem. And in case nothing seeming to respond after exiting game have you tried using Ctrl+Shift+Esc to see if Task Manager opens up? And GTX660 is so old card that latest drivers are more likely to just keep breaking things than improving anything. Nvidia simply doesn't give a damn for people with not the latest (and more expensive than predecessor model) cards. (just like they cared for fair marker competition only as long as they were the underdog below 3dfx)

Actually gameplay of every different style ships should be checked even without interest in playing that style ships: Knowing the enemy is half of the battle. For example Aerroon, Flamu, iChase and Notser have good videos showing how various ships play.

For first three tiers new players have separate match making pool. At T4 you'll meet players of all different experience/skill levels. And showing side of cruiser to destroyer can be fatal Though in case of T4 RN cruiser Danae even destroyer HE shells can score citadel hits doing max damage of shell. Like already said by others RN CLs are very demanding ships and not goot for learning game mechanics. Besides knowing how to aim those need also hitting to correct spots of enemy ships and how to position yourself, because unlike HE AP is sensitive to hitting angle. USN cruisers up to T5 would be better for learning basics... Though still being demanding because of amount of battleships in matches and possibly being often bottom tier in Tier 7 match. As for aiming part have you already enabled Atlernative Battle Interface Mode? Learning to lead targets basing to shell flight time makes it easier to swap between different shisp with different guns.

In the form of: ...The next post copies the list and removes 3 points from the ship that they think is worst and adds 1 point to the ship they think is best... http://forum.worldofwarships.eu/index.php?/topic/65517-tier-x-elimination-thread-warships-edition/

Score/kills/damage etc are decided and kept track by server. Client just shows those basing to data it gets from server. Updated any drivers recently or installed some software before problem started and what Event Viewer gives for errors near times of crashes? Though software problems can't cause easily total PC crashes. So possibly something might be going bad on hardware side... What's the precise model of PSU? Lot's of them with cheap Chinese parts which can't be considered very reliable for longer term active PC use... Especially if having old case with PSU on top sucking in heat from CPU and and third party/non-reference cooler equipped graphics cards. For heavy CPU stability testing there's Linpack based testing like LinX: http://www.xtremesystems.org/forums/showthread.php?201670-LinX-A-simple-Linpack-interface Hour or two of that without problems (no crashes/smoke) is good sign for CPU and its voltage regulation being OK. Prime95 in Blend and Large-FFT modes puts also some stress on memory controller and memory. http://www.mersenne.org/download/ For "smoke testing" of graphics card FurMark is very good, though nowadays GPU drivers detect it and limit clocks to prevent magic smoke from escaping. FurMark and Linpack together is again good for putting heavy load on PSU.

Aren't those two parts mutually exclusive? But yeah, Assassin's Creeds definitely have good feel of environment for game's time period.

Actually: At least 4, preferably 5/6 BBs. The rest don't really matter, except preferably no CVs capable to annoying BBs.

Calling all BBs as overnerfed? Well, that should be bigger disqualifier for voting eligibility than failure to read rules of elimination and randomly just down or upvoting.

87% survival - 75% WR - 63,4k avg damage and 10,8k kills too low for 4½k matches? With "fun and engaging" detonation from first hit(s) responsible for 14% of sinkings... Propably 25-30%, if it was possible to look just this year. Which is why I know claims about detonation chance being random per shell hit as BS. (except randomizing in which match player gets usually totally screwed) It doesn't have any better stock turret traverse, or detectability. (6,8km is with camo) HE fire chance is 9 vs 8% and 55 knot torps take minute to reach final stop. But maybe you want to ask this enemy team how weak Gremlin is: And today first match in couple days: 149k damage, obvious High Caliber and Confederate. First gunning Mutsuki out from cap. Then smoking to cap and send torps at suicide rushing Kongo, eventually sending it 4½k hp worth HEs before 5 torps deducted rest. During that Mutsuki came for more spanking and I got the kill with 9,3k hp piece of that cake, err ship. After that no enemies wanted to contest cap, so I kept gunning for total of ~100k HE+fire damage. (5% fires in T4/5 match... but 217 hits starts few) Including 11k to enemy Bogue fair 13km away (instead of BB at ~10km) to make sure Bogue stopped hurting team mates as fast as possible.

Can't half the people voting here anymore even read what's the actual latest point situation or why so many trying to start from old numbers? Now what might be their ability to understand all game play mechanics, analyze possible scenarios etc... Zuiho (1/2/1) : 8 Kongo : 2 + 1 = 3 Fujin/Kamikaze : 18 - 3 = 15 More OP than Gremlin against bad enemy team, but one trick pony scales badly in other case and against planes+radar. Gremmy : 32 Surprised didn't upvote Gremlin this time? That's because all possible scenarios considering Kongo definitely doesn't deserve that much worser score than "Fukamikaze". Which can be negated very effectively by enemy players being good, hydroacoustics, planes and finally radar of tier 7. While guns work in every situation. Plus Kongo has range to possibly snipe spotted unwary CVs. And while sure having harder time against T7 BBs Kongo's speed and range gives good control and options for engagement... Though I don't mean that one Kongo (followed by Colorado) hiding at border behind island in SW corner of minimap: Neither can cruisers swarm Kongo so easily unlike slow BBs. And because of that speed also DDs can't dance around it just like that. Heck, skilled player in Kongo can actually push detection avoiding DD around.

You need to update your game knowledge. It's been couple months since MM last allowed two destroyer difference between teams. And at this rate German DDs might just get hydro so that they don't need cruisers to detect enemy DDs behind islands/smoke.

I don't think WG would sell anything in eBay when they have own shop... Only time when when I would see them doing such auction is if it was somekind charity campaign with proceeds donated to something. Not even for this?

Balless Boats should move at least near cap to support capping instead of hiding 10km behind at map borders and too often behind some island(s) blocking firing line to map's center areas!

With Bismarck being famous for basically YOLO rush... In which concussions from first firing of its main guns against British cruisers knocked out its own radar. Tirpitz again being German version of "Hotel Yamato"... While also being practise target for many RAF bombings. Then Scharnhorst eventually sinking in another YOLO attack, with Gneisenau's fate being even less prestigious... (after career of mostly sinking helpless cargo ships) That "prestige" sure is funny thing, isn't it?

Who ever wrote that clearly haven't played game at all! It's conflicted by actual game and in no way explains why especially destroyers have so clearly highest chance to detonate from first hits. With amount of suffered detonations from total decreasing rapidly the more hits destroyer has survived/the lower its hp is. While that "data" would imply not even completely random distribution of detonations evenly at various hp levels of ship. But completely opposite of what's actually happening, with average chance of detonation from next hits increasing the more hits you've taken. So we can conclude that myth as BUSTED.

Well, isn't that what everyone should do to players failing armor angling... Like one enemy Aoba in early week Fault Line match when enemy had pushed from other side to cap. Cruiser not angling against stealthed destroyer is understandable... until you have battleship few km behind you! After offensive smoking and half of its hp removing 130mm AP salvos that team mate in Colorado removed rest of Aoba's hitpoints. Must have gotten real drafty in engine room with all the citadel hits...

Autobounce angled cruiser belt armor bounces every BB's AP. In those situations BB needs to aim ahead of citadel overmatching bow plating and smashing through citadel's forward armored bulkhead. Against higher tier cruisers Scharnhorst would have harder time in that. But very fast turret rotation (for big guns) and faster reload again give more chances to surprise someone. So in giving up something it also gains advantages in elsewhere.

Or are you getting only some other map instead? I I've had all seven or eight matches today in it. First at mid day and now three in row.

Just where are potential damage tanking missions for BBs? Instead of absolute damage it should be easy to make it related to ship's HP pool so that high tier BBs don't have advantage. That would be best for getting BBs become more active and maybe teach someone to stop showing broadside constantly to enemy team (while sailing to some useless map border/corner) if told when selecting mission.

Well, game play is definitely too often like watching crash happen you already saw coming 10 minutes ago.

Forced and unskippable long animation of reward crates have already been discussed at least once. Maybe in some day there will be some animation skipping or automatic background opening option so that regular players don't have to keep watching those same animations over and over again.

And it's almost like those missions have vastly increased amount of total retard play with so many Balless&Brainless boats firing HE yesterday.

Battleships are least affected by detonations. I see cruisers detonating lot more often. And destroyer's are the most affected with single small caliber HEs (no way to reach magazine below waterline behind all compartmenting) having ridiculous chance to detonate them from high hp. But let's hope that BBs start detonating as often as other classes! Maybe WG will then give this mechanism head shot or at least remove that huge detonation chance bonus of first hits and make it actually random. It definitely doesn't do that. Or it's also as broken as "randomness" of detonation.

Guess amount of player retardness must have infected server...

You don't use zoomed in view for launching torps, ever! In that case it's 200% your fault. Standard zoomed out sailing view is more than accurate enough for launching torps and shows straight away if there's team mate next to you.