Infinity or nan error with Rust Experimental

Hi I am getting this error in the server console window over and over. I restarted the server but still getting this. Anyone able to help? Thank you.

Sorry For putting in wrong place.

 

Oh please help me you great ones!
Server Network Exception
IndexOutOfRangeException: Array index is out of range.
Infinity or nan floating point numbers appear when calculating matrices for collider.
Server Network Exception
IndexOutOfRangeException: Array index is out of range.
Infinity or nan floating point numbers appear when calculating matrices for collider.
Server Network Exception
IndexOutOfRangeException: Array index is out of range.
Infinity or nan floating point numbers appear when calculating matrices for collider.
Server Network Exception
IndexOutOfRangeException: Array index is out of range.
Infinity or nan floating point numbers appear when calculating matrices for collider.
Server Network Exception
IndexOutOfRangeException: Array index is out of range.
Infinity or nan floating point numbers appear when calculating matrices for collider.
Server Network Exception
IndexOutOfRangeException: Array index is out of range.
Infinity or nan floating point numbers appear when calculating matrices for collider.
Server Network Exception
IndexOutOfRangeException: Array index is out of range.
Infinity or nan floating point numbers appear when calculating matrices for collider.
Server Network Exception
IndexOutOfRangeException: Array index is out of range.
Infinity or nan floating point numbers appear when calculating matrices for collider.
Server Network Exception
IndexOutOfRangeException: Array index is out of range.

Another Issue I am having is Rusty Rcon tool won't let me connect sometimes. It has a mind of its own, sometimes it says connect then right after it will say not connected.

I am also having an issue with teleport script freezing and not working. causing me to restart my server everytime. Any known cause or fix?

 

I feel like this error is caused by someone..... I always felt that way!

 

This error isn't related to the one in Legacy I believe. It seems like there are 5 possible causes, the Net.sv.Cycle, the stabilityCheckQueue, updateSurroundingsQueue, stabilityGroundPath and AIHandler.Cycle as the specific error message is called by ServerMgr.Update() :

Code:

    private void Update()
    {
        Realm.PushServer();
        try
        {
            using (new TimeWarning("Net.sv.Cycle", 1f))
            {
                Net.sv.Cycle();
            }
            using (new TimeWarning("stabilityCheckQueue", 1f))
            {
                BuildingBlock.stabilityCheckQueue.RunQueue(1L);
            }
            using (new TimeWarning("updateSurroundingsQueue", 1f))
            {
                BuildingBlock.updateSurroundingsQueue.RunQueue(1L);
            }
            using (new TimeWarning("stabilityGroundPath", 1f))
            {
                BuildingBlock.stabilityGroundPath.RunQueue(1L);
            }
            using (new TimeWarning("AIHandler.Cycle", 1f))
            {
                AIHandler.Cycle();
            }
        }
        catch (Exception exception)
        {
            Debug.LogWarning("Server Network Exception");
            Debug.LogException(exception, this);
        }
        Realm.Pop();
    }

Still looking into it further if I can dig up anything concrete but what I can already say is that it is an actual server issue and it isn't caused by a player trying to hack like it was on Legacy.

 

Well all I know is I was using the old oxide update 59b, because thats all that was out when the last patch was released. So I requested gameservers update to 68. They sure are taking their time.

 

Confused by "The other snapshots are just new hooks" I dont understand.

 

Thats still confusing to me. I dont know wtf a snapshot is. a picture like in pokemon snap?
plus game servers doesnt even have oxide 59, just oxide 58. You have to ask them to add it for you. I tried following a tutorial to the T and couldnt get it to work. So, I wait for them add update from 59b to 68. Until then my server is loosing people and running like garbage. fun times..

 

I have 59b
Also I just added TP script Mugishi reccomended and now my server is broken, Only I can connect and no one can join. I removed all plugins and configs and data, and no one can join anymore. My server is officialy broken after that TP script with the manual thing. So now im wiping my server. I know I sound frustrated its because I am lol. There is such a lack of proper information when it comes to Oxide. They don't make it known to people like me of updates and compatibility problems or issues.
For now on, I wont test plugins anymore on my server.
Can someone please tell me what files are needed for a decent backup in the future?
Can someone plesae tell me how to manually update my oxide after I server wipe. I follow the tut when 59b was released and that didnt work.
Thanks!

 

build 59b doesn't have required hooks for latest plugins like Teleportation which is why it was freezing on my server in the first place. Thats why I need build 68

 

I agree the Author should make note it requires a specific build of oxide for its functionality 100%
can you plz link me to the tutorial on how to add it manually plz plz? thanks!
[DOUBLEPOST=1419830621][/DOUBLEPOST]Gameservers finally updated my server. yay!
[DOUBLEPOST=1419845016,1419827217][/DOUBLEPOST]With latest oxide build 68 and latest plugins a full server wipe aswell, I have zero console errors and my players are happy so I'm happy.
to join us Type
client.connect 108.61.124.27:28016
in console (F1) to join this server manually.

 

Guess we'll have to introduce a version system or something for Oxide. That way we can say which version it is actually for since at the moment we can only say 2.0

 

good idea!

 

I am having the same issue for the last 3 days..