devtrackers.gg
Title.
External link →Title.
External link →It's what we call a tools update. Usually it's a revision to the launcher or such. In this case it's just a bit of advanced logging surrounding a few of the most frequent yet perplexing crashes we're seeing.
I imagine logging impacts performance, right?
Logging can in the overarching sense yes -- the more rapidly a log file is written to, the more resources it consumes. For this though, it's just to capture additional information when specific crashes occur, so shouldn't impact performance in any noticable way.
It all depends on context. I've worked on various projects in which logging was the performance bottleneck. Of course, the main cause was often bad programming or a system running in a debug state, but the fact is that depending on the language, logging library and amount of log statements that need to be processed, logging can have a very noticeable impact on performance.
I don't really have a clue what logging in games entails in regards to volume and message size, but I've seen first hand how research and enterprise software can be bogged down by bad logging approaches.
It can happen here too. Often when a mod becomes incompatible. It can hit the console log pretty hard and fast and has been known to degrade performance, notably on older or lower spec machines.