Page 10 of 12

Re: Dedicated Server API Client Communication

Posted: 12 Aug 2014, 22:29
by The_Big_Boo
What do you mean by "quite common"?
Anyway, I really don't have any other idea about how to find and fix this issue... I don't know what's in common among those getting it (if it's a hardware thing, an OS thing, a config thing, a particular moment during dedicated execution as I already asked for having the server status information, ...) and I still can't reproduce it whatever I try :? So, unfortunately, there's nothing I can do anymore...

Re: Dedicated Server API Client Communication

Posted: 12 Aug 2014, 22:32
by oliverde8
We are using the API in eXpansion we never had an issue, I think it works great :thx:

the fact that their amount changes suggest that it is due to changes you are doing I would say. Need to try and see that. I think checking response time and loop times to see if there is a problem with that would be interesting also.

Re: Dedicated Server API Client Communication

Posted: 18 Aug 2014, 18:21
by oliverde8
hi, we are using the version from 4th of May. we probably should update :roflol:

We do 60 cycles per second, default of Manialive.

Re: Dedicated Server API Client Communication

Posted: 19 Aug 2014, 09:27
by w1lla
apparently it gives some issues in getMaxPlayers(); in the widgetPlugin. Maybe its better to set a debug line there to make certain it can get data or not.

or add a try catch exception line into it to figure the problem out.

Re: Dedicated Server API Client Communication

Posted: 19 Aug 2014, 12:29
by steeffeen
the timeout is only happening frequently there because it's called so often

Re: Dedicated Server API Client Communication

Posted: 19 Aug 2014, 12:36
by w1lla
where it seems to be based on everyplayerconnect aswell as certain callbacks. Just by looking at the code found on github.