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

[ImportBot]

Originally Posted by GaWebDev*:

 

I've ran this plugin for months now and am very familiar with working through and around the various bugs that have occurred including the most recent Battlelog incompatibility (slot reporting).

 

The mapList.endRound 1 solution did work on several occasions to reset the Battlelog slot bug but now it's ineffective and in my opinion the plug-in is depreciated and should be listed as such until the new version or Battlelog-side fix is released.

 

I'm a professional web-developer and coder by trade and the recent incompatibility of this plug-in with battlelog slot reporting has cost me hours of down server time and wasted hours fixing issues that adversely affected the normal operation of Procon. YES this plugin now seems to be incompatible with Procon.

 

I have had to do at least 3 complete server-side wipes and new installs of the Procon hosting layer to fix.

 

Please don't misunderstand what I'm reporting here. It was an awesome Plugin and many thanks are due the developer.

However until a functional plug-in update addresses the Battlelog incompatibility issues or less likely Battlelog addresses the incompatibility it should be red-listed as depreciated or it will continue to cause server slot reporting issues via Battlelog and even more concerning negatively impact PROCON operation.

[ImportBot]

Originally Posted by falcontx*:

 

To be clear, there is nothing wrong with the plugin, and it's not incompatible with PRoCon. If you'll notice, the proper server size is always set and reflected properly in PRoCon. It's Battlelog that has issues. That said, I agree that the plugin should not be used until Battlelog is fixed, unless the server admin has the time to resolve potential issues when they occur. Whether that's worth the trouble is, of course, up to the admin.

[ImportBot]

Originally Posted by GaWebDev*:

 

Well said falcontx. I love the functionality of the plugin prior to last server/battlelog update. Perhaps they'll resolve the incompatibility issues with Battlelog but I'm not holding my breathe on their fix as in all honesty they are all about "privatization" of Battlelog and keeping it exclusive rather than inclusive. Their support for the open source developer community is piss poor....sadly.

[ImportBot]

Originally Posted by EBassie*:

 

Well said falcontx. I love the functionality of the plugin prior to last server/battlelog update. Perhaps they'll resolve the incompatibility issues with Battlelog but I'm not holding my breathe on their fix as in all honesty they are all about "privatization" of Battlelog and keeping it exclusive rather than inclusive. Their support for the open source developer community is piss poor....sadly.

DICE is working on it. The fix did not make it into R27 because of too short time.

The bug has already been fixed with a BETA server I tested.

 

R28 will contain the fix for this problem but will unfortunately released in August though

[ImportBot]

Originally Posted by Armor9*:

 

What is causing the bug that causes the server to lock on a particular size? For example, we have a 64 man server and it start at 16, and then moves to 24, then 32, 48 and finally 64. Today it locked on 24 and did not increase in size when the 21st player joined.

 

Not sure how this could be a battlelog issue since it is Procon that reports what server size the server should be set at. So we just turned off the plugin, set the server to 64 (no restart required) and then it was 64. So it seems like the plugin was not reporting correctly to procon to increase the server size.

[ImportBot]

Originally Posted by Jasonpb*:

 

What is causing the bug that causes the server to lock on a particular size? For example, we have a 64 man server and it start at 16, and then moves to 24, then 32, 48 and finally 64. Today it locked on 24 and did not increase in size when the 21st player joined.

 

Not sure how this could be a battlelog issue since it is Procon that reports what server size the server should be set at. So we just turned off the plugin, set the server to 64 (no restart required) and then it was 64. So it seems like the plugin was not reporting correctly to procon to increase the server size.

And did people continue to join the server up to the 64 players it was set at? I have tested this multiple times and it's not unique to this plugin and can safely say that Dice stuffed it up.

 

Although the server shows it being set at 64 players it won't allow anyone else to join, they get a "black screen" when attempting to, you then force the next round and it allows all 64 players to join.

 

If you enabled the plugin again and set the player limit to a smaller amount the exact same thing occurs until you set it back to the limit you want and then force another end round.

[ImportBot]

Originally Posted by EBassie*:

 

Although the server shows it being set at 64 players it won't allow anyone else to join, they get a "black screen" when attempting to, you then force the next round and it allows all 64 players to join.

