Jump to content
Forum Shutdown 28/7/2023 Read more... ×

m4inbrain

Beta Tester
  • Content Сount

    662
  • Joined

  • Last visited

  • Battles

    525

Everything posted by m4inbrain

  1. m4inbrain

    Very bad performance with destroyers - Mitsuki

    Well.. Stuff to look forward to, i suppose. Still worth it, while i have fun with US DDs, later on i do think it's harder to make them work thanks to very limited torprange.
  2. m4inbrain

    Very bad performance with destroyers - Mitsuki

    Just started with the Mutsuki as well, tried to grind through all the stuff needed to get the longer range torps back - it's.. workable now, to put it politely. It's a huge letdown after the Minekaze though.
  3. m4inbrain

    Lag issues

    I do have lags/rubberbanding, but fps stay constant regardless of time of the day.
  4. Disagree. If a BB cant dodge incoming torps anymore, which has to be seen, even with high torpspread its easier to score more than one or two hits by altering the attack angle between squads. Otherwise, i cant really see a problem for the class that has the highest potential damage and survival rate apart from being brainnumbingly boring to play.
  5. m4inbrain

    Homing torpedoes

    Sure. Right after the deathstar and the HMS Nevergonnahappen.
  6. m4inbrain

    Lag issues

    Certainly. Not trying to be mean or something, but that CPU is simply awful nowadays. You will have alot more fun with a more recent one, even from the lower end of the scale.
  7. m4inbrain

    Lag issues

    Ouch. Well, a dualcore with 1.65gh won't cut it for a game that is in development. Keep in mind, World of Tank went through alot of optimization, whereas World of Warships did not.
  8. m4inbrain

    Lag issues

    Yeah, think so too - if you get 20fps with everything on minimum, that's an issue. I have a lower-end PC as well, but at all settings mid/high i run more or less constant 50fps. Drops a bit if a BB misses me alot and there's alot of waterfountains, but alas.
  9. I wouldn't say that "fixed" turning rate of BBs does nothing to correct the issue of a bigger spread.
  10. m4inbrain

    Homing torpedoes

    Also first used by KM, which isn't in the game. Yet. edit: homing torpedos and spirit of fair play in one sentence doesn't work.
  11. Nah, in this case i actually do agree. Smoke should have drawbacks, not be a ninja tool. And i just recently started DDs and decided that that's where i'm staying. Smoke is a defensive tool for DDs, not an offensive tool for everything else. That also goes in line with all other abilities in game, which all, with no exception, are defensive.
  12. Am i missing something? Honestly now, i thought that ships in smoke are detectable the second they shoot, apart from torpedos. That's the impression i get as DD as well, the second i use my main guns (out of fog) against a CA or smth at +-5km range (which is in detection range for my "unfogged" DDs, between 5 and 6km), i get shot. And i don't mean people shoot in my direction, i mean getting destroyed even though i'm swerving and never ever stand still in a DD. If that's not the case, it should certainly be changed. If you fire your guns in smoke, you should get detected. But if you don't, or use your torpedos (main weapon of DDs), you should stay invisible.
  13. m4inbrain

    Lag issues

    Could you tell us your specs? It's hard to judge without them.
  14. After reading the new patchnotes, long needed help for CVs is in sight!
  15. You know what's really odd? That in fact ships are visible if they fire their guns in smoke. The only thing that works in smoke without you getting visible is torpedos. PS: the smoke hides you as well if there's nobody else spotting from (for example) above. Don't take it the wrong way, but if you don't even know how the mechanics work, you shouldn't rant about them.
  16. m4inbrain

    fps drops 4th of june

    Am i missing something, it's the fourth of june?
  17. m4inbrain

    DD's RNG has become unplayable

    That's what i read into that - but there's also the possibility that this community representative talks out of his ar..mpit and just made crap up to get off the case (hence it was immediately closed). And again, it might be nitpicky, but it doesn't even feel like i was talking to an actual community representative, thanks to all the spelling errors. In my world, if you get a job that's literally purely based on communication, you don't hire someone who puts 7 errors in that tiny paragraph there. -.-
  18. Thanks for pointing that out - i'll give that a shot. The lead indicator in that one is so much better than the stock one.
  19. I bet that system was developed hand in hand with Nintento, and the 3DS. I'm just wondering then.. Would a desk-fan count as "bot" then?
  20. m4inbrain

    DD's RNG has become unplayable

    Here you go then. Fixed spelling errors and removed name, but that's it.
  21. m4inbrain

    Issues in the US cruiser line

    Weee, Augustdorf - i was stationed there for two years.
  22. m4inbrain

    DD's RNG has become unplayable

    First time for me too, that support ticket is translated decently though. If needed i can add the german original posting, if you're able to read that. A penetrated magazine btw does considerably more than just taking out a turret. A torpedo is 500kg of destruction, compare that to a 2kg shell that does more damage. Even if i drop that torpedo somehow flat on top of a ship, it will (and has to, considering the reload and how hard it is to hit with them compared to shells) do more damage.
  23. I agree with that - the problem is, it doesn't change the problem that the TE and Seth want to see nerfed. Both clearly stated they want to see ships in the fogs. They do already as soon as they open fire. They resort to simply exaggerating or in case of Seth plain lying to show how OP smoke is - but in the end, and i'm sorry there, if you can't deal with smoke, you're simply bad. DDs don't need to see out of the smoke anyway, since you don't need vision to zone with torpedos.
  24. m4inbrain

    DD's RNG has become unplayable

    Funny enough, i got an answer from support. Have to translate, since for some reason, even though i wrote the ticket in english, i got an answer in german (and peppered with errors, which is kind of a disgrace for a company as big as WG). "Ahoy, This is not a bug. Torpedo damage (and projectile damage) can and will vary, and depends on a couple of factors. A heavily armored section will reduce the received damage considerably. Please keep in mind, that ships in WoWs are compartmentalized into segments, each of which has its own hitpoints. If a section was damaged, or destroyed (ie, if their HP were reduced or reached 0) then it can happen that you do little to no (0) damage will be done. Regards, name of a german customer support guy." This sounds an awful lot like "there is no ghost shells", just to backpaddle after years and attempt to fix it. Since we're talking DD vs DD, there are no heavily armored sections. Then, and i'm just assuming here, it HAS to be a bug that a section that was destroyed (engines/rudder for example) basically is immune to damage now (if that is the issue anyway). Especially considering that they clearly are still working. And just as a sidenote: this supportguy is a joke. He not only did a couple of spelling errors (not speed-typos, but spelling), which is a nono already - he immediately closed the ticket. I'm sorry, as a "Customer Service Representative", you did a really bad job. My issue is not resolved, and i can PROVE that what he was saying is bs, thanks to having the replay. The 118 damage minekaze did not receive critical damage prior. And it doesn't explain why a midship hitting torpedo does damage to the rudder. Nor is a Minekaze "heavily armored". Don't start that ghostshell desaster over here again.
×