wilkatis_LV

How small your screen must be for them to be in the way? O_o

You do realize SCs are RNG based drop, right? Lets say the chance (and this percentage is just a random number I picked) to get an SC is 2%. That would mean that (on average) out of 100 containers 98 would be regular and 2 would be SC. Does that mean that you can't get 3 in a row? No it doesn't. There will be moments when you get SCs, there will be times when you don't. I got 3 SCs on February, 2 more on May, and then this week where I've scored 2 already. You're not going to score them each time, stop dreaming

Pretty much any cruiser of those tiers will do. Potential dmg isn't just hits you took / bounced / shattered. It's also all the shells and torpedoes that missed you

I'll just tag everyone so you can see it @RobS80 @Tyrendian89 @Skyllon @waxx25 @TVLX @iJoby @Negativvv @MortenTardo @Nimrod411 Solution is simple - DO NOT alt+tab out of the game while it's starting up, after you click "play" on the launcher let it get to the point where you log in. That way it will keep the game fullscreen if it was selected like that before you exit the game previously

Dmg to his own division mates doesn't count towards being a TKer Scoring damage AND a kill are both important, killing no HP enemy or just dealing some dmg to ally won't instantly turn you pink normally Also take into account that it depends on how often the player does Team Dmg - that Derpitz might have been "clean" for a really long time, so just 4 torp hits made him "under inspection" so to say, but not a teamkiller. Or he might have been assigned "TKer" status AFTER the match not in the middle of it. And someone being pissed and torping an ally in one of thousand games means you were just the unlucky one to receive it. It's a multiplayer game with Team Dmg enabled, someone is bound to get pissed and TK someone every now and then

@Fred3n @Aragathor @MaxxyNL Well, actually there was something just as they promised https://worldofwarships.eu/en/news/common/fish-and-ships/ "Fish and Ships" posted on 9th August

I think I haven't opened the inventory since the 1st time I tried it. Unless I can leave it loading for at least 30 min it's not worth to bother

In the campaigns never trust the text, it can and often will be misleading. Look through the icons (i.e. Mission 1 Task 2 says "ships of tier iX nad X" but the symbols are "random battle" / "cruiser" / "tier IX & X"). Icons are correct, text isn't

Just the typical amount of misinformation, nothing new for EU

these usually go through "Bug reports" thread, but whatever 1) Screenshots are still saved in your games directory. Just open the folder where your game is installed (default should be C:\Games\World_of_Warships or something like that) and there is a "Screenshots" folder where you'll have ALL of your in-game screenshots you've ever made 2) Replays have always being buggy. Here are some points that usually help: -Make sure it's a replay from the current patch - older patch replays won't work. If there is a micropatch (like 0.6.9.1 following the 0.6.9) in the middle there is basically as 50/50 chance that replays of the whole patch will work, probably with some issues like minimap not displaying islands -Do not use "jump back" ("<" and "Ctrl <") and / or "jump forward" (">" and "Ctrl >") -> they pretty much always will crash your replay, possibly even whole PC -Let the replay load in by itself, do not click on the "start battle" to get to it quicker 3) That's around for 1 or 2 patches, it used to be a rare occurrence, altho now forums seem to be spammed with it. Literally all you can do is to shut down WoWS through task manager and try to get back in as fast as you can

This has been around for a few patches, looks like it just affects a new massive amounts of people in this patch. Anyway, the bug is purely visual and doesn't actually impact your game Supposedly it's your PC being slow with loading in textures for all objects, and supposedly the "easiest" fix is having the game on an SSD not a HDD

As I (mainly BB player) see it there would be a rather easy way to deal with the "overpopulation" - increase cruiser survivability so [more or less half of all] the cruisers every game don't get instantly deleted and buff the IJN DDs to approximately where they were before all the nerfs. Nothing convinces you to move like a wall of skill threatening to nuke you, and people are generally better at dodging torps than they were when the game just came out