The "Black Loading Screen" issue happens when the round was started with a lower slots count and scaled up later during the round.

 

All players joining above the 'original' slot count will get stuck in the loading screen.

 

Only way to resolve this is disabling the plugin, manual set the server size to it's max slots and end the round properly (with the new option in Procon).

 

After doing this, you can enable the plugin again.

 

Also make sure you set the plugin setting "On startup, assume round started at max server size" to YES.

[ImportBot]

Originally Posted by Armor9*:

 

Jasonpb - No, people are not able to join at that point. It turns the 64 man server into whatever size server it gets locked at until we turn the plugin off. Then it jumps back to 64. I hear what you are saying but it is seeming like it is the plugin that is holding it back because as soon as it is turned off, problem fixed.

 

BUT the plugin is needed to get big servers populated so it is a catch 22.

[ImportBot]

Originally Posted by falcontx*:

 

Jasonpb - No, people are not able to join at that point. It turns the 64 man server into whatever size server it gets locked at until we turn the plugin off. Then it jumps back to 64. I hear what you are saying but it is seeming like it is the plugin that is holding it back because as soon as it is turned off, problem fixed.

 

BUT the plugin is needed to get big servers populated so it is a catch 22.

I don't think it's the fault of the plugin, but if you believe it is, simply provide the information requested in the Support section of the first post and I'd be happy to look at it. Without proper details and logs, there's not much I can do.

[ImportBot]

Originally Posted by Xeffox*:

 

Recently on our server we have run into an issue where the adaptive server size is getting stuck at 16. So the server is 16/16 and it won't allow anymore players to join. The way we have it set and the way it worked before was after there were 14 it would kick up to 24 so it would be 15/24.

 

So if the DEV of the plugin could look into this that would be great. Thanks.

I have the same problem. A solution ?

[ImportBot]

Originally Posted by EBassie*:

 

I have the same problem. A solution ?

You have to wait until R28, which is due August.

 

This morning I received a new R28 Beta Build from DICE to test the next couple of days.

I could use some help to fill it up. So please spread the word:

 

http://battlelog.battlefield.com/bf3...-862614f2389f/

[ImportBot]

Originally Posted by Jasonpb*:

 

I don't think it's the fault of the plugin, but if you believe it is, simply provide the information requested in the Support section of the first post and I'd be happy to look at it. Without proper details and logs, there's not much I can do.

You quoted two different people. I didn't say the plugin is at fault, it's the changes DICE made that are the reason for it not working

 

Jasonpb - No, people are not able to join at that point. It turns the 64 man server into whatever size server it gets locked at until we turn the plugin off. Then it jumps back to 64. I hear what you are saying but it is seeming like it is the plugin that is holding it back because as soon as it is turned off, problem fixed.

 

BUT the plugin is needed to get big servers populated so it is a catch 22.

There's no doubt that the plugin helps seed servers but after a while if you're doing the right thing by the players your server will be full 24/7, if not the regular players tend to seed it.

 

What sucks is trying to log into your servers to have a game and there being 64 people playing and 10 people in the queue, thank god they released the VIP slots.

[ImportBot]

Originally Posted by ghostwarrior*:

 

Jasonpb - No, people are not able to join at that point. It turns the 64 man server into whatever size server it gets locked at until we turn the plugin off. Then it jumps back to 64. I hear what you are saying but it is seeming like it is the plugin that is holding it back because as soon as it is turned off, problem fixed.

 

BUT the plugin is needed to get big servers populated so it is a catch 22.

having the same problem

[ImportBot]

Originally Posted by Xeffox*:

 

Hi Falcon,

 

a small suggestion, the possibility of adding a reason with "idle kick".

 

Because when a player has kick with the plugin, there is no reason is given.

 

Thank you to you

[ImportBot]

Originally Posted by falcontx*:

 

Hi Falcon,

 

a small suggestion, the possibility of adding a reason with "idle kick".

 

Because when a player has kick with the plugin, there is no reason is given.

 

Thank you to you

The plugin doesn't actually kick anyone. It just changes the server settings that control the idle kick. In my experience, when the server kicks someone for being idle, it does state that in Battlelog after they are kicked. But, if it's not, there's nothing I could do to fix it.

