Failed to create agent because it is not close enough to the NavMesh

Discussion in 'Rust Discussion' started by Bear 9, Oct 21, 2017.

  1. Bear 9

    Bear 9

    I have Oxide build 2.0.3600 spamming into the console. Oxide build 2.0.3608 will fix the problem?
     
    Bear 9, Oct 22, 2017
    #21
  2. Wulf

    Wulf Community Admin

    Oxide doesn't have anything to do with the error in this thread. The only relation Oxide had was with AI not moving from the conflicting protobuf-net, which was resolved days ago.
     
    Wulf, Oct 22, 2017
    #22
  3. [MorFin]

    [MorFin]

    [MorFin], Oct 22, 2017
    #23
  4. alukar

    alukar

    Thx !!!
    And what about hurtworld. Remove this file too ?
     
    alukar, Oct 22, 2017
    #24
  5. Wulf

    Wulf Community Admin

    You can, it won't be used unless you have something loading it such as an extension or plugin.
     
    Wulf, Oct 22, 2017
    #25
  6. draindoc98

    draindoc98

    Hey Wulf!.....Just so I am clear on the whole "protobuf-net.ddl" thing.....are you saying that that file should "Not" be in our
    RustDedicated_Data/Managed File!?
     
    draindoc98, Oct 22, 2017
    #26
  7. Wulf

    Wulf Community Admin

    It doesn't need to be, but unless you have something loading that it won't harm anything. I'd suggest removing it anyway though.
     
    Wulf, Oct 22, 2017
    #27
  8. draindoc98

    draindoc98

    Next, probably really stupid question, but........Do I need to shutdown server in order to get rid of protobuf-net.dll file?
     
    draindoc98, Oct 22, 2017
    #28
  9. Wulf

    Wulf Community Admin

    Generally no, but it'd be best to, especially if it's being used.
     
    Wulf, Oct 22, 2017
    #29
  10. draindoc98

    draindoc98

    Thanks Wulf!
     
    draindoc98, Oct 22, 2017
    #30
  11. oxijen

    oxijen

    is the problem still existing?
     
    oxijen, Oct 23, 2017
    #31
  12. Smabezo

    Smabezo

    I'm getting this shit
    Code:
    Failed to create agent because it is not close enough to the NavMesh
(Filename:  Line: 674)
Failed to create agent because it is not close enough to the NavMesh
(Filename:  Line: 674)
Failed to create agent because it is not close enough to the NavMesh
(Filename:  Line: 674)
Failed to create agent because it is not close enough to the NavMesh
(Filename:  Line: 674)
Failed to create agent because it is not close enough to the NavMesh
(Filename:  Line: 674)
    seems it happens after 150k entities

    C'mon facepunch, stop adding bullshits to the game and start to fix the plenty of bugs that it has!!!!!
     
    Smabezo, Oct 23, 2017
    #32
  13. Ryrzy

    Ryrzy

    strange... i have this isue too. i have new oxide, i removed protobuf-net.ddl, reboot and still... animals are fuc*ed up (they move but they are stupid). i thinked to make full reinstall of server but how to backup blueprints ?
     
    Ryrzy, Oct 23, 2017
    #33
  14. Bear 9

    Bear 9

    Copy the folder "my_server_identity"
     
    Bear 9, Oct 23, 2017
    #34
  15. M16A3Brah

    M16A3Brah

    It'd appear like yesterdays Oxide update fixed the Navmesh error.
     
    M16A3Brah, Oct 23, 2017
    #35
  16. Smabezo

    Smabezo

    Someone has fixed it? Problem still persists, even after update to the last oxide.
     
    Smabezo, Oct 23, 2017
    #36
  17. Wulf

    Wulf Community Admin

    Nothing has changed in Oxide for Rust, not related to Oxide as Oxide does not modify or control the AI without plugins.
     
    Wulf, Oct 23, 2017
    #37
  18. Smabezo

    Smabezo

    Yeah, I know that Oxide is not related with AI, but that guy posted that the update Fixed the problem for him.

    PD: C'mon facepunch, stop adding bullshits to the game and start to fix the plenty of bugs that it has!!!!!
     
    Smabezo, Oct 23, 2017
    #38
  19. Ryrzy

    Ryrzy

    for me not ;/ everything is up to date and still spam in console ;/
     
    Ryrzy, Oct 23, 2017
    #39
  20. Alistair_Mc

    Alistair_Mc

    Hey guys,

    We've released a new update today (changeset 23432), we hope this should resolve the issue. The AI was incorrectly spawning on the constructions layer.
     
    Alistair_Mc, Oct 23, 2017
    #40