Jump to content

Recommended Posts

Posted

All,

 

I'm looking to work on developing some historical logs based off the activity recorded on the DSERVER.   

 

What is the command or flag that needs to go into the .sds, .cfg, or other file that will actually log the events that happen on the system during a mission?

 

I'm trying to see entries in a log similar to the following.

Pilotname departed Achtuba in a Pe-2.

Pilotname dropped 2 bombs with 50% accuracy.

Pilotname bailed out and was captured.

Pilotname was shot down by BetterPilotName

BetterPilotName fired 300 rounds with 10% accuracy.

BetterPilotName crashed and was killed.

 

I've tried enabling all the logs that were templated into the .sds, and can only get chatlog to work, and missionlog enabled; however, missionlog dumps a rather cryptic new file into the root of the folder every 5 seconds or so, resulting in 10s of thousands of files over time containing what appears to be useless data.

 

Appreciate the help from the devs or anyone that can provide some insight into how this is supposed operate.  Thanks!

 

 

 

-NW-FourSpeed
Posted

Just off the top of my head (I can't actually look from here at work), but I don't think the logging
is handled in the .sds file.

 

If I recall properly those are defined in the startup.cfg file.  They cover port settings, bandwith limits
and logging of chat and game.

 

 

Regards,

4 <salute>

Posted

Just off the top of my head (I can't actually look from here at work), but I don't think the logging

is handled in the .sds file.

 

If I recall properly those are defined in the startup.cfg file.  They cover port settings, bandwith limits

and logging of chat and game.

 

 

Regards,

4 <salute>

 

This is what our KEY=system looks like in startup.cfg"

 

- Only chatlog actually logs into logs\chat.

- the mission log is the one that dumps all those tiny files every 5 seconds into the default folder, which doesn't really contain any useful data.

 

What is the correct variable we need to include, to enable the logging we're trying to get?

 

[KEY = system]
      mgenlog = 1
      bin_log_folder = "logs\bin\"
      chatlog_folder = "logs\chat\"
      textlog_folder = "logs\text\"
      debug_info = 1
      dlgbox_sky = 0
      gamelog = 1
      keep_binary_log = 0
      modes = 0
      playoffline = 0
      reset_configs = 0
      show_net_skins = 1
      skin_dir = "graphics\Skins\"
      rcon_ip = "RE.DA.CT.ED"
      rcon_port = 8991
      chatlog = 1
      mission_text_log = 1
      rcon_start = 1
[END]
Posted (edited)

I think Lupson made his BoS Parser app based on the mission logs (those generated by mission_text_log=1), and this app's able to parse and report the info you're looking for (events, kills, hit rate...), you can try to check with him. Although it's for SP missions, he reported that he tried to do some work with MP logs too (towards the end of the thread).

Edited by yeikov
Posted

That project looks like it has potential... thank you for sharing! 

 

I'm really just trying to understand the basic logging operations of the dserver:

 

1.  How do I actually turn on the type of logging I'm looking for with the Dserver (identified above)?

2.  Once it is on, where does it store the log file and what is it called?

 

If I can get the above answered, I'm confident it will lead to more questions.   ;)

  • Upvote 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...