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

dedman

Beta Tester
  • Content Сount

    4
  • Joined

  • Last visited

  • Battles

    26044
  • Clan

    [ODB]

Everything posted by dedman

  1. dedman

    Update 0.8.11: New Year

    1. collect container like you usualy do 2. on the left, instead of buy container stuff, you got collect 2 containers good luck
  2. Are you sure about that? I mean if you are behind the smoke, it does act as an object blocking the line of sight. But if you are in the smoke, I believe there are factors such as ship speed that affect your concealment. If I'm not mistaken, a few patches back, being on fire decreased your concealment in smoke, as well as AA being active.
  3. That could be the case, firing debuff value > smoke concealment value. The SA bug would be just the tip of the iceberg, e.g. SA working properly but detection mechanism bugged/desync etc (tinfoil here ) Furthermore I think that could be data-mined, no? Maybe WG messed up value by a decimal or two.
  4. hey guys, I have too had issues with SA and concealment. However I don't think the "2-3 seconds delay" is the most bothering issue here (might have been there or not before patch). The most annoying thing is the gun fire debuff within smoke: Before you used to be able to shoot (detected), pop smoke and stop and become invisible within seconds (2-3 seconds?) Now with this patch, you shoot (detected) pop smoke and stop (SA turns off), but keep being visible to the enemy for 10-20 seconds! I have experienced this in benson, got wrecked in my smoke after stopping (SA off) getting shot with precision for 10-20 seconds. Asked enemy if I was visible, and I was. There is a workaround to this: smoke and stop before you fire. Try it, you will remain invisible. This is far from ideal, so my benson & kiev will stay in port for now. So either the gun fire debuff value has been raised too high to be hidden by smoke, or smoke concealment is too low. Plus SA not working. @WG now, I find you "proof or never happened" stance very debatable. Don't you have test teams that can handle this? Because there is _obviously_ a problem cheers!
×