seowhq.net

There are some problems with analysis and statistics of mission 4, please wait until they are solved.

Thanks
Maraz

We need to look at why the server plane crashed at mission start, and correct so that there will not be a repeat.

This caused major lags and warping in the first 5-10 minutes of the mission, and ofcourse no radar for both sides.

The server plane is still the B-29 radar control airplane, isn't it?

We should think of a mod that would make the server plane invincible, so it will never be damaged when it "drops" on the runway

Edit: maybe increasing the ultimate G loading of this aircraft would do the trick...

But there may be easier options then coding... Has anyone tried placing the Server Airplane on a small,. non-moving escort CV so that it enters the 3d world in "chocks in" state?

Cheers,

IAF.ViFF wrote:We need to look at why the server plane crashed at mission start, and correct so that there will not be a repeat.

This caused major lags and warping in the first 5-10 minutes of the mission, and ofcourse no radar for both sides.

The server plane is still the B-29 radar control airplane, isn't it?

We should think of a mod that would make the server plane invincible, so it will never be damaged when it "drops" on the runway

But there may be easier options then coding... Has anyone tried placing the Server Airplane on a small,. non-moving escort CV so that it enters the 3d world in "chocks in" state?

Cheers,

Hi.
the server plane crash is due to a problem in the missin generated by SEDCS, that we are investigating. But it's a trivial problem (we had no problem in previos missions). The radar plane spawned in the air without fuel, so it crashed few seconds later.

But it's unlikely that the death of the server aircraft has generated lag and other problems. Scorched Earth is played using a coop server, and in coop missions it's normal that the server plane is shot down in combat or from other accidents. This should not cause lag or warps. These might be due, instead, to the mission being very heavy with so many player slots and moving ships.
Of course the death of the server plane (the usual pink B-29 ) caused radar malfunction to both sides.

Maraz

Thanks for clarifying Maraz...

Would be interesting to know if the lags and warps subsided after 5-10 minutes because the load on the server was decreased from those clients that crashed and were kicked, or it subsides after 5-10 minutes regardless of how many clients get kicked.

I remember in the BoB campaign we used to wait for the first 5-10 minutes on the ground to let the server settle down before starting up. Might not be a viable option for those with an airstart.

Cheers,

Mission analisis failed because the system did not complete properly the DSC cycle.
i.e. the seow-eventlog.lst and the database backups were not created.
System found an old seow-eventlog.lst on 17th of febraury related to a test mission I flew to check the system and then it analized that one.

The only reason why the system failed is maybe the admin ordered not only the DCS TERMINATE (that's enough in the first 10 mins) but overlayed that command with DSC REPLAY that could have stopped the DSC SEOW automatic cycle.

Since the seow-eventlog.lst was not stored, I cannot re-analize the mission and I can only restore the database Built status to replay the mission once again.

The only chance is getting the eventlog from AMVI_RugerOne who should have the complete file as he was in the game for all 3 hours.

PS: Ruger will send his file to me this evening. Please wait until 20:00 CET to know if I can analize the mission or not (in the case we must replay the mission).
Meanwhile I restored the database situation ready to replay.

22GCT_Gross wrote:Mission analisis failed because the system did not complete properly the DSC cycle.
i.e. the seow-eventlog.lst and the database backups were not created.
System found an old seow-eventlog.lst on 17th of febraury related to a test mission I flew to check the system and then it analized that one.

The only reason why the system failed is maybe the admin ordered not only the DCS TERMINATE (that's enough in the first 10 mins) but overlayed that command with DSC REPLAY that could have stopped the DSC SEOW automatic cycle.

Since the seow-eventlog.lst was not stored, I cannot re-analize the mission and I can only restore the database Built status to replay the mission once again.

The only chance is getting the eventlog from AMVI_RugerOne who should have the complete file as he was in the game for all 3 hours.

PS: Ruger will send his file to me this evening. Please wait until 20:00 CET to know if I can analize the mission or not (in the case we must replay the mission).
Meanwhile I restored the database situation ready to replay.

Diego,
did you read the e-mail I sent you this morning and the PM on 22GCT forum?

Maraz

no

Mission was analized.
Now tell me if you consider the mission not regular (I will restore the previous status) or we can go on.

PS: I'm asking for a graphic card upgrade