MP airfield spawn point limitations

[TP_Jacko]

We had a few problems recently that may or may not be patch related. We had 2 spawn points close together on an airfield. It seems that there is a limit of 13 players total that is not linked to the airfield setting of unlimited AC.  Took an awful lot of re-starting to try it out then we had to split group of 16 and run as  2 separate missions.  I could not see anything wrong with the set up in the mission editor. Has anyone else had this problem

[JimTM]

I'm not sure I understand your issue TP_Jacko. Could you give a bit more detail. Did you have two fakefield or two fakernwspawn objects close together? Were you trying to spawn the max planes that each object could handle at one time? What's happening now versus what you've seen before?

Edited October 22, 2018 by JimTM

[TP_Jacko]

Hi JimTM

I am not at the pc when writing this the fakefield was the square grid not line abreast.

We had 2  groups of 8 intending to spawn side by side. In the editor the spawn points looked far enough apart.

Is there a limit to the nunber of aircraft a spawn point can accept. 

We seemed to get a block after 13 players joined the game and before selecting the base spawn point. No one could join the game after 13 were in.

Previiysly we had 16 join but spawned on dufferent airfields.

There must be an issue wuth spawn points close together.

[JimTM]

Looking at the display below the Object Library in the editor, it seems like each fake_rnwspawn (square grid) is limited to 60m wide by 90m deep or 5 slots wide by 4 slots deep. I've never tested the limits so I don't know what happens in the case of trying to spawn bombers versus fighters and what happens if two airfield objects overlap. I suspect that 60m wide by 90m may be the real limit and not the number of slots.

 

I know that at some point, the airfield object is full (I believe the message is "Airfield conditions have changed") and at least one player needs to move to make room for more players to spawn in (assuming there are more planes available).

 

You wrote "We seemed to get a block after 13 players joined the game and before selecting the base spawn point. No one could join the game after 13 were in." I assume that you mean only 13 players can spawn into planes and the rest are stuck in the map view and you do not mean that players can no longer join the server after 13 players spawn into planes, right?

 

 

Edited October 22, 2018 by JimTM

[TP_Silk]

Jim - players could not even join the server once 13 were in. It was really odd. The two spawn points were more than far enough apart not to actively interfere with each other, or at least you would have thought so. Certainly when the two groups started spawning in they were a couple of hundred meters away from each other at the nearest point. The field itself was Kalinin-South-East, which is a grass strip and the two spawn points were fake field runway spawn, so each should have been able to accommodate 15 Bf-109s spawning in simultaneously.

 

Eventually we got around this by hosting the mission on two separate servers with one Staffel spawning on each server, but that obviously meant that we weren't able to have the full Gruppe experience.

[JimTM]

Thanks for the details Jacko and Silk. It really is a strange situation. 

 

If I understand correctly, you could spawn all 16 planes into two airfield objects, as long as those airfield objects were on two different "airfields" (i.e., runway, taxiway features on the terrain). For example, Kalinin (0414-9) and Migalovo (0413-9). However, with two airfield objects at Kalinin only, you could only spawn 13 planes, split between the two airfield objects, and everyone else was locked out of the server. Is that correct?

 

For troubleshooting only:

    - Have you tried having some players move out of their spawn points to see if that lets more players join the server?

    - Have you tried removing an airfield object and spawning everyone in on one object?

If you want, I can help test the next time you have a group together.

 

If you don't mind, can you please do the following:

 

1. Copy your .sds file and remove the values for the following from the copy:

     - login

     - password

     - protection

     - ServerIP

     - RconIP

     - RconLogin

     - RconPassword

 

2. Zip the copy of the .sds file and the mission and post it here.

 

Edited October 23, 2018 by JimTM

[TP_Silk]

Mission is here

https://app.box.com/s/ifaqdymrqkt76rq6s7vwh0oawv1hds6c

 

SDS is on one of Prangster's Machines, so I'm positive that it is fine.

 

So, if we all tried to spawn into one server, it stopped letting us at 13. If I hosted one copy of the mission for one Staffel on my machine and Prangster the other on his, then we could all spawn in to our respective spawn points. One thing that we didn't try and maybe should have is to have everyone try to spawn into my version of the hosted mission, but time was marching on and we wanted to get flying before the snows hit in November  

 

The mission is done now, we got around the issue this last week. I think that Jacko is just trying to see whether this is something we're going to maybe encounter again next week.

[JimTM]

OK, thanks Silk. I did not see anything obvious in the mission that would cause the issue (I was thinking of this post). I was also wondering whether one of the DServer settings was responsible.

 

Hopefully, you just had a one-off problem and it won't reoccur.

 

Cheers!

 

Jim

Edited October 23, 2018 by JimTM