Add option to stop .log file
- Jeliozver
- Topic Author
Less
More
Would be nice to have option to stop logger.
Searched all config files and couldn't find anything.
DS3 creates quite a huge .log file for me it might have a hit on performance who knows.
Searched all config files and couldn't find anything.
DS3 creates quite a huge .log file for me it might have a hit on performance who knows.
Please Log in or Create an account to join the conversation.
- JBeckman
Less
More
8 years 7 months ago - 8 years 7 months ago #2
by JBeckman
Replied by JBeckman on topic Add option to stop .log file
Oh wow it actually does, been playing for a few days now and the file is around 1.3 GB, wonder what causes that, must be some spam in it that gets repeated endlessly thus the huge size, going to try deleting it and playing for a few minutes and see what's in it, no way I'm opening a 1.3 GB text file as that would take forever to load.
(Create a dxgi.log file and write protect it as a workaround?)
EDIT: Made a new log file.
16/04/2016 11:35:25:889 [10964] | INFO | Redirecting 'RegisterRawInputDevices(00007FFEE20A0A20, 1, 16)' ...
16/04/2016 11:35:25:889 [10964] | INFO | Redirecting 'RegisterRawInputDevices(00007FFEE20A0A50, 1, 16)' ...
Thousands and thousands of those, two addresses spammed constantly.
(Is that maybe why the Steam controller issue occurs? I only use mouse and keyboard myself but that "RawInput" something seems like it tries to detect gamepads/mice/keyboards over and over again.)
EDIT: Setting read only / write protecting the file works, won't get any diagnostic data though but it stops the file bloat, guessing it's something the game does but perhaps Crosire can work the ReShade injector around whatever is causing this issue?
(Need to see what a tracelog does too, maybe some more detailed info that could be of use?)
EDIT: Tracelog is about the same though it does create a much larger file, looks like this instead.
16/04/2016 11:47:11:996 [14676] | INFO | Redirecting 'RegisterRawInputDevices(00007FFEE20A0A50, 1, 16)' ...
16/04/2016 11:47:11:996 [14676] | TRACE | > Dumping device registration at index 0:
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
16/04/2016 11:47:11:996 [14676] | TRACE | | Parameter | Value |
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
16/04/2016 11:47:11:996 [14676] | TRACE | | UsagePage | 0x1 |
16/04/2016 11:47:11:996 [14676] | TRACE | | Usage | 0x6 |
16/04/2016 11:47:11:996 [14676] | TRACE | | Flags | 0x100 |
16/04/2016 11:47:11:996 [14676] | TRACE | | TargetWindow | 00000000014E0884 |
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
16/04/2016 11:47:11:996 [14676] | INFO | Redirecting 'RegisterRawInputDevices(00007FFEE20A0A20, 1, 16)' ...
16/04/2016 11:47:11:996 [14676] | TRACE | > Dumping device registration at index 0:
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
16/04/2016 11:47:11:996 [14676] | TRACE | | Parameter | Value |
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
16/04/2016 11:47:11:996 [14676] | TRACE | | UsagePage | 0x1 |
16/04/2016 11:47:11:996 [14676] | TRACE | | Usage | 0x6 |
16/04/2016 11:47:11:996 [14676] | TRACE | | Flags | 0x1 |
16/04/2016 11:47:11:996 [14676] | TRACE | | TargetWindow | 0000000000000000 |
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
(Create a dxgi.log file and write protect it as a workaround?)
EDIT: Made a new log file.
16/04/2016 11:35:25:889 [10964] | INFO | Redirecting 'RegisterRawInputDevices(00007FFEE20A0A20, 1, 16)' ...
16/04/2016 11:35:25:889 [10964] | INFO | Redirecting 'RegisterRawInputDevices(00007FFEE20A0A50, 1, 16)' ...
Thousands and thousands of those, two addresses spammed constantly.
(Is that maybe why the Steam controller issue occurs? I only use mouse and keyboard myself but that "RawInput" something seems like it tries to detect gamepads/mice/keyboards over and over again.)
EDIT: Setting read only / write protecting the file works, won't get any diagnostic data though but it stops the file bloat, guessing it's something the game does but perhaps Crosire can work the ReShade injector around whatever is causing this issue?
(Need to see what a tracelog does too, maybe some more detailed info that could be of use?)
EDIT: Tracelog is about the same though it does create a much larger file, looks like this instead.
16/04/2016 11:47:11:996 [14676] | INFO | Redirecting 'RegisterRawInputDevices(00007FFEE20A0A50, 1, 16)' ...
16/04/2016 11:47:11:996 [14676] | TRACE | > Dumping device registration at index 0:
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
16/04/2016 11:47:11:996 [14676] | TRACE | | Parameter | Value |
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
16/04/2016 11:47:11:996 [14676] | TRACE | | UsagePage | 0x1 |
16/04/2016 11:47:11:996 [14676] | TRACE | | Usage | 0x6 |
16/04/2016 11:47:11:996 [14676] | TRACE | | Flags | 0x100 |
16/04/2016 11:47:11:996 [14676] | TRACE | | TargetWindow | 00000000014E0884 |
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
16/04/2016 11:47:11:996 [14676] | INFO | Redirecting 'RegisterRawInputDevices(00007FFEE20A0A20, 1, 16)' ...
16/04/2016 11:47:11:996 [14676] | TRACE | > Dumping device registration at index 0:
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
16/04/2016 11:47:11:996 [14676] | TRACE | | Parameter | Value |
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
16/04/2016 11:47:11:996 [14676] | TRACE | | UsagePage | 0x1 |
16/04/2016 11:47:11:996 [14676] | TRACE | | Usage | 0x6 |
16/04/2016 11:47:11:996 [14676] | TRACE | | Flags | 0x1 |
16/04/2016 11:47:11:996 [14676] | TRACE | | TargetWindow | 0000000000000000 |
16/04/2016 11:47:11:996 [14676] | TRACE | +
+
+
Last edit: 8 years 7 months ago by JBeckman.
Please Log in or Create an account to join the conversation.