You mean USED TO GET better rewards? I'm sorry but I'll keep pointing out the 0.6.7 economy changes till I'll get an actual response about it You nerfed the "potential damage" reward for BBs by 70% there. Guess what - a BB who's pushing ahead, taking hits and tanking damage for the team (a.k.a. playing it correctly) instantly took a massive credits & xp cut. But wait, it gets better! Guess what the BB sitting at 30km with his range build Yamato doesn't get? He doesn't get shot at! So he was absolutely unaffected by these economy changes. As a BB to get a better score than that "sniper", who's sitting as far back as he can, the only way is to actually perform better than him on damage & kills, tanking dmg like you should doesn't give you anything

Generally just go watch some YT and Twitch. Flamu, Ichase, Aerroon, Notsers older videos, as well as many other people doing WoWS videos - all of those would most likely help to at least with the general idea

Just look at the symbols below the text, those are always correct while text can and often is misleading They are "Random Battles" / "Tiers IX & X" / "Cruisers"

1. Description Screenshots are partially inoperable. Screenshot is still saved to games directory in "Screenshots" folder, that part works as intended. Meanwhile just taking a screenshot (PrntScrn -> Insert -> Ctrl+C) and then pasting it (Crtrl+V) into a chat service (like Discord or Skype) or editing program (like MS Paint) returns this: 2. Reproduction steps -Take a screenshot in-game -Paste it in some chat service and / or editing program (like mentioned before) -Compare result to the screenshot saved in games "Screenshots" folder 3. Result Easily workable, just a small inconvenience 4. Expected result Pasting (Ctrl+V) a screenshot works just like it always did

1. Description Game starts in windowed mode even if fullscreen is selected, IF you alt+tab out of it as it's starting up 2. Reproduction steps Windowed: -Start client -Click "Play" -Keep doing something on your computer (i.e. browse the internet) -When the game starts up immedeately alt+tab out of it -Game will be in "windowed" mode no matter what was selected previously Fullscreen: -Have "Fullscreen" selected previously -Start client -Click "Play" -Let the game load in (recommended not to alt+tab before it's stably loading) -Game will be in the "Fullscreen" mode 3. Result Small annoyance of having to switch back over from windowed to fullscreen each time 4. Expected result Selected "Fullscreen" option keeps itself selected instead of resetting to "windowed"

Missouri's a BB No bug there, just poor wording in the description

A new (or new-ish) problem has been spotted above the horizon - people getting hit without being spotted. First signs of this (that I noticed) showed up in late 0.6.6 or early 0.6.7, slowly ramping up and becoming more and more... popular. Basics are quite simple - you are not spotted, but you are getting hit by someones main battery fire. Initially I always wrote it off with one of the following "explanations": -Long range fire, it was fired at the last moment and then took 10...20 seconds to reach the ship after it was spotted -Lucky blindfiring into a smokescreen (without any tracers to aim for) -Ridiculously bad aim at someone near me who was spotted, and it just happened hit my ship I started to pay more attention to this when I heard other players starting to talk about this, as well as saw more and more people writing in chat about it. While some situations could be explained with the points I made, they often just don't fit. Wasn't in smokescreen, was maneuvering after getting de-spotted, there are no allies nearby... This video is the best example I've got as of yet. The Maass, played by my clanmate, hadn't been spotted when at around 1min 20 seconds into the game enemy suddenly fired a reasonably accurate salvo at him (no hits scored, but all 4 shells splashed around his ship). And as you can see towards the end of the video - the spotting marker still works when you are actually spotted. Happens both - with and without - "Priority Target" trained on your commander, as well as both - with and without - any mods installed. My best guess is either it's a serious bug randomly showing the enemies some ship that shouldn't be visible or (most likely) some kind of a new exploit. Please do share any information / evidence you have about this, all of it could help to get rid of this problem before it's massively widespread.

Any chance of a replay? This game really needs that "save replays" selection added in options, so few people have them... To be fair... whatever. I'm giving up on this. 6 of 12 players responded, 0 of those 6 have replays enabled. There is a [more or less] fully functioning replay system for the game, and yet WG doesn't give players a reasonable ability to activate it - either you have to get a mod or you have to play around with the games code for it. Tomorrow's patch day, all replays from 0.6.8 will be useless. Case closed

