Adaptive Server Size (1.3.5.3 - 06/14/15)

[ImportBot]

Originally Posted by Singh400*:

 

No issues at all.

[ImportBot]

Originally Posted by GaWebDev*:

 

Thanks Singh400!

[ImportBot]

Originally Posted by EBassie*:

 

No issues here

[ImportBot]

Originally Posted by Ruger*:

 

Works fine on both of mine now.

 

 

Sent from my iPhone using Tapatalk

[ImportBot]

Originally Posted by GaWebDev*:

 

Roger. Same here. Very pleased to report that it's working superbly on our server now for several hours. Thanks for the reports gang. Cheers

[ImportBot]

Originally Posted by Sabn0ck*:

 

25hrs with no problems. It's either working or working alot better than it was.

[ImportBot]

Originally Posted by EBassie*:

 

25hrs with no problems. It's either working or working alot better than it was.

No, it's just working

[ImportBot]

Originally Posted by purebattlefield*:

 

Working for us. We're a new server and didn't have a lot of time to use the plugin before R28, but did notice the previous player cap lock issue once before R28 (which server restart fixed). Haven't noticed anything since. Seems to be working fine so far.

[ImportBot]

Originally Posted by BobbyDigital*:

 

ok plugin dont lock up no more i had update the procon layers like 2 times and that fix the problem. Now sometimes the plugin goes on and off line for some reason. The tickets be way over the limit dont know why i dont think its the plugin might be the new patch

[ImportBot]

Originally Posted by falcontx*:

 

ok plugin dont lock up no more i had update the procon layers like 2 times and that fix the problem. Now sometimes the plugin goes on and off line for some reason. The tickets be way over the limit dont know why i dont think its the plugin might be the new patch

This plugin has nothing to do with tickets. Did you mean Adaptive Ticket Count?

[ImportBot]

Originally Posted by EBassie*:

 

Hey Falcontx,

 

found an issue with the plugin. I think this one is not new, but I just found out what and why this happens.

Our servers have a 1 player start.

 

vars.roundStartPlayerCount 1

vars.roundRestartPlayerCount 0

 

 

What happens:

1. Server is freshly restarted and thus having 0 players, and full slot size (64)

2. When first player joins, server slots are set to 8 slots by the plugin

3. On first spawn of that player, the server restarts the map automatically (this always happens after fresh restart and first player spawn)

 

But when the round is restarted, the slotsize stays 8.

The plugin does not reset the server to it's max slots first.

 

When this happens, only 8 players can join the server and rest of them get stuck in the loading screen, even when the server size has been set bigger by the plugin.

 

Only way to fix this is to disable the plugin, set the server to it's max slots and end the round properly.

[ImportBot]

Originally Posted by falcontx*:

 

Hey Falcontx,

 

found an issue with the plugin. I think this one is not new, but I just found out what and why this happens.

Our servers have a 1 player start.

 

vars.roundStartPlayerCount 1

vars.roundRestartPlayerCount 0

 

 

What happens:

1. Server is freshly restarted and thus having 0 players, and full slot size (64)

2. When first player joins, server slots are set to 8 slots by the plugin

3. On first spawn of that player, the server restarts the map automatically (this always happens after fresh restart and first player spawn)

 

But when the round is restarted, the slotsize stays 8.

The plugin does not reset the server to it's max slots first.

 

When this happens, only 8 players can join the server and rest of them get stuck in the loading screen, even when the server size has been set bigger by the plugin.

 

Only way to fix this is to disable the plugin, set the server to it's max slots and end the round properly.

I'm going to need the PRoCon console logs (with events enabled) while this happens in order to fix it. Normally restarts are detected by the plugin. If this one isn't maybe there's something unique about it. I'm not sure.

[ImportBot]

Originally Posted by Flaxe*:

 

We have noticed that also EBastard, but we have never found out why it happens. Right now all our servers are pretty empty so can't test it and provide any logs atm. Maybe EBastard will be able to do it tho!

[ImportBot]

Originally Posted by dyn*:

 

I too have seen a behavior similar to this but wasn't sure what was causing it or how to duplicate it. Sadly I do not have console logging enabled as our host was pretty adamant it was causing our server to lag (they were wrong).

[ImportBot]

Originally Posted by EBassie*:

 

I will try to duplicate this behaviour.

 

My guess is it had something to do with a lagging procon layer making the plugin lag too, so it was too late to change the slot size.

[ImportBot]

Originally Posted by falcontx*:

 

I will try to duplicate this behaviour.

 

My guess is it had something to do with a lagging procon layer. So the plugin was too late to change the slot size.

It could be. That's why the logs will be necessary.

[ImportBot]

Originally Posted by EBassie*:

 

I tried to duplicate the issue. But no 'luck'.

I've enabled the debug output for the plugin now too.

 

See if I can come up with some intel about this the next time this happens.

[ImportBot]

Originally Posted by DeviousDevil*:

 

I always thought it was bad to have the round start count be higher than the round restart count... I've always had mine set to round start=1 and restart=2, and have never had any issues..

[ImportBot]

Originally Posted by Mootart*:

 

on our side what happen is.

let say the server has 10players on 16slots and the plugin is set if the player is reach 13 the server size will change it to 24

 

