If killing a standard scientist on the Large Oilrig solves this, I can't imagine it having anything to do with Oxide. Is this happening to servers without Oxide?
"SetDestination" can only be called on an active agent
pretty much what the title says. it just spams i would say about a 100 times
Failed to create agent because it is not close enough to the NavMesh
(Filename: Line: 648)
any way to fix this?
EDIT: It is also before that putting "
"SetDestination" can only be called on an active agent that has been placed on a NavMesh.
"
a couple of times
Failed to create agent because it is not close enough to the NavMesh
(Filename: Line: 648)
any way to fix this?
EDIT: It is also before that putting "
"SetDestination" can only be called on an active agent that has been placed on a NavMesh.
"
a couple of times
From what i can gather this is related to the scientist on the oil rig, i as well had the errors , ive updated all plugins and checked everything.
Killing the floating scitentist on the oil rig does clear the error for now.
This appears to be a Facepunch sided error.
Killing the floating scitentist on the oil rig does clear the error for now.
This appears to be a Facepunch sided error.
How to Filter the error? Seems that there's no fix at this moment
In response to Adriok ():How to Filter the error? Seems that there's no fix at this moment
There is a fix. It's been posted in this thread at least twice. I haven't seen anyone report that killing the specific scientist on large oil rig not working.
https://umod.org/community/rust/7249-setdestination-can-only-be-called-on-an-active-agent?page=1#post-11
It worked for me. No issues since.
https://umod.org/community/rust/7249-setdestination-can-only-be-called-on-an-active-agent?page=1#post-11
It worked for me. No issues since.
You know if your toilet is broken you can crap in your hand and walk it outside. But I would rather fix the toilet.
Still not fixed on my servers... Note that I help run 8 servers with all diffrent map seeds.... Every restart this error pops up... guess what my 8 servers restart every 12hr... no... just no.
As a temp solution to the RCON spam I just set RustAdmin to filter out the "SetDestination" lines so I can see actally needed things
As a temp solution to the RCON spam I just set RustAdmin to filter out the "SetDestination" lines so I can see actally needed things
dont know if this is related, but on one server i simply updated this event randomizer plugin and it seems to have fixed the issue:
https://umod.org/plugins/event-randomizer#updates
if you guys also use that plugin and havent updated it im wondering if it was the plane caught in a low spawn causing this.
Seems fixed for me for now.
Merged post
Update and it's back! XD dang it
https://umod.org/plugins/event-randomizer#updates
if you guys also use that plugin and havent updated it im wondering if it was the plane caught in a low spawn causing this.
Seems fixed for me for now.
Merged post
Update and it's back! XD dang it
Update - I haven't seen the error but like 1 time for 1 restart in the last few days.