Auto Increment - Still Working?

[Edge100x]

Pain, as I said, I only have it set up for Rush and Conquest right now. On other modes, you'll have to run with the beta adjuster feature off, or use other workarounds.

[.=QUACK=.Major.Pain]

ok thanks

[woowoo]

OK, here's our results. We have a 64 slot conquest server and a 32 slot rush server.

Conquest:
The auto increment worked great and we had no reports of the infinite load screen. Once we hit 32 players it seemed to increment straight from 32 to 64. It would be better if it continued to slowly increment instead of jumping straight to 64. Once it jumped up, we had a hard time continuing to add players - we maxed out at ~ 40 players.

Rush:
The auto increment seemed to get "stuck" a couple of times, with all slots filled and it didn't increment until a map change. However, there were no reports of the infinite load screen which is excellent news.

John, sounds like this work around solves the load problem.

[woowoo]

OK - turns out the load screen thing returns above 32. Not sure how this could possibly be. But we move nicely through to 32 players and then players are unable to join again because of the load screen issue. We've seen this 2x now.

Any ideas?

[Edge100x]

Did the level change before the system saw the low ticket count and bumped up the maximum players?

If so, then I could potentially have it check more often.

If not, then the black screen has another cause as well.

[woowoo]

Did the level change before the system saw the low ticket count and bumped up the maximum players?

If so, then I could potentially have it check more often.

If not, then the black screen has another cause as well.

I'm not sure, I noticed the level did change to maximum and back down but I didn't notice the timing.

[.=QUACK=.Major.Pain]

It is only for above 32. We tried it again with rush and conquest only and did the same thing.

On the Procon forum, someone made a plugin to do about the same thing, but has the same issue. There are claims that there is a cap that is hit that blocks additional players till the next round. If set at below 16, the server will adjust accordingly the max players, but the player join cap is at 16 where anyone after that can't join. When the round or map ends, the player join cap will jump to 24 if the max was from 24-31, and will jump to 32 if the max was 32+. Then the next levels are 48 and 64.

It is thought that there is a bug where 32 slot servers won't allow 32 players.
I think the coding might show as:

if max slots(previous round) > 32, then max slots 32(next round).

So a 32 slot server never adjusts to 32 and stays at 24 for the following rounds.

Proper coding should be:

if max slots(previous round) => 32, then max slots 32(next round).

They are sure if something is causing the = not to be recognized.
That's what the discussion has come up with so far.

[woowoo]

Interesting.

So John, the correct increment should jump straight from 32 to 64 I suppose.

[.=QUACK=.Major.Pain]

They had fixed the one for Procon where it changes the slot size just before the round loads up. We tested it last night and had a full server most of the night.

With the last patch tho, I haven't had a chance to test it.

[Edge100x]

Ours has done that for awhile, though.

[woowoo]

Ours has done that for awhile, though.

Do you mean changes the size right before round end or increment straight from 32 to 64?

I bet the procon plugin copied you.

[.=QUACK=.Major.Pain]

Ours has done that for awhile, though.

But yours causes the black loading screen still and doesn't work.

[Edge100x]

Since DICE says they fixed the black loading screen in R9, I hope not.

But I did have it bump up the player limit before new rounds started (as discussed above), to the maximum allowed by the server.

[woowoo]

Since it gets hung between 32 -> 64 can you increment directly to 64 (or whatever the max slot count is set to) for anything over 32?

[Edge100x]

woowoo, it goes to the maximum allowed by the server whenever it sees the tickets on a Conquest server drop below 50 or the tickets on a Rush server drop below 20. It checks these values every 2.5 minutes and whenever a player joins or leaves the server. 5 seconds after the new level loads, it drops the player count back down.