now the players reach 13 , 14, 15, 16 and the slot is stuck to 16players. what we do is disable the plugin and set it manual so players can join again.

 

will post the log here. soon.

 

is this the cause of the r28 update?

 

 

*ahh i got it.. before the enable idle kick is active. and the plugin is having problems

 

but when i disable it. now it work fine and great.

 

i think there might be some problem with the idle kick.

 

now for me its working great. battelogs update too.

 

update i noticed to when the agressive join is enable same problem occurs

[ImportBot]

Originally Posted by cjffly*:

 

I wonder how is this great plug-in fit with the latest update R29? Still got some problems?

[ImportBot]

Originally Posted by Singh400*:

 

I wonder how is this great plug-in fit with the latest update R29? Still got some problems?

Nope, no problems here!

[ImportBot]

Originally Posted by Mootart*:

 

if the aggressive join is disabled. plug in works great. but if the aggressive join is enabled some time the max players is example 56players and the current players is also 56. which should be like this. if should change to 64 max players it current players is already on 52p. i think there is still issue with the aggressive join vs. this plugin vs battlelog.

 

an update would be great.

 

as of now the aggressive join is disable and working like a charm. yet reserve slot would be great if enable. without having problems.

[ImportBot]

Originally Posted by falcontx*:

 

if the aggressive join is disabled. plug in works great. but if the aggressive join is enabled some time the max players is example 56players and the current players is also 56. which should be like this. if should change to 64 max players it current players is already on 52p. i think there is still issue with the aggressive join vs. this plugin vs battlelog.

 

an update would be great.

 

as of now the aggressive join is disable and working like a charm. yet reserve slot would be great if enable. without having problems.

Does the problem show only in Battlelog (i.e. sticking at 56 players)? Or does it also show max 56 in PRoCon? My guess is that the problem only shows in Battlelog, in which case there's nothing I can do to fix it.

[ImportBot]

Originally Posted by Mootart*:

 

Does the problem show only in Battlelog (i.e. sticking at 56 players)? Or does it also show max 56 in PRoCon? My guess is that the problem only shows in Battlelog, in which case there's nothing I can do to fix it.

it show on procon and battlelog.

 

happen like this. its like the plug-in is having delay to change the max players. and when more players connecting it goes now on que. bec of delay. now let say the plug-in change the max players to max the player that is already on que. get stuck on que. so what they do is leave the que and join again.

 

mostly i think something with delays of how the plug-in works.

 

will try to put some log for you asap. im going to enable the agressive join now so we can sort this out!

[ImportBot]

Originally Posted by Singh400*:

 

Does the problem show only in Battlelog (i.e. sticking at 56 players)? Or does it also show max 56 in PRoCon? My guess is that the problem only shows in Battlelog, in which case there's nothing I can do to fix it.

The latest R29 documentation does mention about how they changed the underlying commands that query the server for player count. So it might be something you could fix if there is any issue.

[ImportBot]

Originally Posted by Mootart*:

 

The latest R29 documentation does mention about how they changed the underlying commands that query the server for player count. So it might be something you could fix if there is any issue.

i dont think its with the battlelog also bec without the plugin battlelog que system works ok with aggressive join enabled

 

 

on the other hand R29 might causing some problem with the plugin. i think even with R28 and until now.

http://battlelog.battlefield.com/bf3...4348212683286/

What do you think.

 

This plug-in should be check also. to make sure.

[ImportBot]

Originally Posted by falcontx*:

 

The latest R29 documentation does mention about how they changed the underlying commands that query the server for player count. So it might be something you could fix if there is any issue.

They just added a command to check the actual player count. In this case, the desired player count, which is what is checked by the plugin, would be higher as the server grows, so this shouldn't be an issue.

 

That said, if someone can get me the proper logs, I may can fix it. It just depends on what's wrong.

[ImportBot]

Originally Posted by Mootart*:

 

They just added a command to check the actual player count. In this case, the desired player count, which is what is checked by the plugin, would be higher as the server grows, so this shouldn't be an issue.

 

That said, if someone can get me the proper logs, I may can fix it. It just depends on what's wrong.

still runing it and observing on full server. seems to be that the reserved slot is in deed messed up. waiting for something to went wrong the debug mode is on so soon as something went down will let you know soon as possible

[ImportBot]

Originally Posted by Mootart*:

 

They just added a command to check the actual player count. In this case, the desired player count, which is what is checked by the plugin, would be higher as the server grows, so this shouldn't be an issue.

 

That said, if someone can get me the proper logs, I may can fix it. It just depends on what's wrong.

still checking the logs everything looks normal. but look what i have encountered.

 

http://i.imgur.com/EPZax.jpg

 

i am stuck on que while the server already finish the round and couple of player left already im still on que while other players join.

 

any idea?

[ImportBot]

Originally Posted by falcontx*:

 

still checking the logs everything looks normal. but look what i have encountered.

 

http://i.imgur.com/EPZax.jpg

 

i am stuck on que while the server already finish the round and couple of player left already im still on que while other players join.

 

any idea?

It seems to be a bug in Battlelog. As you can see, PRoCon properly shows 50/56.