[2.9.X] Enemy too near, hindered building placement

Discussion in 'Closed bugs' started by Xyaminou, Aug 22, 2016.

  1. Xyaminou

    Xyaminou Member

    Messages:
    1,362
    Likes Received:
    154
    Trophy Points:
    0


    In this video you can see that there are no enemies near the Refineries, yet both ruins and middle refinery were blocked by "Enemy too near".
     
  2. Thexa4

    Thexa4 Developer Staff Member Moderator

    Messages:
    304
    Likes Received:
    98
    Trophy Points:
    0
    Where in the video should we look?

    What should I do to reproduce this?
     
  3. Avatarix

    Avatarix Member

    Messages:
    422
    Likes Received:
    24
    Trophy Points:
    0
    11:52, there are no enemies nearby but he still can't place
     
  4. Xyaminou

    Xyaminou Member

    Messages:
    1,362
    Likes Received:
    154
    Trophy Points:
    0
    this forum is retarded and broke my link that started the video at the right moment. But to be honest you should watch all of it.

    I don't know that's why I posted a video of the thing. Now it's all you to find out why this happens. Talk to Smithy, pretty sure it's the same bug we had in one of the 2.9 beta tests.
     
  5. Neoony

    Neoony Member

    Messages:
    1,365
    Likes Received:
    106
    Trophy Points:
    0
    You cant do time link in embed videos.
    You just gotta make a pure link out of it, either with the "link" feature or just over code editor. Maybe you will have to remove the "http://" if you have trouble with forums forcing the embed video or something like that, cant remember exactly how I did it before.

    Actually let me have a try.

    youtu.be/dXn_HP_QNUQ?t=11m52s

    EDIT:
    Yes, just remove the "https://" from the time link and use the "Link" option in post editor features and it will stop forcing embed video and make a pure link out of it.

    [​IMG]
     
  6. Xyaminou

    Xyaminou Member

    Messages:
    1,362
    Likes Received:
    154
    Trophy Points:
    0
    My point was that there's a "media" button to turn youtube (and others) videos into embedded, so the link shouldn't do it by itself. That's a huge flaw if you ask me.
     
    Neoony likes this.
  7. Smithy

    Smithy Developer Staff Member Administrator

    Messages:
    333
    Likes Received:
    68
    Trophy Points:
    0
    After some testing with Neko_Baron and Avatarix, we couldn't reproduce it.
    We did come to the conclusion that the "Enemy too near." could be split into 3 separate reasons - player/vehicle/building. At least this way we know which entity is causing this bug.
     
  8. Xyaminou

    Xyaminou Member

    Messages:
    1,362
    Likes Received:
    154
    Trophy Points:
    0
    Did you check on your initial thought of it being a ragdoll or something leftover from player/vehicle/building dying?
     
  9. NekoBaron

    NekoBaron Member

    Messages:
    141
    Likes Received:
    18
    Trophy Points:
    0
    yes we tried that for players, we also tried combining it with disconnecting, reconnecting.
     
  10. Xyaminou

    Xyaminou Member

    Messages:
    1,362
    Likes Received:
    154
    Trophy Points:
    0
    Then I'm afraid you'll have to go through the code line by line...

    I didn't think you'd be able to reproduce it, which is why I haven't even tried.
     
  11. NekoBaron

    NekoBaron Member

    Messages:
    141
    Likes Received:
    18
    Trophy Points:
    0
    we know its client side, and the best thing I could suggest was to report which ents are blocking it as a debug, or as smithy said add new reasons so you can check the type blocking it.
     
  12. Xyaminou

    Xyaminou Member

    Messages:
    1,362
    Likes Received:
    154
    Trophy Points:
    0
    Well if someone tells me how to actually debug it when it happens, I will. But you have to show me how to do it.
     
  13. Smithy

    Smithy Developer Staff Member Administrator

    Messages:
    333
    Likes Received:
    68
    Trophy Points:
    0
    Think we've concretely found the cause of this bug. We have a fix to address it which will hopefully ship with the next patch.
    Thanks again to those who helped me in finding the bug and testing the fix.
     

Share This Page