Even assuming that you didn't read my write up, the title still says BUG / exploit. Not just exploit. I already point out how that could be the case of one or the other. In the video you get the gameplay footage from the pre-game countdown to shells landing around Maass, and then from the shells landing around the Maass to him actually getting spotted. He wasn't spotted in game, he doesn't get the spotted notification in the replay, and if you actually look where he is / where the enemies when they get spotted are - he COULDN'T be spotted at that point. Just as I said multiple times (I'll assume you didn't bother to read through all the comments as there are quite a few of them already) - I'll happily check out other peoples videos / replays with suspected cases of getting fired at while they are not spotted, as well as I'm continuously going through my own replays and paying attention to my "new" games scouting for more evidence to bring up, as 1 case just isn't enough. I even contacted the enemies of this match with the hope of getting at least 1 replay from their side, currently of those 12 just 4 have responded and none of them have replays enabled. I wouldn't have said anything if it wasn't occurring with suspicious frequency. These one in a million shots happen every now and then, but this seems to be way too frequent, that's why I'm trying to figure it out. The whole point for this video & post is to raise awareness, with the hope that people who actually record their games and / or have replays enabled could provide some more data as finding out something like this without any help isn't exactly easy to do. Even just the fact that you have to play around with the games code or to have a modpack installed to have replays available is ridiculous. Everyone should have a chance to have them easily, that would greatly help the community to weed out bugs, glitches and other problems

Well that's the thing - it might have been legit kill. Hard to say without inspecting the replay :)

Actually I went over that in the replay - when the shells are fired no ship gets spotted, and both - Hipper and Bayern pop up in line with them, Hipper was also looking ion the direction. But I'm not looking for someone who intentionally or unintentionally might be using this, I'm going after the problem (assuming it exists) itself. I could tell you which ship fired those if I wished to, by just carefully tracing back those shells to their starting location in the replay. That's not exactly what matters While this is a relatively rare occurrence, it happens way too often to be just a 1 in a million random shot As for "the ship behind" - what ship? Even if it's not so clear in the video I've provided screenshots in this same thread that quite clearly show there is no allied ship close enough for that to be the case

It's too early to get spotted that's why I included the whole part from timer running down to the moment the shells land, and then from the moment the shells land until the actual first encounter with enemy DD where Maass got spotted for the 1st time. Also the spotting indicator pops up and disappears together with your marker on the enemies minimap, meaning you know you are spotted before they can even see you (assuming you pay attention). I 100% agree that more evidence is needed, as 1 case is just nothing more than an empty claim. Hence the request for people to post here if they have anything, as well as me keeping an eye on my future games / past replays for more. Most cases can be explained, they just feel like you got hit unfairly. But there are situations like this one where I come empty handed as far as reasonable explanation is concerned. -------------------- As for this point - it's super easy to test it. All you need is to have training room enabled (I mean, it would still work in normal battle, but that's not exactly testing ground :D) In training room set up your opponents to be one or multiple immobile & unarmed AIs - basically stationary targets. Position yourself somewhere where you can shoot at at least 1 of them, select the target (by default that would be "X" key) if it's not already locked, and fire at different points around the area. The result will be simple - while aiming at a ship (since it's stationary you don't need any lead, obviously) you are going to hit a the ship, meanwhile while you have a ship selected and you fire at some point away from it -> you'll be able to witness aimassist in action -> your shells will go for approximately middle between where you aiming and where your selected target is. As for the terrain indicator.. it's delayed always, you will hit the island before it pops up and usually you can already fire at the enemy before it disappears. It's also largely affected by which battery you are using as your view point while in binoculars (by default settings it changes that automatically, default key binding is "C"). There might be a case where your front turrets may hit the enemy, but you get the indicator because you are aiming from your aft batteries. Is there a way to tag everyone who posted? Anyway, here are 2 screenshots from an elevated point of view on the tracers path: They definitely aren't aimed at the Fiji as it was suggested, those are accurate shots right on Maass' position. Also I'm trying to get in contact with the guys on the enemy team for a replay from their side, currently the only ones that have responded don't have replays enabled.

That's another possibility, yeah. That's I don't want to blame anyone, and I do regret instantly targeting the Kutu. Innocent until proven guilty!