Dserver Log Parser?

[[Pb]Vapor]

The Dserver logs can be produced by flipping a flag in the start.cfg.  Is there any documentation or reference for the meaning of the values in the log files that are produced?  I have seen some mentions of parsers for these logs.  Is their an official parser or community developed one that everyone is using for this?  Or does everyone end up having to write on on their own?

 

Example of Dserver Log output:

T:0 AType:15 VER:17
T:103484 AType:12 ID:315396 TYPE:Fw 190 A-3 COUNTRY:201 NAME:noname PID:-1
T:103484 AType:12 ID:384004 TYPE:BotPilot_FW190 COUNTRY:201 NAME:BotPilot_FW190 PID:315396
T:103484 AType:10 PLID:315396 PID:384004 BUL:2480 SH:0 BOMB:0 RCT:0 (135396.625,47.184,252525.563) IDS:629b4301-fc5f LOGIN:f9242e5f-96c8-404d-b71a NAME:Pilot_Name TYPE:Fw 190 A-3 COUNTRY:201 FORM:0 FIELD:18432 INAIR:1 PARENT:-1 PAYLOAD:5 FUEL:0.600 SKIN:fw190a3/fw190a3_skin_04.dds WM:33

This appears to be Initial pilot identification?  Still uncertain of what is being declared here and what I need to reference in other logs.

 

 

[coconut]

Originally by taleks, one of the devs. I have updated it with later changes to the log format. See https://bitbucket.org/johdex/plog/src/master/

C# code, I've only update the library, ploggy. There's also two apps, plog and plog_gui which I haven't used.

[[Pb]Vapor]

21 hours ago, coconut said:

Originally by taleks, one of the devs. I have updated it with later changes to the log format. See https://bitbucket.org/johdex/plog/src/master/

C# code, I've only update the library, ploggy. There's also two apps, plog and plog_gui which I haven't used.

 

Awesome, thanks coconut!  

 

I am having some trouble with your modified version of plog.  I can get it to compile but get some strange null value errors during execution:

plog.exe "logs\missionReport(2018-02-17_13-04-58)[0].txt"

Unhandled Exception: System.ArgumentNullException: Value cannot be null.
Parameter name: key
   at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
   at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
   at System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
   at ploggy.GameObjectsData.GetUnitType(String name) in C:\Users\user\Downloads\plog\plog-1\ploggy\GameObjectsData.cs:line 37
   at ploggy.MissionLog.GetUnitType(String name) in C:\Users\user\Downloads\plog\plog-1\ploggy\MissionLog.cs:line 223
   at ploggy.MissionLog.ProcessPlayerPlaneEntry(PlayerPlaneEntry entry) in C:\Users\user\Downloads\plog\plog-1\ploggy\MissionLog.cs:line 648
   at ploggy.MissionLog.AddLogEntry(LogEntry entry) in C:\Users\user\Downloads\plog\plog-1\ploggy\MissionLog.cs:line 1089
   at ploggy.MissionLog..ctor(LogFile logFile, GameObjectsData gameObjectsData, DeathSourceClassifier deathnoteProto) in C:\Users\user\Downloads\plog\plog-1\ploggy\MissionLog.cs:line 74
   at plog.MainClass.Main(String[] args) in C:\Users\user\Downloads\plog\plog-1\plog\Program.cs:line 671

I admit I deal almost exclusively with interpreted languages so I don't compile code often myself.  In VS nlog doesn't seem to be recognized so I end up having to update the package and roll everything back to .net 3.5 (which I assume is the correct version for all three apps) 

 

I am able to compile Taleks version and it works.  Really cool tool. However, I see what you saying, BoM planes and BoK planes are not in his original Plog code.

 

For those that stumble across this, the original version written by the Dev is here: 

  But it is out of date and doesn't work properly for BoM and BoK planes.   So try and use coconuts if you can get it to work.

 

 

Edited May 2, 2018 by FFS_Vapor