Zyll Posted May 31, 2024 Posted May 31, 2024 If you launch a mission (no scripts) in single player, you will not notice any logged events in dcs.log, unless you explicitly request them via scripting. That's good. However, if on your local game you launch the same mission as a multiplayer server, or you put the mission (no scripting) on a dedicated server, then your logs fill with messages like these: 2024-05-31 15:57:28.565 INFO Scripting (Main): event:type=mission start,event_id=1,t=0,linked_event_id=0,ta=28800, 2024-05-31 15:57:28.565 INFO Scripting (Main): event:linked_event_id=0,t=0,event_id=2,type=took control, 2024-05-31 15:58:14.783 INFO Scripting (Main): event:type=engine startup,initiatorPilotName=TAW_Zyll,place=Kobuleti,t=42.808,placeDisplayName=Kobuleti,initiator_unit_type=UH-1H,initiator_object_id=16777729,linked_event_id=0,event_id=8,initiator_coalition=2,initiator_ws_type1=1,initiatorMissionID=2, 2024-05-31 15:58:14.792 INFO Scripting (Main): event:initiator_unit_type=UH-1H,type=under control,initiator_object_id=16777729,targetMissionID=2,target=Rotary-1-2,t=42.808,initiatorPilotName=TAW_Zyll,initiator_coalition=2, take a Huey door gunner firing into a group, and you can imagine the logs just get filled with unnecessary messages, which can hinder performance. If there is a server configuration to remove these event logs, I'd love to know it. If anyone is not seeing these messages running as a server (local install or dedicated), I'd like to compare notes. Can something like the above be used to REDUCE the amount of logging? What I don't want to do is eliminate mission makers' ability to actually log events to troubleshoot their scripts, but I don't want events to fill the logs when I didn't ask for them thanks, 1 1
Gater45988 Posted June 18, 2024 Posted June 18, 2024 Hello @Zyll, I used this to stop the spam log.set_output("dcs", "", log.WARNING, log.FULL) -Gater 1
Zyll Posted June 18, 2024 Author Posted June 18, 2024 Let me play with that a bit. I want to still see errors and informational messages that help mission makers troubleshoot their scripts, I just don't want to see all the other stuff that is being obsessively logged. Thx Gater.Zyll @ TAW 1
Actium Posted January 31 Posted January 31 While not exactly what you ask for, you can mute log messages with levels below warning, only for the missions scripting environment (instead of all info messages as above example from Gater): log.set_output("dcs", "SCRIPTING", log.WARNING, log.FULL) 1
Zyll Posted March 26 Author Posted March 26 On 1/31/2025 at 11:20 AM, Actium said: While not exactly what you ask for, you can mute log messages with levels below warning, only for the missions scripting environment (instead of all info messages as above example from Gater): log.set_output("dcs", "SCRIPTING", log.WARNING, log.FULL) how does that work exactly? is it looking for the word "SCRIPTING" in the log message and suppressing it? On 1/26/2025 at 3:54 AM, LittleNose said: Hi Zyll, did you find a suitable way to do this? unfortunately not, I just have been getting by with excessively large DCS.log on the dedicated server. tools like klogg have helped to filter the log from a readability point of view, but I'm still concerned about the performance impact
Zyll Posted March 26 Author Posted March 26 unfortunately the solutions proposed by @Actium and @Gater45988 both take away too much from the log. If there's a script error or warning or info I'd like to still get those, in order to debug any issues. It's just all the event spam which only shows on a multiplayer server that I'd like to suppress
Recommended Posts