[ImportBot]

Originally Posted by Xeffox*:

 

Thank you for your very quick response.

 

Anyone know how to change the result of "idle kick" ?

[ImportBot]

Originally Posted by k4n30*:

 

Thank you for your very quick response.

 

Anyone know how to change the result of "idle kick" ?

Its handled by the server, not from procon - therefore its not possible unless its done manually by a plugin, which would need to kick in before the server kicks them.

 

tbh I don't think it needs to be changed as the server provides the message "you were idle for too long" already. Or another localised version of that

[ImportBot]

Originally Posted by mrix2000*:

 

Hi all, every day my server increments fine until it reaches 64 players then it gets stuck at that point until I restart the server?

This is a common problem that many are getting right?

Cheers all

mrix

[ImportBot]

Originally Posted by EBassie*:

 

Hi all, every day my server increments fine until it reaches 64 players then it gets stuck at that point until I restart the server?

This is a common problem that many are getting right?

Cheers all

mrix

Yes, this issue is known by DICE and will be fixed with the R28 server release in August.

 

As posted before in this topic: I'm currently running a test server (R28 beta) where this issue is fixed.

[ImportBot]

Originally Posted by Leo65*:

 

Hi, I think I found a temporary "fix" for the problem where server stuck at maximum players. The downsite of this is that you will have to "sucrifise" two slots of your server. Just input in plugin settings 2 slots less than the actual number of your server's slots. My server is at 64 slots but in plugin settings I have input maximum number of players to 62. My server has hit 62/62 a few times but it never stucked there. It shows at battlelog as it shows in procon. I hope it works for you too

[ImportBot]

Originally Posted by EBassie*:

 

Hi, I think I found a temporary "fix" for the problem where server stuck at maximum players. The downsite of this is that you will have to "sucrifise" two slots of your server. Just input in plugin settings 2 slots less than the actual number of your server's slots. My server is at 64 slots but in plugin settings I have input maximum number of players to 62. My server has hit 62/62 a few times but it never stucked there. It shows at battlelog as it shows in procon. I hope it works for you too

I think you are just lucky. My 64 slot server sometimes got stuck on 48, 50 & 60

 

The only real working fix is to ask your GSP to switch to the "old" queueing system.

 

More information about the queuing system described by Mikael Kalms here:

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

[ImportBot]

Originally Posted by AgentHawk*:

 

its worked now_!

All my Servers running well today...realy strange...:/

 

Pls try it and write a feedback.

[ImportBot]

Originally Posted by uncut1980berlin*:

 

Something changed yesterday. No server size bug at 3 servers. Maybe it gonna fixed now ?

[ImportBot]

Originally Posted by purebattlefield*:

 

My server got stuck today at 64 people even though in ProCon it was displaying 42/48, or similar sizes. First time I have seen this.

[ImportBot]

Originally Posted by EBassie*:

 

Something changed yesterday. No server size bug at 3 servers. Maybe it gonna fixed now ?

It's still broken. We really have to wait for R28 later this month.

[ImportBot]

Originally Posted by EBassie*:

 

Server R28 is due on Thu Aug 9:

 

http://battlelog.battlefield.com/bf3...54625165201880*

 

The adaptize size bug will be fixed by tomorrow

[ImportBot]

Originally Posted by GaWebDev*:

 

Hooraah! Cheers and thanks for the heads up!

[ImportBot]

Originally Posted by Hutchew*:

 

Don't know about everybody else, but adaptive is locking up worse now than before for us.........

 

Great job, EA!

[ImportBot]

Originally Posted by Sabn0ck*:

 

running for 10hr 45min with no lock up. Was locking up after this time frame for me anyways. hopefully its fixed

[ImportBot]

Originally Posted by GaWebDev*:

 

running for 10hr 45min with no lock up. Was locking up after this time frame for me anyways. hopefully its fixed

I was just getting ready to re-install the plugin bit will delay the re-install until further confirmation from the plug-in's developer and/or other reports from server administrators about on-going issues. I'm watching this thread closely and am looking forward to being able to use the plug-in again after having to pull it a while back. Thanks!