Missions Check

22GCT_Gross · Post by **22GCT_Gross** » Tue Feb 07, 2012 9:45 am

About playability, please report your experience.
Mission 2
# Flights 72
# Players 63
# Grounds 47
# Ships 51
# Statics 474
# Buildings 181

Mission 3
# Flights 80
# Players 80+6
# Grounds 0
# Ships 53
# Statics 526
# Buildings 224

Disconnections confirmed:
6S Boss after 84 mins - using the 96MB il2fb.exe
102nd-YU-Shtele after 94 mins - reason unknown
IAF.Xcom after 102 mins - reason unknown
22GCT_Hollywood after 147 mins - using 384Mb il2fb.exe
Mission lasted 227 mins>180 (have to check)
Very few of disconnections; I'm surprised.

242Sqn_Chap · Post by **242Sqn_Chap** » Tue Feb 07, 2012 11:03 am

Ran ok here Diego.
The initial countdown took a long time .
(but that was because somebody had not pressed fly in time I think and the DSC had to remove them.)

Classic EAF19 · Post by **Classic EAF19** » Tue Feb 07, 2012 11:07 am

Was all fine for me apart from the long startup but thats to be expected with so much action, the main thing is I dont think anyone dropped.

IAF.ViFF · Post by **IAF.ViFF** » Wed Feb 08, 2012 7:04 am

Another briliantly stable session provided by from the ITA_Server.

Molto Bene Gross

We had one pilot from the IAF that dropped due to incorrect installation of the Marianas Modpack, and this has already been fixed.

I suggest to continue to increase limits of plane slots and ship movements.

As long as there are pilots available to take the slots I suggest we keep pushing the envelope, I'm very much interested to see how far we can go.

S!

Post by **IV/JG7_4Shades** » Wed Feb 08, 2012 8:32 am

Hi Gross,

For interest, how many Statics were in the mission file?

Cheers,
4S

22GCT_Gross · Post by **22GCT_Gross** » Wed Feb 08, 2012 2:03 pm

first post edited, Mike.

102nd-YU-Mornar · Post by **102nd-YU-Mornar** » Wed Feb 08, 2012 2:20 pm

Everything was A OK!

22GCT_Gross · Post by **22GCT_Gross** » Sun Feb 12, 2012 10:38 am

Following a request form both sides, flights playability has been set at 40/40.

I recommend to check your net speed = 10000, use the 512 mb exe and keep free your network from any other process.

We are now at the edge of IL2 capability, be patient if some trouble will occur.

22GCT_Gross · Post by **22GCT_Gross** » Tue Feb 14, 2012 9:24 am

The third mission seems to have overcome the known playability limits.
I'm wondering where we can go further.

However some automatic features are not yet working (database backup, eventlog storage, mission renaming)

22GCT_Gross · Post by **22GCT_Gross** » Tue Feb 14, 2012 11:18 am

NetData20120213

1 player kicked at mission start: ping > 900
23 players must set netspeed from 8000 to 10000
2 player must set netspeed from 5000 to 10000
1 player must set netspeed from 25000 to 10000

Start Timing was not respected once more.
Please, the ADMIN MUST "DSC CLOSE" the mission at 21:30 and dont reopen.

Cipson · Post by **Cipson** » Tue Feb 14, 2012 11:46 am

22GCT_Gross wrote:The third mission seems to have overcome the known playability limits.
I'm wondering where we can go further.

100 PILOTS BIG CIRCUS?

102nd-YU-Uross · Post by **102nd-YU-Uross** » Tue Feb 14, 2012 1:30 pm

Several pilots from 102nd had stuttering and small 1-2 sec freezes, mostly when a player would leave mission, but I'm guesing that with so many players and big map, lot of ships... it's not unusual.

102nd-YU-shtele got a game freez.
=VARP=Vjeran got disco from server, but his internet was still working, he was on TS whole time.

What was unusual is that several 102nd pilots could not disconect from server when they either crashed or bailed. They had to terminate game from Task Manager. When I crashed I got message that I must leave or will be kicked from server in 600 seconds?

22GCT_Gross · Post by **22GCT_Gross** » Tue Feb 14, 2012 2:47 pm

102nd-YU-Uross wrote:When I crashed I got message that I must leave or will be kicked from server in 600 seconds?

That is a DSC setting to avoid a killed player can stay in the game. 600 secs setting let the bailed ones from high altitude to touch the ground and becorrectly registered in the eventlog.