Jump to content

Henk85

Members
  • Content Сount

    24
  • Joined

  • Last visited

  • Battles

    20301
  • Clan

    [OPGS]

Community Reputation

0 Neutral

About Henk85

  • Rank
    Seaman
  • Insignia

Recent Profile Visitors

231 profile views
  1. In my opinion its pretty simple: it doesnt matter how the cv's are played. So the difference between the previous and current style isnt that important. There are still ppl averageing well over 150k a match, hence carrying just as hard as they did in the previous cv-gameplay. In the end there will be ppl that know how to play it, and ppl who dont. And ofcourse when you play dd these days ur gonna be in for a rough ride. A good cv will find you and once your spotted the shell rain starts, you smoke and you will get radared. What it comes down to is the spotting mechanics of CV's, I believe that is what irritates ppl most. A good cv knows that killing enemys isnt his sole job, but he has to find targets for his friendlies to shoot at, drop AA to protect his friendly ships (especially when capping). In my opinion the only way to fix this is to let winrate/PR/average dmg take a role in MM. Otherwise you will still get into unbalanced games that get decided by a CV that understands its job (vs one that doesnt).
  2. Hope its fixed. I got the same thing. Nothing worked, even tried a fresh windows install. Now I heard it might had to do with maxing out my pc's powersupply. I've brought down the gamespecs a little and underclocked my GPU (using MSI's Afterburner), which seems to work. So thank u BURN_Miner
  3. Henk85

    New video card?

    Hope its fixed. I got the same thing. Nothing worked, even tried a fresh windows install. Now I heard it might had to do with maxing out my pc's powersupply. I've brought down the gamespecs a little and underclocked my GPU, which seems to work.
  4. Ok, I guess there is a point in fixing something that is broken and might lead to unexpected results or an unstable game. What I do not get is why not leave it unfixed untill u can fix it properly (that is, same result; different code).
×