Log File analysis

[=69.GIAP=STENKA]

I'm looking for a means of analysing the statistics of an online mission that I'm hosting.

Effectively using IL2 1946 there is a logfile generated at the end of each mission that you can open and read or analyse with a parser. I'm searching for the equivalent of that.

In the 1csoftclub section I edited one of the conf files to switch on logfile generation.

After running a 15 minute dogfight session, there was indeed a log generated with the filename I specified. However it was huge, and contained all the spam messages and error messages and even some stack traces. So I seem to have activated some form of debug logging - which is not what I'm after.

So does anyone know how to get the eventlog working?

I've already scanned the forums and seen what Repkaserver is doing to collect stats - which is a very complex c-script in the mission file.

[Vengeanze]

I remember that logfile from PF.
It was really cool but a bit of buggy.

Our squad took the file and parsed it with PHP and published on a website for an online campaign.

Wasn't there this great online campaign where most squads flew and stats where updated?

[Ataros]

I think in CloD statistics can be output to any file (even in web format) if you program it in the mission script (in C#). No need to parse logs as far as I know.

This is the only mission with statistics I know of http://forum.1cpublishing.eu/showthread.php?t=24954 You may wish to check it out to learn how it is done.

[=69.GIAP=STENKA]

Hi Vengeanze,

The system of mission planning and analysis that we use in IL2 1946 is called SEOW.

It holds a central campaign database, a graphic user interface to plan missions, then generates the mission files, you fly the mission, it parses the logfile, presents the stats, updates the database with new front line, resupply etc.

The results of a campaign/mission look like this

http://www.69giap.com/SEOW/MP4.773/S...mea/index.html

You can drill down to full stats on individual missions.

Ataros,

Yes thanks for the link, I had looked at the C scripting Repko are using for their stats, it's a complex chunk of code. Effectively they are controlling the start/stop, writing and analysing the equivalent of an eventlog and then generating HTML and publishing the result.

If I stick my pencil in that I'll break it.

I'm hoping to simply parse the basic events out of an existing log, then I can summarise in a spreadsheet and manipulate scoring systems till I'm happy with them - which is all I need to do for a first test campaign.

On the French Clod wiki I've found reference to the conf parameters

LOG=
LOGTIME=
logkeep=
LOGFILE=
LOGKEEP=

There is also mention of other parameters that control the ammount of detail going into the log but I'm not sure what the settings are and if they're implemented yet in clod.

I'm fairly sure that Clod has been designed to do this, however as to whether this is operational yet is a question.

[Ataros]

Server log works (Log=1, and logkeep=0 to keep it small), but it works as you described: it includes server error messages in it as well by default. Since recent patch there are not many errors on server side if a mission is done correctly (compared to the amount of errors before patch). This probably can be changed with a script I think. Try asking naryv (a developer) in this thread how to do it http://www.sukhoi.ru/forum/showthrea...=68629&page=12 (he speaks English).

I think you need a C# fluent programmer to make even one good online mission in CloD and you definitely need one to make a campaign. C# is a very popular language. I am sure you can find a programmer within your squadron or in SEOW community. COOP-based campaigns and log-parsing days are gone with good old IL-2 IMHO. In CloD you can run several "COOP" missions in the same airspace on one server at the same time but not one-by-one only as you had to do in original IL-2 COOPs.

[Ataros]

Advice from someone who really knows what he is talking about http://forum.1cpublishing.eu/showpos...4&postcount=27

[=69.GIAP=STENKA]

Thanks Ataros,

That looks like a good option